I’m dropping out massive numbers of tables out of a SQL Server 2005 database. How do I shrink the database – assuming I’m not replacing the data or the tables? I’m archiving stuff to another db.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m dropping out massive numbers of tables out of a SQL Server 2005 database. How do I shrink the database – assuming I’m not replacing the data or the tables? I’m archiving stuff to another db.
or
However, shrinking files will likely fragment your tables, particularly larger onces, as contents of tables get moved about within the file, so once shrunk it’s a good idea to defragment your tables. This, of course, will make your files grow again, but probably not so large as they were before you dropped your old tables. (Err, that assumes that the dropped tables contained large quantities of data…)