January 4, 2012 at 12:33 am
Hello Sir,
I am creating an application in which I am consuming Sql Server Database. Now I want to protect my database from unauthorized used of database. No one can take back up of my database or restore it or can’t attach mdf file in sql server on another system and no one can see schema definitions of the database.
Please tell me how it is possible.
January 4, 2012 at 1:42 am
I assume you are somewhat new to SQL Server, so here are a few good links to get you started.
http://www.sql-server-citation.com/2009/05/how-to-secure-sql-server-sql-server.html
http://www.sql-server-performance.com/2002/sql-security/
http://searchsecurity.techtarget.com/news/873207/Top-10-SQL-Server-security-blunders
http://www.bradmcgehee.com/2010/09/sql-server-security-checklist/
http://sqlsecurity.com/FAQs/SQLSecurityChecklist/tabid/57/Default.aspx
Some material may be outdated, but you'll get the basics and a good understanding.
Let us know if you need additional info or have any questions.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
January 4, 2012 at 2:17 am
amitsingh308 (1/4/2012)
Now I want to protect my database from unauthorized used of database. No one can take back up of my database or restore it or can’t attach mdf file in sql server on another system and no one can see schema definitions of the database.Please tell me how it is possible.
Host the database and grant customers minimal permissions. That is the only way.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 4, 2012 at 3:42 am
I don't have access of customer's pc I have to hand over CD of the software to the client.
January 4, 2012 at 3:54 am
If the customer is putting the database onto a server that they control, they will have full control over that database and there is no way you can prevent that.
This problem is dealt with in two ways:
1) Host the database and give minimal permissions
2) Hand over the database and use licensing agreements requiring that the customer not reverse engineer, alter or distribute the database.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply