Share this PostTaiyeb Zakir Microsoft SQL Server Escalation Support Services When replicating identity columns https://docs.microsoft.com/en-us/sql/relational-databases/replication/publish/replicate-identity-columns  and using Auto Identity management, you need to make sure ranges are defined properly. The default “ranges” for automatic identity range management, while good 20 years ago, may need to be tuned for today’s higher workloads. Share this Post

Share this PostCustomer asked: “We need to reload a table weekly\nightly, batch job takes few minutes, but Replication takes long time to move the batch changes to Subscriber, how can we speed this up”? If Subscriber is mirror of Publisher, perhaps Replication is the wrong technology! A better solution may be to configure the database
Read More »

Share this PostChris SkorlinskiMicrosoft SQL Server Escalation Services Customer encountered transaction log growth for a Published SQL Server 2016 database while nightly refreshing Azure SQLDB. We discovered the default publication setting “replicate_dll” was still enabled. SELECT [description],[name],[replicate_ddl] FROM <your published database>.[dbo].[syspublications] description name replicate_ddl —————————————————— ———- ————- Snapshot publication of database ‘AdventureWorks2014’ Customers 1 (1
Read More »

Share this PostI hope this blog posting will provide some clarification into the MSDN article providing steps on how to initialize a transactional subscription from a backup. https://msdn.microsoft.com/en-us/library/ms147834.aspx First I want to clarify the @backupdevicename parameter. The article reads like the “DISK = “should be included in the parameter, it should not. For a physical
Read More »