Database replication. 2 web servers, Master data source and also the 2nd reads - just

Say you have 2 data source web servers, one data source is the 'master' data source where all write procedures are executed, it is dealt with as the 'real/original' data source. The various other web server is data source is to be a mirror duplicate of the master data source (servant?), which will certainly be made use of for read just procedures for a particular component of the application.

Just how do you deal with establishing a servant data source that mirrors the information on the master data source? From what I recognize, the slave/readonly data source is to make use of the master db is purchase log documents to mirror the information deal with?
What alternatives do I have in regards to just how usually the servant db mirrors the information? (actual time/every x mins?).

0
2019-12-02 03:04:38
Source Share
Answers: 4

The response to this will certainly differ relying on the database web server you are making use of to do this.

Edit : Sorry, possibly i require to find out to consider the tags and also not simply the inquiry - i can see you marked this as sqlserver.

0
2019-12-03 04:43:43
Source

What you desire is called Transactional Replication in SQL Server 2005. It will certainly reproduce adjustments in close to live as the author (i.e. "master") data source is upgraded.

Here is a pretty good walk through of how to set it up.

0
2019-12-03 04:35:53
Source

From what I recognize, the slave/readonly data source is to make use of the master db is purchase log documents to mirror the information deal with? What alternatives do I have in regards to just how usually the servant db mirrors the information? (actual time/every x mins?).

This seems like you are speaking about log delivery as opposed to replication. Wherefore you are intending on doing though I would certainly concur with Jeremy McCollum and also claim do transactional replication. If you are mosting likely to do log delivery when the data source is recovered every x mins the data source will not be readily available.

Below is an excellent walkthrough of the distinction in between both. Depressing to claim you need to enroll in an account to read it though. =/ http://www.sqlservercentral.com/articles/Replication/logshippingvsreplication/1399/

0
2019-12-03 01:59:44
Source

SQL Server 2008 has 3 various settings of replication.

  • Transactional for one means read just replication
  • Merge for 2 means replication
  • Snapshot
0
2019-12-03 00:20:23
Source