Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Redundancy in SQL Server Expand / Collapse
Author
Message
Posted Friday, September 19, 2008 10:41 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, October 20, 2011 1:13 AM
Points: 7, Visits: 131

I want to develop a redundant system.For achieving this I have two machines(SYS1 and SYS2) each having SQL Server 2008 database,and my application running over it.This application connects to the SQL Server instance present on that machine.At a given point of time only one of the system is active and other passive.Both the database are true copy of each other.

In the active machine(SYS1) database transactions are made.I want these transactions to be replicated on the passive server(SYS2) whenever it is available.Similarly whenever the active server becomes passive(SYS1) and the passive becomes active(SYS2) the transaction done on SYS2 be replicated on SYS1 in real-time.

Will Transaction-Replication be a suitable method to achieve this?I want to achive this by using CODE or T-SQL as the databases and tables are dynamically created .
Post #572925
Posted Saturday, September 20, 2008 2:25 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 7:53 AM
Points: 42,822, Visits: 35,952
Have a look at database mirroring. It looks, from your requirements, that it would be a closer fit than replication


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #572954
Posted Saturday, September 20, 2008 2:51 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, October 20, 2011 1:13 AM
Points: 7, Visits: 131
Thanks..i had read about database mirroring but was quiet confused between mirroring and replication.Your confirmation to implement database mirroring will help me ... i will give it a try
Post #572962
Posted Saturday, September 20, 2008 7:03 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 7:53 AM
Points: 42,822, Visits: 35,952
Mirroring is more an 'automated' logshipping than it is similar to replication.

Replication (transactional) will give you a second server that's fully usable (read and write) that is slightly behind the publisher. There's no easy way to reverse the direction of the replication. It requires manual work to drop the existing publication and subscription and recreate in the opposite direction.

Mirroring gets you a secondary database that's inaccessible but is up to date (synchronous mirroring) or nearly up to date (asynchronous mirroring) with the primary. Changing which is active is very easy, it's a single command.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #572995
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse