Hello ,
Find out what it is that is actually growing and blowing. My guess would
be the logs as data ais retrieved from the source (by default) in one huge
batch before being inserted and if you have a lot of data then this could
cause the log to grow and blow your disk space.
Have a look at how much space on your drives you have to play with. Maybe
it is time to add a new drive or think about cleaning up anything that does
now not need to be there.
You can also have a look to insert in batches (last tab transform data task)
.. This will at least allow the log to breathe and may save you for a while
but it really seems that this would only put off when the data gets too big
and eats the remaining disk space.
--
Allan Mitchell
http://wiki.sqlis.com |
http://www.sqlis.com |
http://www.sqldts.com |
http://www.konesans.com [quoted text, click to view] > Hi,
>
> I think make a house keeping into you db server and shrink or release
> unecessary logs of db(s)
>
> "Simon" <Simon@discussions.microsoft.com> wrote in message
> news:26454713-D0AA-4858-8449-5193FA995009@microsoft.com...
>
>> I have written a series of DTS packages which move data from a FOX
>> database
>> onto SQL2000. The packages work fine for small tables. However when I
>> run
>> a
>> package that looks at a large table in FOX then I get an unspecified
>> error
>> in
>> the DTS designer. Before the error comes up I get a message saying
>> low
>> disk
>> space on server. I`m assuming that DTS uses disk space on the server
>> to
>> process the data. I`m guessing this defaults to the drive that SQL is
>> installed on. How can I change that so it can use a drive with much
>> more
>> space ?
>> Thanks
>>
>> Si
>>