Data Flow Task Problem: cut

Showing posts with label cut. Show all posts

Wednesday, March 7, 2012

Data being cut off on text import

I am trying to use SQL Server 2000 import/export funtion to import a
tab delimited text file. Some of the lines have upwards fo 27,000
characters in it. The first column of data is only 16 characters, the
rest in the second column. When I import it works however end up on
the largest data set to only have 8194 characters of data in the
field. I am importing the data into an NTEXT field but no joy. Any
suggestions?
Thanks.
JR
How are you determining that there are 8194 characters? Are you selecting
the data in Query Analyzer, copying it, and measuring the length? In this
case, the output is limited to 8192 characters, and does not necessarily
truly represent the data in the column. Try applying DATALENGTH() to the
column directly.
"JR" <jriker1@.yahoo.com> wrote in message
news:4d9da209-6bd6-4537-a3f9-184b6544ff49@.l1g2000hsa.googlegroups.com...
>I am trying to use SQL Server 2000 import/export funtion to import a
> tab delimited text file. Some of the lines have upwards fo 27,000
> characters in it. The first column of data is only 16 characters, the
> rest in the second column. When I import it works however end up on
> the largest data set to only have 8194 characters of data in the
> field. I am importing the data into an NTEXT field but no joy. Any
> suggestions?
> Thanks.
> JR

Data being cut off on text import

I am trying to use SQL Server 2000 import/export funtion to import a
tab delimited text file. Some of the lines have upwards fo 27,000
characters in it. The first column of data is only 16 characters, the
rest in the second column. When I import it works however end up on
the largest data set to only have 8194 characters of data in the
field. I am importing the data into an NTEXT field but no joy. Any
suggestions?
Thanks.
JRHow are you determining that there are 8194 characters? Are you selecting
the data in Query Analyzer, copying it, and measuring the length? In this
case, the output is limited to 8192 characters, and does not necessarily
truly represent the data in the column. Try applying DATALENGTH() to the
column directly.
"JR" <jriker1@.yahoo.com> wrote in message
news:4d9da209-6bd6-4537-a3f9-184b6544ff49@.l1g2000hsa.googlegroups.com...
>I am trying to use SQL Server 2000 import/export funtion to import a
> tab delimited text file. Some of the lines have upwards fo 27,000
> characters in it. The first column of data is only 16 characters, the
> rest in the second column. When I import it works however end up on
> the largest data set to only have 8194 characters of data in the
> field. I am importing the data into an NTEXT field but no joy. Any
> suggestions?
> Thanks.
> JR

Data being cut off on text import

I am trying to use SQL Server 2000 import/export funtion to import a
tab delimited text file. Some of the lines have upwards fo 27,000
characters in it. The first column of data is only 16 characters, the
rest in the second column. When I import it works however end up on
the largest data set to only have 8194 characters of data in the
field. I am importing the data into an NTEXT field but no joy. Any
suggestions?
Thanks.
JRHow are you determining that there are 8194 characters? Are you selecting
the data in Query Analyzer, copying it, and measuring the length? In this
case, the output is limited to 8192 characters, and does not necessarily
truly represent the data in the column. Try applying DATALENGTH() to the
column directly.
"JR" <jriker1@.yahoo.com> wrote in message
news:4d9da209-6bd6-4537-a3f9-184b6544ff49@.l1g2000hsa.googlegroups.com...
>I am trying to use SQL Server 2000 import/export funtion to import a
> tab delimited text file. Some of the lines have upwards fo 27,000
> characters in it. The first column of data is only 16 characters, the
> rest in the second column. When I import it works however end up on
> the largest data set to only have 8194 characters of data in the
> field. I am importing the data into an NTEXT field but no joy. Any
> suggestions?
> Thanks.
> JR

Friday, February 17, 2012

Cyrillic problem with cr10 on XP and 2003

When I run my application on windows 2000 everything is ok. But on XP service pack 2 and windows 2003 words in report cut at the end of the line. Words a written in cyrillic alphabet. Does anybody meet this problem?Set Can Grow option for that field

Cutting to a certain word

Hi there, i need to know how to cut a string to the nearest word. For example, i've got an article and i need to extract just a part of the beginning, i could use LEFT([content], 250) but there is little chance this will cut on a word. Therefore i need to know if there is a function that will cut to the nearest word in T-SQL or i will simply put a summary field in the database. (I prefer to generate the summary on the fly if possible)

You could use CHARINDEX.

SELECT LEFT(column, CHARINDEX(' ', column) ) FROM yourTable

|||

I just looked up what you said and this doesn't make sense...

I didn't even try but i know what this will result in... Returns the first word of a column...

But i guess if i provide a startAT value(param 3) to charindex i can start the search at 250 characters and it will cut accordingly...

|||

Yes, this will always give you a full word:

Declare @.tvarchar(100), @.startatintSET @.t ='this is a good test and a long sentence to test end of word'SET @.startat = 33SELECT @.t,left(@.t,@.startat + CHARINDEX(' ',right(@.t,len(@.t) - @.startat)))

Tuesday, February 14, 2012

cut the size of the log

I use this command but it doesnot work
cannot cut the size of the log to 2MB
DBCC SHRINKFILE(ABC_log,2)
what is the correct command actually pls?
actually i want to cut the size
because it is testing environment
"izumi" <test@.test.com> wrote in message
news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
> I use this command but it doesnot work
> cannot cut the size of the log to 2MB
> DBCC SHRINKFILE(ABC_log,2)
> what is the correct command actually pls?
>
|||If you are using a FULL or BULK LOGGED recovery model (SELECT
SERVERPROPERTYEX ('<db name>', 'RECOVERY), you can't shrink the log file
unless you backup the transaction log or truncate it. If you are using the
SIMPLE recovery model, you can't shrink it much if there are open
transactions that happen to occupy the end of the file.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"izumi" <test@.test.com> wrote in message
news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
> I use this command but it doesnot work
> cannot cut the size of the log to 2MB
> DBCC SHRINKFILE(ABC_log,2)
> what is the correct command actually pls?
>
|||http://www.nigelrivett.net/Transacti...leGrows_1.html
"izumi" wrote:

> actually i want to cut the size
> because it is testing environment
> "izumi" <test@.test.com> wrote in message
> news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
>
>
|||finnaly I offline the database
go to physical path and delete the abc_log
then get back much more disk space
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:%23IsFtKMXEHA.3988@.tk2msftngp13.phx.gbl...
> If you are using a FULL or BULK LOGGED recovery model (SELECT
> SERVERPROPERTYEX ('<db name>', 'RECOVERY), you can't shrink the log file
> unless you backup the transaction log or truncate it. If you are using
the
> SIMPLE recovery model, you can't shrink it much if there are open
> transactions that happen to occupy the end of the file.
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backup files? Try MiniSQLBackup
>
> "izumi" <test@.test.com> wrote in message
> news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
>
|||I hope you did a backup before. This is not a safe operation, and you should consider yourself lucky
if the database isn't corrupt after the operation.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"izumi" <test@.test.com> wrote in message news:e2z8mbMXEHA.644@.tk2msftngp13.phx.gbl...
> finnaly I offline the database
> go to physical path and delete the abc_log
> then get back much more disk space
> "Peter Yeoh" <nospam@.nospam.com> wrote in message
> news:%23IsFtKMXEHA.3988@.tk2msftngp13.phx.gbl...
> the
>
|||Yes i agree your point....
But this time it is testing environment...
so it is ok
next time, if it is live, i will backup
Thanks d><b
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e9I4kyNXEHA.2940@.TK2MSFTNGP09.phx.gbl...
> I hope you did a backup before. This is not a safe operation, and you
should consider yourself lucky
> if the database isn't corrupt after the operation.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "izumi" <test@.test.com> wrote in message
news:e2z8mbMXEHA.644@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
file[vbcol=seagreen]
using
>
|||Hi Izumi
What does 'does not work' mean? Do you get an error message? If so, what
error? Do you get any response at all? What does it say?
What version of SQL Server are you running?
Please give us more information.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"izumi" <test@.test.com> wrote in message
news:#VPGv#KXEHA.2408@.tk2msftngp13.phx.gbl...
> I use this command but it doesnot work
> cannot cut the size of the log to 2MB
> DBCC SHRINKFILE(ABC_log,2)
> what is the correct command actually pls?
>
|||I also had a hard time with this problem. If it's a testing environment or you just don't care about being able to recover to a point in time, change the recovery model to Simple and then issue the following command in SQL Query Analyzer.
SHRINKFILE (logfilename_log, -1)
In the simple recovery model, a sequence of transaction logs is not being Maintained. All log records before the MinLSN can be truncated at any time, except while a BACKUP statement is being processed. The log file will shrink down to about 1mb.
"Kalen Delaney" wrote:

> Hi Izumi
> What does 'does not work' mean? Do you get an error message? If so, what
> error? Do you get any response at all? What does it say?
> What version of SQL Server are you running?
> Please give us more information.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "izumi" <test@.test.com> wrote in message
> news:#VPGv#KXEHA.2408@.tk2msftngp13.phx.gbl...
>
>
|||I also had a hard time with this problem. If it's a testing environment or you just don't care about being able to recover to a point in time, change the recovery model to Simple and then issue the following command in SQL Query Analyzer.
SHRINKFILE (logfilename_log, -1)
In the simple recovery model, a sequence of transaction logs is not being Maintained. All log records before the MinLSN can be truncated at any time, except while a BACKUP statement is being processed. The log file will shrink down to about 1mb.
"Kalen Delaney" wrote:

> Hi Izumi
> What does 'does not work' mean? Do you get an error message? If so, what
> error? Do you get any response at all? What does it say?
> What version of SQL Server are you running?
> Please give us more information.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "izumi" <test@.test.com> wrote in message
> news:#VPGv#KXEHA.2408@.tk2msftngp13.phx.gbl...
>
>

cut the size of the log

I use this command but it doesnot work
cannot cut the size of the log to 2MB
DBCC SHRINKFILE(ABC_log,2)
what is the correct command actually pls?actually i want to cut the size
because it is testing environment
"izumi" <test@.test.com> wrote in message
news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
> I use this command but it doesnot work
> cannot cut the size of the log to 2MB
> DBCC SHRINKFILE(ABC_log,2)
> what is the correct command actually pls?
>|||If you are using a FULL or BULK LOGGED recovery model (SELECT
SERVERPROPERTYEX ('<db name>', 'RECOVERY), you can't shrink the log file
unless you backup the transaction log or truncate it. If you are using the
SIMPLE recovery model, you can't shrink it much if there are open
transactions that happen to occupy the end of the file.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"izumi" <test@.test.com> wrote in message
news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
> I use this command but it doesnot work
> cannot cut the size of the log to 2MB
> DBCC SHRINKFILE(ABC_log,2)
> what is the correct command actually pls?
>|||http://www.nigelrivett.net/TransactionLogFileGrows_1.html
"izumi" wrote:
> actually i want to cut the size
> because it is testing environment
> "izumi" <test@.test.com> wrote in message
> news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
> > I use this command but it doesnot work
> >
> > cannot cut the size of the log to 2MB
> >
> > DBCC SHRINKFILE(ABC_log,2)
> >
> > what is the correct command actually pls?
> >
> >
>
>|||finnaly I offline the database
go to physical path and delete the abc_log
then get back much more disk space
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:%23IsFtKMXEHA.3988@.tk2msftngp13.phx.gbl...
> If you are using a FULL or BULK LOGGED recovery model (SELECT
> SERVERPROPERTYEX ('<db name>', 'RECOVERY), you can't shrink the log file
> unless you backup the transaction log or truncate it. If you are using
the
> SIMPLE recovery model, you can't shrink it much if there are open
> transactions that happen to occupy the end of the file.
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backup files? Try MiniSQLBackup
>
> "izumi" <test@.test.com> wrote in message
> news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
> > I use this command but it doesnot work
> >
> > cannot cut the size of the log to 2MB
> >
> > DBCC SHRINKFILE(ABC_log,2)
> >
> > what is the correct command actually pls?
> >
> >
>|||I hope you did a backup before. This is not a safe operation, and you should consider yourself lucky
if the database isn't corrupt after the operation.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"izumi" <test@.test.com> wrote in message news:e2z8mbMXEHA.644@.tk2msftngp13.phx.gbl...
> finnaly I offline the database
> go to physical path and delete the abc_log
> then get back much more disk space
> "Peter Yeoh" <nospam@.nospam.com> wrote in message
> news:%23IsFtKMXEHA.3988@.tk2msftngp13.phx.gbl...
> > If you are using a FULL or BULK LOGGED recovery model (SELECT
> > SERVERPROPERTYEX ('<db name>', 'RECOVERY), you can't shrink the log file
> > unless you backup the transaction log or truncate it. If you are using
> the
> > SIMPLE recovery model, you can't shrink it much if there are open
> > transactions that happen to occupy the end of the file.
> >
> > Peter Yeoh
> > http://www.yohz.com
> > Need smaller SQL2K backup files? Try MiniSQLBackup
> >
> >
> > "izumi" <test@.test.com> wrote in message
> > news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
> > > I use this command but it doesnot work
> > >
> > > cannot cut the size of the log to 2MB
> > >
> > > DBCC SHRINKFILE(ABC_log,2)
> > >
> > > what is the correct command actually pls?
> > >
> > >
> >
> >
>|||Yes i agree your point....
But this time it is testing environment...
so it is ok
next time, if it is live, i will backup
Thanks d><b
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e9I4kyNXEHA.2940@.TK2MSFTNGP09.phx.gbl...
> I hope you did a backup before. This is not a safe operation, and you
should consider yourself lucky
> if the database isn't corrupt after the operation.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "izumi" <test@.test.com> wrote in message
news:e2z8mbMXEHA.644@.tk2msftngp13.phx.gbl...
> > finnaly I offline the database
> > go to physical path and delete the abc_log
> >
> > then get back much more disk space
> > "Peter Yeoh" <nospam@.nospam.com> wrote in message
> > news:%23IsFtKMXEHA.3988@.tk2msftngp13.phx.gbl...
> > > If you are using a FULL or BULK LOGGED recovery model (SELECT
> > > SERVERPROPERTYEX ('<db name>', 'RECOVERY), you can't shrink the log
file
> > > unless you backup the transaction log or truncate it. If you are
using
> > the
> > > SIMPLE recovery model, you can't shrink it much if there are open
> > > transactions that happen to occupy the end of the file.
> > >
> > > Peter Yeoh
> > > http://www.yohz.com
> > > Need smaller SQL2K backup files? Try MiniSQLBackup
> > >
> > >
> > > "izumi" <test@.test.com> wrote in message
> > > news:%23VPGv%23KXEHA.2408@.tk2msftngp13.phx.gbl...
> > > > I use this command but it doesnot work
> > > >
> > > > cannot cut the size of the log to 2MB
> > > >
> > > > DBCC SHRINKFILE(ABC_log,2)
> > > >
> > > > what is the correct command actually pls?
> > > >
> > > >
> > >
> > >
> >
> >
>|||Hi Izumi
What does 'does not work' mean? Do you get an error message? If so, what
error? Do you get any response at all? What does it say?
What version of SQL Server are you running?
Please give us more information.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"izumi" <test@.test.com> wrote in message
news:#VPGv#KXEHA.2408@.tk2msftngp13.phx.gbl...
> I use this command but it doesnot work
> cannot cut the size of the log to 2MB
> DBCC SHRINKFILE(ABC_log,2)
> what is the correct command actually pls?
>|||it means the the size of the log is kept unchanged
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:O98aR8QXEHA.1684@.tk2msftngp13.phx.gbl...
> Hi Izumi
> What does 'does not work' mean? Do you get an error message? If so, what
> error? Do you get any response at all? What does it say?
> What version of SQL Server are you running?
> Please give us more information.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "izumi" <test@.test.com> wrote in message
> news:#VPGv#KXEHA.2408@.tk2msftngp13.phx.gbl...
> > I use this command but it doesnot work
> >
> > cannot cut the size of the log to 2MB
> >
> > DBCC SHRINKFILE(ABC_log,2)
> >
> > what is the correct command actually pls?
> >
> >
>|||There are some links to articles regarding shrink of files for tlog at
http://www.karaszi.com/SQLServer/info_dont_shrink.asp.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"izumi" <test@.test.com> wrote in message news:OeFMDCbXEHA.2940@.TK2MSFTNGP09.phx.gbl...
> it means the the size of the log is kept unchanged
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:O98aR8QXEHA.1684@.tk2msftngp13.phx.gbl...
> > Hi Izumi
> >
> > What does 'does not work' mean? Do you get an error message? If so, what
> > error? Do you get any response at all? What does it say?
> >
> > What version of SQL Server are you running?
> >
> > Please give us more information.
> >
> > --
> > HTH
> > --
> > Kalen Delaney
> > SQL Server MVP
> > www.SolidQualityLearning.com
> >
> >
> > "izumi" <test@.test.com> wrote in message
> > news:#VPGv#KXEHA.2408@.tk2msftngp13.phx.gbl...
> > > I use this command but it doesnot work
> > >
> > > cannot cut the size of the log to 2MB
> > >
> > > DBCC SHRINKFILE(ABC_log,2)
> > >
> > > what is the correct command actually pls?
> > >
> > >
> >
> >
>

Wednesday, March 7, 2012

Data being cut off on text import

Data being cut off on text import

Data being cut off on text import

Friday, February 17, 2012

Cyrillic problem with cr10 on XP and 2003

Cutting to a certain word

Tuesday, February 14, 2012

cut the size of the log

cut the size of the log

cut the size of the log

Data Flow Task Problem

Blog Archive

About Me