March 18, 2002 at 10:59 am
I have a production server (SQL 7) that is used for an application in our imaging department. The application is mission-critical, so we are exploring ways of having a replicated backup server that is always ready to go should the first one fail. I've been doing a little reading and it seems like transactional replication might be the way to go if I want an exact copy that is always up-to-date.
Any thoughts? Pitfalls? Etc? I'm a total newbie so this is all new to me. I'd also appreciate any pointers to where I might find more info on doing something like this.
March 18, 2002 at 11:18 am
Typical latencies are 1-3 seconds unless the box is heavily loaded - and that could be either the publisher or subscriber. Nothing wrong with transactional replication, but you probably want to look at both log shipping and clustering, or some combination of the three.
Andy
March 18, 2002 at 11:20 am
Should I be looking at any third-party products to make this easier, or is everything I need built into SQL server?
March 18, 2002 at 1:55 pm
Pretty much everything is in the box. Log shipping only comes with Enterprise edition, but there are scripts for SQL7 that would do the same thing for you.
Andy
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply