2007-06-12
1,281 reads
2007-06-12
1,281 reads
2007-06-11
1,419 reads
2007-06-07
1,309 reads
One of the more interesting new features with SQL Server 2005 is the native encryption built into the product. Expert SQL crpytographer, Michael Coles, brings us a look at the symmetric keys in SQL Server 2005 and how they can be used to encrypt data and be secured by a certificate.
2007-08-24 (first published: 2007-05-11)
54,575 reads
2007-04-17
1,137 reads
2007-04-12
1,357 reads
2007-04-06
1,276 reads
2007-03-29
1,060 reads
SQL Server 2005 has greatly changed the security paradigm for SQL Server DBAs. The sa account still exists, but for many tasks
you can now avoid using it. New author Ken Johnson brings us some ides for properly securing this highly privileged account.
2008-02-20 (first published: 2007-03-14)
16,605 reads
2007-03-13
1,479 reads
By HeyMo0sh
As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...
By Steve Jones
AI is everywhere. It’s in the news, it’s being added to every product, management...
By Vinay Thakur
RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...
Hi, ssms is free here. I can think of other reasons to do this...
I've written some documentation on using different Markdown types of files on GitHub. It's...
Comments posted to this topic are about the item Not Just an Upgrade
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers