Had an interesting problem on a SQL 2000, spk 3 machine last night where a
DTS data pump failed with the target database reporting the primary file
group is full. But when I looked at the server it's not.

Anyone have thoughts, etc.?

On Jun 12, 8:15am, SQLdba <burt_k...@yahoo.com> wrote:
> Had an interesting problem on a SQL 2000, spk 3 machine last night where a
> DTS data pump failed with the target database reporting the primary file
> group is full. But when I looked at the server it's not.
>
> Anyone have thoughts, etc.?

Do you have auto-growth enabled? By what increment? Most likely what
happened is that the filegroup filled up, auto-grow was triggered, but
your DTS process timed out waiting for the growth to take place. This
can happen if you're growing in large increments, say 10% on a 200GB
database - that's 20GB of new space that has to be "initialized" -
whatever process triggered the growth will have to wait for that to
take place.

My idea is that DTS was inserting lots of data, filled up the file (which
obviously didn't have autogrow enabled or which filled up a disk), and the
transaction was terminated which caused a rollback and left the free space
in the file that you now see.

Also note that sp_spaceused does not maintain accurate information. You
would need to run dbcc updateusage (beware performance hit) to get accurate
data on space.

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"SQLdba" <burt_king@yahoo.com> wrote in message
news:98A62F89-4AD3-412A-ABE0-7C21B00B3EB2@microsoft.com...
> Had an interesting problem on a SQL 2000, spk 3 machine last night where a
> DTS data pump failed with the target database reporting the primary file
> group is full. But when I looked at the server it's not.
>
> Anyone have thoughts, etc.?
>
>