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?
vnewman29Asked:
Who is Participating?
 
sventhanCommented:
0
 
sventhanCommented:
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.
0
 
vnewman29Author Commented:
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!!
0
 
vnewman29Author Commented:
Thank you so much.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.