Share this Postby 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
Read More »
Share this PostI came across a great posting by Laurentiu Cristofor [MSFT] called “SQL Server 2005: How to regenerate the same symmetric key in two different databases”. I modified his “column encryption”example slightly to include DecryptByKey and reposted it below. The sample wraps in blog posting but is readable after you paste it into SQL
Read More »
Share this PostI recently needed to move a Transactional Replicated table to a new File Group. There are a couple of documented Schema changes that can break Replication. http://msdn.microsoft.com/en-us/library/ms151870(SQL.90).aspx However, I found most problems are solved if I first ensure all data between all peers/subscribers is synched, “no replicated transactions”, before making schema change, then
Read More »
Share this PostWhile assisting a customer with a SQL 2000 Replication configuration on Windows 2003 we need to reference the \ReplData folder as a Driver Letter. With help of Rick Rieser and Ryan Mangipano from Microsoft Windows Support team we had a simple elegant solution; Windows subst command. — Example below creates an alias V:
Read More »
Share this PostJosé Moreira Neto Microsoft Escalation Engineer I ran into an issue where the customer was complaining that Merge Replication was generating “fake” conflicts. This customer has a straight SQL Server Merge Replication with no filters where the only non-default setting is the use of the Microsoft Maximum Conflict Resolver a very specialized feature
Read More »