Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
d3ng
Yak Posting Veteran
83 Posts |
 Posted - 2007-09-24 : 03:30:50
|
| Hi experts, I would like to ask if it is feasible to limit the accessibility of an SA account in SQL 2005 in a specific database. The reason of doing this procedure is since we are deploying a package software to our client(s) we want to secure our own database to get tampered by our client(s). |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-09-24 : 04:38:42
|
You can't stop a user who has SA rights on a server being able to see everything in your database. Period.  So you will have to take other steps to secure your Intellectual Property. Mostly those start with a legal agreement saying that you will hang, draw and quarter any client who steals your know-how  And then people get increasingly paranoid and start renaming tables and columns to random names etc. Waste of time IMHO, how hard is it to design a schema for a given scenario? Not that hard, and yours is no more smart in that regard than mine (about which I'm very protective!!) is.SProcs and Triggers can be encrypted...WITH ENCRYPTIONAS... but encryption was useless up to, and including, SQL 2000 - although it would keep a casual observer out, and prevent ad hoc changes to the code. I believe encryption is more robust in SQL 2005, but I haven;t checked Google for how many hackers boast of having bypassed it!!And beyond that you can put some critical code in your application, and encrypt some data within the database (again, from your application). The sort of thing that you might expect to do for, say, Credit Card numbers anyway.Kristen |
 |
|
|
|
|
|
Database Security