2004-10-25
1,554 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,673 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,458 reads
2004-10-07
1,424 reads
2004-10-06
1,434 reads
2004-10-04
1,533 reads
2004-10-01
1,653 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, and it wasn't one of those show stopper type problems. It's not about SQL, but we think it is on topic.
2004-09-30
5,305 reads
By Steve Jones
A customer was asking about tracking logins and logouts in Redgate Monitor. We don’t...
By Brian Kelley
Every year, the South Carolina State Internal Auditors Association and the South Carolina Midlands...
Data Céilí 2026 Call for Speakers is now live! Data Céilí (pronounced kay-lee), is...
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Comments posted to this topic are about the item Your Value from a Conference
Comments posted to this topic are about the item UNISTR Basics
What does this code return in SQL Server 2025+? (assume the database has an appropriate collation)
SELECT UNISTR('Hello 4E16754C') AS 'A Classic';
A:
B:
See possible answers