This project has moved and is read-only. For the latest updates, please go here.

Shrinking a Collection Database that has been split

Apr 8, 2010 at 8:11 PM

I ran into a problem when I tested an upgrade to 2010. I upgraded my 2008 server database to  2010 and decided to split the database to smaller collections based on business ownership. After the first two successful splits I noticed I was running out of space on my data tier. I then noticed that both the original collection database and the new collection database were the same in size. Is there a job that will shrink the new collection database after after it has been split? I would think that the new database would be a lot smaller after some projects have been removed.