Hey all, I need some help / advice. Newly started at a company (purchased by a crew trying to turn things around) and there's a lot of basic, IT-101 type stuff that isn't being done. One is that there has been no data archival. Predictably, we're near to filling up a filesystem (7-8% left). Looking at the tables there are a couple that can readily lose 3/4 of their data. That will give us room to plan for a proper archival strategy.
When we clean up those tables, the database file size doesn't shrink but that can be done point-and-click or with a small script. BUT - I've read that shrinking tables can create tremendous index fragmentation. That, and the test I ran took nearly 10 hours. SO, the questions:
- Will SQLServer efficiently manage that database file? Do I _need_ to shrink that file?
- Can I simply monitor the total sizes of the tables in the database and as long as the sum of this well below the size of the volume, I'm OK?
My background is that I'm an EA who's getting back into being hands-on. So I'm not totally green, but I'm somewhat new to SQLServer (most of my past is *nix and OSS), so this has been a bit of an adventure!
Advice, thoughts, strategies and so on - all appreciated!