Step by Step Configuring Transactional Replication in SQL Server 2008 R2

Step by Step Configuring Transactional Replication in SQL Server 2008 R2

There are 3 steps involved for Configuring the Transactional Replication:

1.Configuring the Distribution Database.

A database which contains all the Replication commands. Whenever any DML or DDL schema changes are performed on the publisher, the corresponding commands generated by  SQL Server are stored in the Distribution database. This database can reside on the same server as the publisher, but it is always recommended to keep it on a separate server for better performance. Normally, I have observed that if you keep the distributoion database on the same machine as that of the publisher database and if there are many publishers then it always has an impact on the performance of the system. This is because for each publisher, one distrib.exe file gets created. 

2.Creating the publisher.

The Publisher can be referred to as a database on which the DML or DDL schema changes are going to be performed.

3.Creating the subscriber.

The Subscribers the database which is going to receive the DML as well as DDL schema changes which are performed on the publisher. The subscriber database normally resides on a different server in another location.

How it works

Transactional replication is implemented by the Snapshot Agent, Log Reader Agent, and Distribution Agent. The Snapshot Agent prepares snapshot files containing schema and data of published tables and database objects, stores the files in the snapshot folder, and records synchronization jobs in the distribution database on the Distributor.

The Log Reader Agent monitors the transaction log of each database configured for transactional replication and copies the transactions marked for replication from the transaction log into the distribution database. The Distribution Agent moves the initial snapshot jobs and the transactions held in the distribution database tables to Subscribers.

Configuring the Distribution Database

Creating the Publisher

Creating the Subscriber

Windows 2012 No Remote Desktop License Servers Available

Customer site is running Windows Server 2012 Essentials and a Windows 2012 Terminal Server. User contacts me to report that she was unable to connect into the Terminal Server from Remote Web Access (RWA). I tried, and got the same error message when I tried to access the Terminal Server:

The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator

I knew it was not an RWA issue because I could RWA into the 2012 Essentials server. A quick search and I found a post that indicates that there is a bug with 2012 RDS session hosts where they will not look to the licensing server for CALs when the grace period ends. Although I would like a permanent fix, the following solution resolved the crisis at hand.
The solution is to delete a specific registry key relating to the grace period, and then reboot the server.

1. Open up the registry editor on the Terminal Server
2. Browse down to: HKLM\System\CurrentControlSet\Control\Terminal Server\RCM
3. Make a backup copy of the GracePeriod registry key
4. Then you can Delete the GracePeriod registry key
   
5. Note: if you are not able to delete the key, you need to give yourself permission:
   Right click on the GracePeriod key and assign ‘full control’ permission to the administrator account.
   You should then be able to delete the key.

 Please see below step....

Step 1

Step 2

In the Permissions window that appears, Click Advanced.

Step 3

Click the Owner tab and Select your username from the list.* Now Check the Replace owner box and Click Apply. (Yes! This is one of the few instances where the Apply button is actually useful!)
*If your username is not on this list Click Other users or groups and manually add it.

Step 4

Click the Permissions tab and then the Add button.  In the Select User window Type your username into the white box and Press OK.

Step 5

A new Permission Entry window should pop-up; just Check the Allow Full Control box and Click OK.

Step 6

Back on the previous window, your username should be on the list with Permissions set to Full Control.  Now all that is left to do is to save and exit all open windows by Clicking OK a couple of times.





6.Reboot the server and check it out.