September 6, 2013 at 6:33 pm
Hi let me first say I know shrinking a Database is bad for fragmentation.
What I want to know is with a very large database, does it cause a performance issue to have a lot of unused space. I'm talking about a 1.8 TB database with 475 GB of unused space.
I ask this not because I want to shrink it, but because I want to avoid the manual file growth requirement (not set by me) to grow the data file when there is less than 20% free space.
I'd prefer to configure auto growth at 8GB and let it roll which got me thinking about, "how does the amount of free space within a data file relate to performance"?
Thanks!
September 6, 2013 at 9:40 pm
The only thing I can think of that might be a performance effect of this is having data be physically "far apart" on disks, leading to a few extra milliseconds of access/seek time. But as long as you aren't serving this up on 4 disks or something I think that would be a minimal effect.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
September 7, 2013 at 12:03 am
Jon.Morisi (9/6/2013)
Does it cause a performance issue to have a lot of unused space.
No.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy