2004-11-01
1,458 reads
2004-11-01
1,458 reads
2004-10-25
1,555 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,679 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,461 reads
2004-10-07
1,425 reads
2004-10-06
1,436 reads
2004-10-04
1,534 reads
2004-10-01
1,656 reads
By Vinay Thakur
As discussed introduction of Always Encryption blog and initial Encryption at rest as TDE...
By Vinay Thakur
Transparent Data Encryption(TDE): TDE was initially introduced in SQL Server 2008 Enterprise Edition; this...
By Steve Jones
Only a little break for me. I’m actually heading to Las Vegas today for ...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item The Problem Isn't Always Your...
Comments posted to this topic are about the item Identity Defaults
What happens when I run this code?
CREATE TABLE dbo.IdentityTest
(
id int IDENTITY(10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
See possible answers