2004-11-01
1,459 reads
2004-11-01
1,459 reads
2004-10-25
1,556 reads
2004-10-18
1,532 reads
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,682 reads
2004-10-11
1,471 reads
Andy has some examples of not very high tech solutions that involve some technology behind the scenes, but the binding factor was that someone had to see the problem first. Not about SQL, but we think it is on topic.
2004-10-08
4,471 reads
2004-10-07
1,426 reads
2004-10-06
1,436 reads
2004-10-04
1,535 reads
2004-10-01
1,657 reads
Reading tutorials is fine. Shipping something is better. If you are trying to break...
By Steve Jones
We work hard at Redgate, though with a good work-life balance. One interesting observation...
By Arun Sirpal
Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...
Comments posted to this topic are about the item Liability for AI Errors
Hello , I would like to run a stored procedure on a secondary replica...
Comments posted to this topic are about the item Pro SQL Server Internals
I run this command to start SQLCMD:
sqlcmd -S localhost -E -c "proceed"At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version 2> goWhat happens? See possible answers