Hi

I had an old architecture where VC code did a lot of data churning, now I
have converted them as DTS tasks. I suddenly realise that the data files get
full very soon, there is no great change done from existing arch, except
that there is a table that holds ingested data until processing is over

Can anyone give me some pointers where and what should be causing the
problem. Has anyone faced something similar to the mess that I am in

could you give me some reasons why using DTS blows my data file and eats
loads of hard disk space

thanks in advance

jeune

What could be happening is that SQL Server is eating space creating work
tables.

Couple of things that speed thigs up

1. Remove triggers
2. Remove non-essential indexes (reapply afterwards)
3. Insert in batches
4. Change recovery model to SIMPLE.


--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"Joe" <joseph.jeune (AT) tfn (DOT) com> wrote

Point 1 - 3 are with regards to speed, but my issue is with space. The
recovery is simple on the db however. So these points have not actually
given me any clue, nor my work overnight on this. Any other clues with
regards to eating space since I am not sure how point 1-3 will reduce space
utilization

Thanks

Jeune
"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

The simple recovery mode cannot remove transactions that are not marked as
committed. So if you commit after every 500 or so then you only have 500
transactions in the log not 5 milllion


--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"Joe" <joseph.jeune (AT) tfn (DOT) com> wrote