SQL Journals allows all SQL folks and other curious enthusiasts to post questions, concerns, experiences, and more. I am actively checking my journal and would promptly respond.
I have an etl process that refreshes the QA database every sunday at 2 am. This job takes 3 hrs to run. There is a 1 week latency issue here but sometimes my application development team needs the up-to-date data for their testing. What is the quickest way to refresh the database so that it doesn’t hold up application testing?
Hi Onye,
An ad-hoc simple resolution to get an up-to-date refresh of the database in your testing environment is to take a full backup of the database and restore to the test server. I recommend a “copy-only” full backup so it does not change the sequence of the restore of the full backups. For more information on this type of backup: https://msdn.microsoft.com/en-us/library/ms191495.aspx
Comments (2)
I have an etl process that refreshes the QA database every sunday at 2 am. This job takes 3 hrs to run. There is a 1 week latency issue here but sometimes my application development team needs the up-to-date data for their testing. What is the quickest way to refresh the database so that it doesn’t hold up application testing?
Hi Onye,
An ad-hoc simple resolution to get an up-to-date refresh of the database in your testing environment is to take a full backup of the database and restore to the test server. I recommend a “copy-only” full backup so it does not change the sequence of the restore of the full backups. For more information on this type of backup: https://msdn.microsoft.com/en-us/library/ms191495.aspx