Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 19,010 of 19,505    |
|    bradbury9 to All    |
|    Re: How to specify SQL Server disk space    |
|    12 Feb 14 08:49:12    |
      From: ray.bradbury9@gmail.com              El miércoles, 12 de febrero de 2014 17:14:37 UTC+1, rja.ca...@gmail.com        escribió:       > We're planning migration of an enterprise reporting system        >        > to SQL Server 2012, and my boss needs an argument to support        >        > installing a certain amount of disc space for ongoing        >        > operations. Can someone point me to a credible argument        >        > for a reasonable minimum allowance of free disk space in        >        > addition to our actual databases?       >        >        >        > I believe that this includes not having to shrink database        >        > files to let others grow, which we are doing now.       >        >        >        > With 1 TB of nightly crushed data, indexes and t-logs, and 0.6 TB        >        > free, I think that we should shop for around 4 TB total space,       >        > and, /yes/ we /could/ buy that size of hard disk for under        >        > US$200 but apparently it isn't that simple. Although, obviously,       >        > it ought to be.              When things with backups and maintenance plans go *really* wrong some free       space in a separate partition could save your asses.              Will not mention names, but in my previous job a bad and non-supervised       manteninance plan made database transaction log grow in such a way that:       - Server had no free disk space.       - Transaction log got corrupted.       - Had no recent backup to restore from.       - Had no free space and could not attach any device to the server to get it.              Long history short:       - Spent 6 hours until recovered main production database. 3 enterprises from       our group had to stop working until fixed.       - If we had some free space we could have backup the database and made it       shrink (after setting it up right).              After that incident I would have cheched the backup policy and maintanance       plans, but I just could give some advice and no actions were taken.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca