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 |
|
GrahamK
Starting Member
5 Posts |
 Posted - 2009-07-22 : 06:26:54
|
| Hi All,I have a question please about which architecture I should implement, and how I should go about it. We have two sites, which both have an SQL Server 2005 server on them. I want both databases to be concurrent with each other (mirroring??) but also if one should fail for some reason, it should fail over to the other site. Then if it were site 2 to fail, Autonomously site 2's users would need instant access to the database on site 1, and then vice versa.Any Help Appreciated.Graham |
|
|
ScottWhigham
Starting Member
49 Posts |
Posted - 2009-09-03 : 06:55:25
|
| You won't find that built into SQL Server. There are third party tools possibly to do this but what you're asking is very, very difficult. There are pieces of SQL Server that can handle individual requirements - merge or p2p replication for the "both databases to be concurrent" feature and then database mirroring (or log shipping) for the fail over. And there won't be "instant access" for your users no matter what - there will be some level of downtime.========================================================I have about 1,000 video tutorials on SQL Server 2008, 2005, and 2000 over at http://www.learnitfirst.com/Database-Professionals.aspx |
 |
|
|
|
|
|
SQL Server 2005 Multi-Site Architecture Question