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 |
|
cat_jesus
Aged Yak Warrior
547 Posts |
 Posted - 2001-10-31 : 11:11:32
|
| We have a need in my shop to create a shadow of our production database. Our development server is in a different location than the prod server(different state even) and our "DBAs" and I use the term lightly seem to only want to use the backup/restore method to create our shadow. We have weekly batch jobs that run in the middle of the week and sometimes they fail. I suspect we have a DB or OS problem since we cannot recreate the problem here- days later after a 9 hour restore to our dev server.I would like this shadow DB to be no older than a day from prod. After doing some reading it seems that transactional replication might be a good solution in our case(bandwidth limitation). Also if we use replication of stored procedures a failed SP should theoretically happen on both the prod and shadow DB.What are the drawbacks to using transactional replication in a case like this and A. are there other options that would work better?B. How complex or difficult is this solution?Complexity is a big issue because our DBAs don't know SQL and don't understand indexes. Therefor a more complex solution will usually be passed over for a simpler solution.Cat |
|
|
|
|
|
Creating a shadow database