Database has gotten relatively large

I upgraded a database from SQL2000 to SQL2005 and it went pretty smooth. After the transition was made, I backed up the DB. The size of the database was as expected, about 5 GB. About 5 hours later, a maintenance plan executed a few optimization jobs in the following order: Reorganize Index, Rebuild Index, Shrink Database, Update Statistics. Soon after that, another job backed up the database and it was then 32 GB. During the time after the first backup, no one was really using the database.

I've been trying to track this down for several days. Does anyone have any ideas for me?

Thanks,
Bobby Crawford
SQL Workbench has some nifty reports you can run, one of which is Disk Usage, it details how much space each table is using. THis should help you track it down.

database diagrams in SQL 2000 + VS.NET 2005

I've recently upgraded to VS.NET 2005 (still using SQL Server 2000),
and I'm no longer able to edit database diagrams from with VS.NET as I
could with VS.NET 2003. Am I missing a setting somewhere, or is this no
longer
supported?
Thanks,
g.not sure about vs.NET 2005, but I know that you can't edit SQL server
2000 diagrams using sql server 2005 management studio, so I would
assume that VS 2005 has had to make a similar sacrifice in order to
provide the ability to edit the sql 2005 ones.
Cheers
Will|||Thanks. Good thing I kept VS2003 around, I guess!