September 4, 2019 at 3:59 pm
I'm creating a stored procedure for Archive data from source db to archive db and we have more than 100 parent and child tables in Source db
Some tables does not have date columns but they are having relation with some non-date column. Can I skip them from archiving after 1st load? They are lookup tables or do I need consider all of them.
September 5, 2019 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
September 5, 2019 at 6:53 pm
It really depends and we can only guess without knowing all the details of the archiving process and how the archive database is going to be used. Often, lookup tables need to be handled differently. From what you described before, the archiving usually involves moving the data to another database and deleting from the production database. So you need to ask yourself things like if you really want to delete the data from production. How is the archive databases used and do you need the lookup table. Is the lookup data going to be updated and how does that impact the archive database.
Sue
September 6, 2019 at 4:48 pm
If we store backups, can we just delete records from source based on the business condition to improve application performance ?and if they need deleted data we can restore database to any other SQL instance and get the data? How is this different from Archiving?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply