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.

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
business people around a table and laptop
Oct 9, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 10: Dynamic Detection Gotcha #3

You can interject a SQL Server Job Step into your Jobs and have this new/injected Job Step do some checking for you. Here's a look at everything that’s involved in such an approach....More
Man holding a piece of paper with the word GOTCHA
Oct 7, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 9: Dynamic Detection Gotcha #2 3

Given that a USE statement is parsed before code is actually run, there are a few options that could be used as a around when it comes to detecting whether or not code should be run....More
iceberg
Oct 2, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 8: Dynamic Detection Gotcha #1 1

Learn about why the option of dynamically detecting whether or not to run a SQL Server Job at execution time is quite a bit more problematic than you might think....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) ×