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 |
|
zsdave
Starting Member
4 Posts |
 Posted - 2010-02-15 : 10:48:49
|
| Currently, we have 2 SQL servers - Production and Test. Up to this point, we have basically 'refreshed' the TEST system every few weeks by doing a restore of .bak files from the production system (about 7 databases). However, now the amount of data is getting so large that this takes almost a day (and if something goes wrong, well you get the idea). What would be the best way to design this so that the Test system would be constantly (or more frequently) updated, yet could be worked without too much administrative involvment? |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-02-15 : 11:18:11
|
| Some earlier questions which might be relevant - if not ask further here please!http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=139826http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=139445P.S. Actually that second link is about rolling out changes made on DEV / TEST to LIVE - probably not relevant to your question |
 |
|
|
|
|
|
Test System