- Snapshot Replication
- Transaction Replication
- Merge Replication
- Heterogeneous Replication: Replicate to other DBMS.
Replication Data Conflict
- Duplicate primary key
- Update conflict
- Update non exist data
- distrib.exe: use for distributor
- snapshot.exe: use for snapshot replication
- logread.exe: use for transaction replication
- replmerg.exe: use for merge replication
- qrdsvc.exe: use when configure as queued updating option within Transaction Replication
SQL Server Agent is required for setting up the replication. ( It is suggested to configure for start automatically.
We can use SSMS’s wizard to generate the replication script.
Create the Distributor , Distributor database
In the sample script below, I created the distributor database name “distribution” and using the network path to store the replication data.
Configures publisher to use the distribution database.
Other Store procedure to check Distribution DB
How to fix “SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported.”
Per Microsoft responds from here http://connect.microsoft.com/SQLServer/feedback/details/365761/sql-server-replication-requires-the-actual-server-name-to-make-a-connection-to-the-server It is by design. We have to use HOSTNAME\MSSQLNAME
However, I still got this in my lab environment. The main reason is I rename my windows server name after I install the SQL Server. Check the MSSQL Server Name from below Query, It is still set as old server name.
Drop and re add the server name. SQL Server need to be bounce to make it effective.