Sameer Dandage

Sameer
Dandage

Sameer Dandage is a consultant with HTC Global Services. He is an MCDBA and a SQL Server DBA with more than five years of SQL Server experience.

Articles
Preparing Disaster Scenarios
How to prepare your transactional-replication setup for a disaster.
After the Crash 1
Transactional replication with queued updates (TRQU) can be a useful way to replicate data if you can tolerate some latency. Sameer Dandage examines the intricacies of backing up and restoring TRQU setups.
Login Security for TRQU

In transactional replication with queued updates (TRQU), the Distributor needs to connect to the Publisher and Subscriber. For security, the replication agents use a special SQL Server login that SQL Server creates during the replication setup for this purpose. This login, distributor_admin, has sysadmin permissions on all SQL Server instances involved in the replication process. You can see this login in the sysxlogins table on all servers.

Looking Under the Hood

Maintaining multiple database servers at multiple sites in active mode and closely synchronizing copies of the data on all servers is a challenge for any DBA. But as long as you can tolerate a little latency, one good option for keeping your data current at all locations is to use SQL Server’s transactional replication with queued updates (TRQU). In the first article in this series, “Queuing Up,” December 2003, InstantDoc 40567, I showed how to set up TRQU.

Queueing Up
If you need to maintain multiple database servers at multiple sites and synchronize all the data, SQL Server has a solution to make your job easier--SQL Server’s Transactional Replication with Queued Updates can help.
Stay in Control 1
Keep your complex software-development projects in check by building a version-control system that uses Enterprise Manager and Visual SourceSafe.
Upcoming Conferences

Register now to get the best rate available!

Digital Magazine Archives

Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.

 

From the Blogs
Sep 12, 2014
Sponsored

Managing a Healthy SQL Server Database: Three Principles We Overlook

In managing a database or sometimes numerous databases, we often get caught up in the day-to-day maintenance and lose sight of the other principles we know are critical to ensuring optimal performance. Here’s a quick refresher....More
Exclamation marke on yellow road sign
Sep 9, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 5: Setting Up Failover Alerts

Alerts represent a great way to take a proactive stance on being notified or alerted when something ugly, potentially ugly, or important happens on a SQL Server. On most servers that I manage, I typically deploy a whole bevy of different alerts....More
synchronize key on computer keyboard
Sep 5, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 4: Synchronizing Server-Level Details

When setting up HA or HA+DR solutions with SQL Server AlwaysOn Availability Groups, it's critical to remember that the basic unit of failover in these scenarios is the availability group (or the group of user-defined databases)....More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×