OK, here's the situation.

We have a DTS Package that contains about 60 or so steps. Each of these
steps is a call to a stored procedure, passing it some parameters. On
very few occasions (less than 1% of 1%) something happens that puts DTS
(or maybe tempdb) into a wierd state, causing tempdb to continue to
expand until it fills the entire hard drive (at this point tempdb is
over 16 gb).

My question is, has anyone see similar behavior with DTS before?

We have poured over the code, and while not the most efficient, there
are no obvious errors that should cause the tempdb to fill up. My
colleague has reproduced this error and we are currently looking into
it, but I wanted to know if this could be a bug in DTS, or is just very
poorly written T-SQL.

Thanks,

Patrick

My guess would be poorly written TSQL.

TempDB is used for a whole raft of things and it is not all that uncommon for it to bloat.

Look at your code and see why.

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - SQL Server 2005 Integration Services.
www.Konesans.com


"pbrisbine" <patrickbrisbine (AT) hotmail (DOT) com> wrote