Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-03-05 : 00:37:40
|
David writes "I have a SQL 7 database that has 3 tables: Jobs, Wins and Parts. The Jobs table has a JobNo primary key, which is the foreign key in Wins and Parts. The Jobs table also has a date field called InvDate. Over time this database gets quite large which effects performance so I want to put some type of automated archiving feature in place.
What I currently do is run a monthly job that executes some sql that copies all data that is more than 3 months old (based on the InvDate) to another 3 tables in the database called JobHistory, WinHistory and PartHistory and then deletes the same info from the Jobs, Wins and Parts tables. I then manually backup the History tables every 3 months and clear them.
Is there a better method to do all this? i.e. the monthly archiving and the manual backup process. I would also love the entire process to be automated.
Any help would be appreciated.
Thanks" |
|
|
|
|
|
Archiving information .