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 |
|
nathans
Aged Yak Warrior
938 Posts |
 Posted - 2005-06-27 : 15:51:04
|
| Guys,We have a 3rd party db in use in Production. This db is a contentManagement db that is fully administered via UI by the Business.In the past, the data team has been manually pulling backups and restoring them into DEV from PROD to keep the data bewteen the two current. It has since become a requirement to keep the data in sync on the hour.It seems wrong to me to configure transactional replication from PROD --> DEV... I know it is bad practice to couple the two so tightly.Any other suggestions? These are zero schema changes occurring and most data changes are updates, very few inserts/deletes. The db size is < 1 GB.I was thinking of configuring transactional repl with queued update son the hour? Thoughts?Yes, they want all non-type tables replicated. |
|
|
Thrasymachus
Constraint Violating Yak Guru
483 Posts |
Posted - 2005-06-27 : 16:02:17
|
| Your replication scheme is fine. Log shipping maybe? Nothing else really seems appropriate. On a dev server, why does the data have to be so current. There was a time when I was doing a fair amount of accounting programming and testing meant the numbers had to balance. So testing became a 2 step process. I made sure the query did'nt kill the server, and then I pushed it production to make sure my numbers came out. Or I made a snaphot of the data on to my test or local, ran their numbers and I tested my code against that.Sean RoussyPlease backup all of your databases including master, msdb and model on a regular basis. I am tired of telling people they are screwed. The job you save may be your own.I am available for consulting work. Just email me though the forum. |
 |
|
|
nathans
Aged Yak Warrior
938 Posts |
Posted - 2005-06-27 : 16:09:10
|
| >> On a dev server, why does the data have to be so current.Im not really sure... we dont interact with this data at all, well, up until now :) Like I said, its a 3rd party tool that the business has been using for a while to configure some aspects of the web content. Some of these things are html templates and css stylesheets, etc. I guess having out of date data, even by the hour, could severely jack up some other stuff.They have a process in place right now, a manual job that creates a backup and restores to the dev box... but I cringe when I think about them running through that every hour??!! |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2005-06-27 : 18:21:16
|
| I would start by asking them to write a detailed justification for this. At the very least you can find out exactly what they need this for and what the actual requirements are.Are they using the development server to run some production reporting? My guess is that this is not really needed. Maybe this is coming from developers?If they really need current data, there might be only one or two tables where it is needed. You might be able to configure some hourly feed to bring the data over to development.You could configure log shipping, but they may find it inconvenient to get kicked out of the database every hour while you roll the logs forward.CODO ERGO SUM |
|
|
|
|
|
|
|
|
Keeping DEV in sync with PROD