New answers tagged

1

As of January 29th, Microsoft SQL Server supports TLS 1.2 for SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 and SQL Server 2014 and major client drivers like Server Native Client, Microsoft ODBC Driver for SQL Server, Microsoft JDBC Driver for SQL Server and ADO.NET (SqlClient). Blog post about the release: ...


1

If I'm not mistaken, the fingerprint is a hexadecimal number. That means you could store it as a binary number, since two hexadecimal characters can be represented by a single byte, making a 32-character hexadecimal string = 16 bytes. Here's the documentation on binary and varbinary data types for MySQL 5.7 (I don't have a test environment handy). I do ...


1

If you have SQL Server Standard edition then you do not have Encryption built into the product. You have other options as the articles you reference mention, but they require work on your part to implement. I think the confusion is where you are seeing that you can implement column/cell encryption using Enterprise edition OR through alternative methods. ...


0

Well I totally agree with the concerns raised by earlier answers in this post but as far as your actual query is concern, the following method can be adapted You may introduce insert/update triggers to encrypt data and do the encryption stuff. You may also trim the actual data iin current table to just keep the last 2 digits for card or SSN or whatever you ...


1

(OK, this is not an answer. Rather it is a warning that the question reflects a need for far more research.) Lock your doors, but don't bother to lock your windows. If you have a laptop with Social Security Number on it and it gets stolen, it won't matter if the data is super-duper-encrypted -- the decryption key is sitting somewhere in the laptop! You ...



Top 50 recent answers are included