vnewman29
asked on
Table Growth in SQL
I have an SQL database that has an activity table within that records all activity to the database. As you can image this table grows pretty fast. When we first got the database it was at about 3gig and after a year and half it is now at 13gig. I’ve talked with the vendor and they suggest that I periodically delete the old records and have no other options. My problem with that is that this is an HR database and I don’t want to lose any data in case they need to reference it. Is there any best practice on how to handle that table in SQL?
You can convert this as a partition(daily/monthly) tables and archive the oldest partitions to the other table. In this case you won't lose data also you keep the main table in control.
ASKER
This sounds like it will work; do you have any detail or where I can get more information on how to archive the oldest partitions to the other table?
Thanks!!
Thanks!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you so much.