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,690 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,346 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
By Steve Jones
My life has some crazy travel stretches for sure. Between speaking, office visits, customer...
In Part 1, we saw how ‘Vamana’ represents vectors as nodes, connects them with...
I’m excited to announce the release of a new open-source project that fully automates...
Comments posted to this topic are about the item Optional Parameter Plan Optimization in...
Comments posted to this topic are about the item AI Experience Gap that we...
There is a table tmp_tab:
CREATE TABLE tmp_tab ( id int, val int );
INSERT INTO tmp_tab VALUES (1, 1), (2, NULL), (3, 3), (4, 4), (5, 5);You want to order the rows ids by the following expression:
ISNULL(val, id) + 1Which of the following queries produces the expected ordering and why? (Select all correct) See possible answers