SP_Spaceused
-
I have a question about how to interpret the results from sp_spaceused
I have a database (SQL Server 2008 R2) that is about to be moved from Development into Production and when I run sp-spaceused it appears to me that there is quite a bit (over 16gb)
database_namedatabase_sizeunallocated space
MYDatabase19705.00 MB16326.98 MB
reserved data index_sizeunused
1819672 KB883976 KB924144 KB11552 KB
My thought was to backup the database and then shrink it.
Any thoughts or suggestions?
-
Why do you think you need to shrink it? Wouldn't you think that production will get a lot bigger than dev anyway?
http://www.brentozar.com/archive/2009/08/stop-shrinking-your-database-files-seriously-now/[/url]
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/ -
I do not anticiapate that the Database will grow alot from this point. They spent quite a bit of time loading Data (with the Vendors help) while in Development and went through 2 separate Front-end upgrades to fix some issues they were having in the process. Their original estimate on what the Production size would be was no more than 8-10 gb. I was just looking to get things cleaned up (space-wise) before moving it to production and I was looking for the most prudent way to go about doing that.
-
I'm nott a big fan of shrinking a database, if you have enough space on production, maybe worth it to keep it as it is.
-
As there is lot of unallocated space then once you can shrink the file..
if it grows again then don't shrink file again.
Note:As specified by some geeks ,it is not advisable to shrink files.
Pramod
SQL Server DBA | MCSE SQL Server 2012/2014
in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/ -
Maybe another approach would be to create a new database and then script all the objects and transfer in the data? For the small amount of data it shouldn't take very long at all.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/ -
Thank you all for your insight!!!! I will script out all object and move my data into a new Database rather than shrink and risk the fragmentation.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply