Dump Huge

A dump of our database is growing more huge by the week, but we aren't doing
much with it. Properties show it us about 13gb in size, but the dump three
weeks ago was 26gb, and today it is 41gb. I dumped tran with no_log and ran
shrink, but that didn't seem to do anything. What's up with this?
Jay Marvin (JayMarvin@.discussions.microsoft.com) writes:
> A dump of our database is growing more huge by the week, but we aren't
> doing much with it. Properties show it us about 13gb in size, but the
> dump three weeks ago was 26gb, and today it is 41gb. I dumped tran with
> no_log and ran shrink, but that didn't seem to do anything. What's up
> with this?
How does your BACKUP command look like? It sounds like you are backing up
the database to the same file each time, but you are not using WITH INIT.
In that case the backup is appended to the file.
You can examine this with RESTORE HEADERONLY on the backup file. If you
get more than one row back, there are multiple backups in the file.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx