October 21, 2008 at 8:08 am
What is the best strategy for data retention given that a newer version of SQL Server is available every 3 years.
For example, if I have a database on SQL 2000 and need to retain it for 10 years for regulatory compliance, if after 9 years, am asked to restore the database, we are probably going to be on SQL 2015 at that point. SQL 2000 may or may not be available / supported on newer Windows platforms.
Has anyone encountered this? If so, what was the course of action?
What are some of the data retention policies that other DBA's follow when data needs to be retained for several years after the system has been decom'd?
October 21, 2008 at 8:35 am
Well SQL 2005 supports 6.5 versions, which are 10 years old. however I'm not sure of the upgrade / restore policy.
Honestly what I've done in the past is archive the media as well. We used to keep yearly tape and we'd put on there the installation folders for SQL versions as well as the various Service Packs. Sometimes you need to get back to specific SPs to reinstall/setup a particular backup. there was a time that we had v6.5 (along with SP1, 2, 3, 4) and v7 (sPs 1, 2, 3, 4) on a backup tape.
October 21, 2008 at 8:41 am
However, this would be based on the assumption that the hardware and the OS platform will support SQL 2000 after another decade.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply