Share this PostThe Microsoft SQL Server Support team uses various scripts to collect Replication and Performance data from customer’s SQL Servers. These scripts extract data into either text files or into temporary databases which are then backed up and sent to Microsoft SQL Engineer for analysis. Below are links to some of these common data
Read More »
Share this PostHave you seen errors like these below when attempting to run SQL Replication Wizard or start a SQL Agent job? TITLE: Microsoft SQL Server Management Studio —————————— SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022) SQL Server blocked access to procedure ‘dbo.sp_get_sqlagent_properties’ of
Read More »
Share this PostSateesh Yele | Microsoft SQL Server Support Symptom Distribution Agent is failing when connecting to subscriber server when replicating between cross domain servers. Consider this, you are setting up replication between 64 bit edition servers that are cross domain and the Distribution Agent is failing with the following error in Replication Monitor. The
Read More »
Share this PostSQL Replication allows you to replicate user-defined Stored Procedures code to subscribers similar to replicating tables. When the sp is modified, the new schema/script is transferred to the subscriber. This ensures all subscribers have the most recent version of the SP. Transactional Replication also allows you to setup a subscriber using a backup
Read More »
Share this PostBelow are cause and recommendation for the SQL Replication LogReader error “The specified LSN (…) for repldone log scan occurs before the current start of replication in the log (…).’. When the LogReader starts, it verifies the Last Distributed transaction (last transaction in msrepl_transactions) still exists in the transaction log. This confirms the
Read More »