I am moving SQL 2000 databases to a new SQL 2008 R2 instance. I am using the Copy Database Task, with the SQL Management Objects option.
I was constantly getting the following error during the copy process:
Then, I decided to remove any file growth restrictions on the source SQL server for this particular database. Monitoring the growth, I saw that on my new SQL 2008 desintation server, a database which the .mdf file was 1.5GB in size was continuing to grow
past 40GB! Then I ran out of disk space, and the job failed. What in the world is causing this database to grow so fat? Is this is a bug? This also happened with another database of mine, in which the secondary .NDF file went from being 500MB to 27GB!
View Complete Post