Were you running shrink or do you have auto-shrink turned on? Looks like you've hit a bug in shrink - see here for details and the fix http://support.microsoft.com/kb/811205

If you are...

There are two issues around blocking in SP4. One's a real bug, the other isn't.

The first one is a bug in the lock manager that manifests during DBCC INDEXDEFRAG. The...

So was the data perfectly readable in the source database? Using what mechanism?

How did you copy it?

That's bad advice - never just run repair. You should always do root cause analysis to prevent a recurrence and make an informed choice between restoring from your up-to-date backups...

Do you have any backups? You should be able to restore to the point the log is corrupted by the AV software.

Did you run CHECKDB after deleting the transaction logs?

Regards

I haven't seen an increasing trend since SP4 was released and on't know of any bugs that would cause it.

What does it say in the errorlog before the database is...

Hi Kevin,

Removing the (index) fragmentation should only be done if the fragmentation is going to affect the perf of your query workload. Basically, if the fragmented indexes are involved in...

So it seems like the destination db data growth can't be helped, as you're simply inserting a bunch of data into it. Its log file growth could be limited by...

It's totally safe. The previous post about it working as a single transaction is wrong - it works as a series of very small system transactions so there is nothing...

Take a look at my signature - I'm responsible for all the Storage Engine in MS and I'm telling you that autoshrink is discouraged. Shrinking is only useful in a...

The log file is increased by 4-5 Gb, or the data file? I think you mean data file for tempdb.

What does this SP do?

Extents

I'm curious - did the PSS person warn you about the consequences of rebuilding the log? Were you instructed to do anything else after rebuilding the log?

Thanks

As a general practice you should not run shrink. The DB needs space to operate in and will likely just grow again. Also, shrink introduces fragmentation when it moves data...

Please post in one of the other forums - this is not a data corruption issue. Thanks.