Re: encrypted value storage
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 21 Feb 2008 15:19:22 -0800
Mike C# (xyz@xxxxxxx) writes:
That's true, I forgot about the ANSI_PADDING setting. As long as SQL
Server doesn't try to do any type of collation conversions on the binary
data, he should be OK with ANSI_PADDING on then?
I don't know. I can't think of any problems that could lead to data
loss, but I don't feel like putting two fingers on the bible and say
"It will work".
I can see problems for innocent GUIs who think the column has character
data, and then are smacked in the face by a NUL character, but that is
not any major concern.
And, in case it was not clear from my post, ANSI_PADDING OFF is a killer
for encryption also with binary columns.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: encrypted value storage
- From: Mike C#
- Re: encrypted value storage
- References:
- encrypted value storage
- From: bill
- Re: encrypted value storage
- From: Mike C#
- Re: encrypted value storage
- From: Erland Sommarskog
- Re: encrypted value storage
- From: Mike C#
- encrypted value storage
- Prev by Date: Re: An issue with SQL 2005 and Kerberos...
- Next by Date: Re: encrypted value storage
- Previous by thread: Re: encrypted value storage
- Next by thread: Re: encrypted value storage
- Index(es):
Relevant Pages
|
