Tag Info

Hot answers tagged

5

What you are seeing on net is mostly a copied advise where people actually want to say that "please don't make shrinking data file or log file a daily routine operation". Had it been so bad Microsoft would have removed it but it is still there and even most experienced DBA's and developer use it but they are aware about the after affects so they know what to ...


3

Shrinking database log file is necessary if log has grown out of control whether after a one-time data delete or where recovery model of the database is FULL and no log backups have been carried out. To reverse the effect of a one-time operation that caused unexpected log file growth are convincing reasons for shrinking a database\ database file. ...


2

My largest obstacle right now with Cassandra are the no-join, no order by (since everything is ordered by key for you), and mass update. If your current data structure depends on joins (or aggregation) to pull off the queries you need you won't find a nosql option that includes these. You do have some options: Consider reviewing your current data ...


1

Yes, it is still recommended not to shrink. If your data file goes up to 20 GB every quarter, then think about this: after you've shrunk it to 5 GB, you've freed up an extra 15 GB on the drive. What are you going to use that space for? Are you going to lease it out to someone temporarily, then kick them off the drive when your database starts to grow again? ...



Only top voted, non community-wiki answers of a minimum length are eligible