Database Reference
In-Depth Information
5. All the tables included in the transactional replication must have the primary key
associated with the published table.
6. For peer-to-peer transactional replication, the distribution must be configured
on each node first and then database schema must be initialized to perform
snapshot processes.
Before you can configure replication, you must install it into the
servers that will participate in your replication topology.
If you have not already installed replication on all participating
servers, go back to the SQL Server Installation Center and add the
replication feature to your servers. It will also make the process of
configuring replication easier if you connect your Object Explorer
in SSMS to all the Data Engine services that will participate in your
replication model.
How to do it...
The following are the steps to administer the snapshot and transactional replication setup:
1.
Backup the publication database at the Publisher.
2.
Backup the distribution database at the Distributor.
3.
Backup the subscription database at each Subscriber
4.
Backup the master and msdb system database at the Publisher, Distributor
and Subscriber.
5.
All of these databases should be backed up at the same time. Backup settings for
Transactional replication are as follows:
To check if sync with backup is set on your publication or distribution
databases, execute the following command at the publisher or distributor
server instance:
select databasepropertyex('db_name', 'IsSyncWithBackup')
If the value is 1 , sync with the backup is set. If sync with backup is not set,
enter the following TSQL command to configure it:
sp_replicationdboption @db_name = 'db_name',
@optname = 'sync with backup',
@value = 'true'
Let us work on restore strategies within snapshot replication and
transactional replication. To restore publication database in snapshot
replication, restore the latest backup of the publication database.
 
Search WWH ::




Custom Search