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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2003-09-11 : 07:46:08
|
| Colin writes "OVERVIEWWe have a client that requires certain Microsoft SQL 2000 tools, to be able to monitor, administer and replicate their MS SQL 2000 SP2 Databases. He has 285 SQL 2000 servers and 1500 users. All the SQL servers reside on Microsoft Windows 2000 servers Latest SP’s (NOT MS Advanced Server). Their Master Database is 7GB in size and they have 2 areas namely Production and Development on separate servers.They have requested that I assist them with their Administration and supply software packages necessary, to be able to Administer these MS SQL 2000 servers and clients and more importantly to do "real time" replication of their Master Database to a Disaster Recovery site, so if the Prod DBase goes offline, the DR site would be software set-up to take over automatically, I am looking for reasonably priced software to do this job - do you perhaps know of any names to research.Many Thanks" |
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2003-09-11 : 08:33:47
|
| Fault tolerance should be handled with clustering, not replication.Jay White{0} |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-09-11 : 12:34:20
|
| Replication comes with SQL Server 2000, but it is not the solution that you use for disaster recovery. Typically, log shipping is used. Log shipping is available in SQL Server 2000 Enterprise Edition. We use clustering and log shipping for our solution. Clustering allows problems and maintenance to occur at the same site. Log shipping allows the duplication of the databases to another site.Tara |
 |
|
|
|
|
|