Hello,

I have an issue with DTS. I have had a package that has run for several
month without issues. But all of a sudden, the package is creating files
with excessive white space. A 20 MB files is grown to 909 MB.

I have checked and there are no new updates applied, and there is nothing in
the event logs either. I have never seen anything like this before. I have
created the same package on the dev version of the server and it works
properly. I have re-booted the server as well and this still persists.

Server Stats

Windows 2003 SP1
4-CPU Server
8GB RAM, AWE Enabled

SQL 2000 Enterprise, SP4
6GB Physical Reserve
512 Threads
Fail-Over Cluster

Any additional information needed will be provided.

Anybody, and Ideas?

Thanks for your help!

Respectfully,
--
David C. Eaton

Hello David,

Where is the whitespace being created? At the start or the end of the generated
file?
This is a text file right?
Does it happen when you reduce the rows exported?
Is this going to the same file everytime? If yes then what about if you
send to a different file?
What does profiler say about the query?
Is the whitespace increasing on every run?
Happen with all queries or just this one?

When you change the destination medium to say SQL Server what happens? Empty
rows?


Allan

Allan,

The whitespace is in between the fields in the text file, ASCII Fixed Length
Records. If I run the the same query in Query Analyzer with the output to a
text file, there are no problems. The query runs for about 2 minutes to
write out 40,000 rows with a file size of 19MB. As a DTS package, it takes
30-40 minutes to run for the same 40,000 rows and the file 965 MB. The
amount of the whitespace seems constant. The data is correct, it is just
blown out with whitespace. The fixed length recors is supposed to be 170
characters per row, in the output file they are 23552 characters per row.

The query is a very well behaved qeury. It runs in 16 seconds if I return
the data to the grid in Query Analyzer.

I have dropped and created a new DTS package, with no luck. I have pointed
the ouput to different files and different servers wit the same problem.

This package was running without this issue for several months until the
other day. It runs on the QS version of the system, slower but with no
whitespace.

I never get "empty rows"

I hink this answers your questions. Like I said, it has been working for
months, and then boom!

Respectfully,

--
David C. Eaton


"Allan Mitchell" wrote: