Chris SkorlinskiMicrosoft SQL Server Escalation Services If you’re familiar with Microsoft SQL Server Replication technology you already know each Replication Agent has various parameters or knobs you can set via Agent Profile or SQL Agent job parameter. This series of posts provide insight into tuning Replication performance using these knobs. Following the 80-20 rule, 80%
Read More »
Content provided by Sateesh Yele, Microsoft SQL Escalation Services BOL/MSDN documents –Logscanthreshold as “internal use only”. https://technet.microsoft.com/en-us/library/ms146878(v=sql.110).aspx -LogScanThreshold scan_threshold Internal use only. Other blog postings imply how to adjust this setting for better Logreader agent performance. If you add this parameter to the Logreader SQL Agent command line and start the agent, Logreader agent will
Read More »
by Chris Skorlinski, Microsoft SQL Server Escalation Services Oracle Publishing, now deprecated in SQL Server 2014, provides ability to use Oracle server as a Transactional Replication Publisher to a Microsoft SQL Server subscriber. Oracle Publishing Overview http://technet.microsoft.com/en-us/library/ms151229.aspx This feature was as designed as an Oracle to Microsoft SQL Server migration tool. Other customers used Oracle
Read More »
ReplTip — Only one Log Reader can connect message when dropping a Publication by Taiyeb Zakir Sometimes when you try to drop a Transactional Publication using the GUI, you get the following error: Only one Log Reader Agent or log–related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you
Read More »
Jose Moreira B. Neto Microsoft SQL Server Escalation Services From SQL Server BOL we have: -ReadBatchSize Is the maximum number of transactions read out of the transaction log of the publishing database per processing cycle, with a default of 500. -MaxCmdsInTran Specifies the maximum number of statements grouped into a transaction as the Log Reader
Read More »