2004-11-01
1,457 reads
2004-11-01
1,457 reads
2004-10-25
1,554 reads
2004-10-18
1,531 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,676 reads
2004-10-11
1,470 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,460 reads
2004-10-07
1,425 reads
2004-10-06
1,435 reads
2004-10-04
1,533 reads
2004-10-01
1,654 reads
By Steve Jones
It was neat to stumble on this in the book, a piece by me,...
Forgive me for the title. Mentally I’m 12. When I started my current day...
By Steve Jones
One of the things a customer asked recently about Redgate Data Modeler was how...
Comments posted to this topic are about the item Expanding into Print
Comments posted to this topic are about the item Downtime Caused by the Postgres...
Comments posted to this topic are about the item The String Distance I
In SQL Server 2025, what is returned by this code:
SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled. See possible answers