There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
Securing SQL Server 2012
Hey guys!!
I must secure a sqlserver database. I've read quite a bit about certificates and key but being a newbie to security I'm lost.
I am using 2005 express and 2012 express.
Any help would certainly be appreciated.
Thanks,
Jerry
I must secure a sqlserver database. I've read quite a bit about certificates and key but being a newbie to security I'm lost.
I am using 2005 express and 2012 express.
Any help would certainly be appreciated.
Thanks,
Jerry
Who is Participating?
Securing the server can mean a lot of things. You mention certificates in your question which is really encryption, not really security. Are you trying to simply encrypt the database or are you trying to prevent access? Or both?
Technodweeb!!!!! Thanks for the post!!
My main goal is to prevent access to files with patient medical information that are contained in a sql server 2005 express database. How would be the best way to go about it?
Sorry I'm late answering but the bank screwed up my account and EE was not able to process my payment.
Thanks again!!
Jerry
My main goal is to prevent access to files with patient medical information that are contained in a sql server 2005 express database. How would be the best way to go about it?
Sorry I'm late answering but the bank screwed up my account and EE was not able to process my payment.
Thanks again!!
Jerry
With medical information you need to study up on HIPPA Compliance. I cannot advise you on this topic. As for good first steps to safeguard your data would be to store things that are sensitive in an encrypted fashion as you were speaking of initially.
For the best performance, you could encrypt the data before placing it into the data fields. This would happen on-the-fly and each computer in the network would never feel the performance hit. The other way to do it would be to encrypt the tables in the SQL database itself which will be a much bigger performance hit as every transaction would require an encryption or decryption process to occur. This requires Express 2005 or greater which you have. The only other option would be to encrypt the file system where the database files reside, but this will be even more of a performance hit as every filesystem read and write will be affected.
For the best performance, you could encrypt the data before placing it into the data fields. This would happen on-the-fly and each computer in the network would never feel the performance hit. The other way to do it would be to encrypt the tables in the SQL database itself which will be a much bigger performance hit as every transaction would require an encryption or decryption process to occur. This requires Express 2005 or greater which you have. The only other option would be to encrypt the file system where the database files reside, but this will be even more of a performance hit as every filesystem read and write will be affected.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month6 days, 7 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
So you are trying to prevent a person that might have copied the DB file from accessing the data within?
This means that you would need to use the methods found here:
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&sqi=2&ved=0CEYQFjAB&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F4%2F7%2Fa%2F47a548b9-249e-484c-abd7-29f31282b04d%2FSQLEncryption.doc&ei=5HePUtzcEJDg2wXnwoAQ&usg=AFQjCNHkAVvzLfb_qaOaqJxvVNiQCqDcHg&sig2=U9lVlHLj8HZu7qyXISYF2w&bvm=bv.56988011,d.b2I&cad=rjt
I would make certain you have an excellent and verified backup before you do anything with encryption. One ooops factor will render your DB useless. Practice this process on a standalone instance, even on another machine or better yet, in a virtual machine, this way you can test and if it does not work you can rollback and do it again till you get it right.