Share this PostToday someone asked me how to “roll their own” SQL Replication Monitor to keep an eye on the health of SQL Server Replication. You’ve seen from my previous post I usually use a TracerToken job to monitor SQL Transactional Replication and query against MSmerge_sessions table for Merge Replication. However, you can also create
Read More »
Share this PostHave you noticed the SQL Server Agent Job RETRY is set to 2147? Well it is not, the dialog window just cuts off the rest of the digits. Actually the Replication Agent are set by default to retry 2147483647 times, once every minute. That is over 4000 years! 2147483647 = 35791394 Hours =
Read More »
Share this PostI wanted a quick way to execute a TSQL command against all databases. I was having hard time getting the sp_MSforeachdb to work and didn’t want to write a cursor, so I instead built a TSQL command which makes the commands I need to execute. Not fancy, but it got the job done.
Read More »
Share this PostFollowing a user database restore the database had orphaned users. We used TSQL commands below to build a list of sp_change_users_login commands in order to resynchronize database users with SQL logins. We then ran these sp_change_users_login commands to automatically fix the users. In SQL 2005 and SQL 2008 the SQL login is created
Read More »
Share this PostJosé Moreira Neto | Microsoft SQL Server Escalation Services sp_addpublication parameter: [ @immediate_sync=] ‘immediate_synchronization’ Immediate_sync has a default of FALSE. independent_agent must be true for immediate_synchronization to be true. Immediate_sync feature instructs Replication to maintain Snapshot BCP files and distributed transactions in the Distribution database should a new subscriber be created (or reinit)
Read More »