If you allow users write access to replicated tables on the subscriber, you can run into cases where a record is inserted on the wrong server - which will result in a replication stopping error if the same primary key is later inserted on the publisher. Find out how to fix it without pushing a new snapshot.
2004-10-15 (first published: 2001-05-04)
9,688 reads
Need to make changes to table that is an article in a publication? Read this article to get step by step instructions on how to do it without doing a new snapshot!
2001-05-02
8,339 reads
This article describes how to create a Visual Basic application for merge replication that will handle both conflict and non-conflict changes between the affected tables.
2001-05-01
2,075 reads
A RAG pipeline that answers questions in the demo is not the same thing...
By Steve Jones
“A multitude of bad ideas is necessary for one good idea” – from Excellent...
Yesterday I gave a talk for MSSQLTips called “Building a DBA Agent for Your...
Comments posted to this topic are about the item Adding new column with DEFAULT
I've got a web application for my side business. I've added a SQL Server...
Comments posted to this topic are about the item Looking for New Blood
Which number will the COUNT() return after executing the following statements:
DROP TABLE IF EXISTS #test; CREATE TABLE #test (id INT) INSERT INTO #test (id) SELECT * FROM GENERATE_SERIES(1, 3) AS gs ; ALTER TABLE #test ADD flag BIT CONSTRAINT DF_#test_flag DEFAULT 0; go UPDATE #test SET flag = 0 WHERE id = 1 UPDATE #test SET flag = 1 WHERE id = 2 INSERT INTO #test (id) VALUES (4) SELECT COUNT(*) FROM #test AS t WHERE flag = 0See possible answers