I wish to install a credit card applicatoin (ASP.Internet + SQL server 2005 express) in local network of some small enterprise for demoing it for time, however i likewise want nobody even sysadmin don't have any permission about this database and then any permission granting wants a safe and secure pass which i have . Among the finest my tables structure and relations and processes be hidden and encrypting the information don't have any advantage

I have to take more time about this article Database Encryption in SQL Server 2008 Enterprise Edition which i found out of this answer is-it-possible-to-password-protect-an-sql-server-database

but

1.I love to be certain and much more obvious about this since the other answer within this page states :

Yes. you are able to safeguard it from everybody except the managers from the server.

2.if this sounds like possible, the db need to be enterprise edition ?

3.can there be every other possible solutions and workaround with this?

4.basically use a new instance with my very own sa password , can one restrict other instances admins from affixing the mdf to their personal ?

thanks ahead of time

These folks can access your server or even the SQL Server instance regardless of what you need to do

  • anybody with physical accessibility server
  • domain admins from the network
  • anybody using the sa password
  • a home windows group with local admin and/or sa privileges (which suggests group policy etc)

You need to host your server off-site if you would like no-one to get at visit it.

It's that simple

In SQL Server, you can't "password-safeguard" a database - you skill is limit the permissions confirmed user or role has inside your database.

You are able to DENY anybody use of your database - but that is a little odd, since nobody will have the ability to utilize it....

That you can do a variety of stuff for your database tables and logins - but a sysadmin will invariably have the ability to circumvent individuals things and obtain access to the database. As lengthy because the sysadmin could possibly get his hands physically around the server, I do not think there's in whatever way to fully shut them out.

If you do not trust even your sysadmins, you've bigger problems.....

There's a number of different ways you can solve this issue.

  1. Host it off-site - I believe the simplest solution would certainly be to host it off-site. There's lots of cheap hosting that is shared available for you to use.

  2. Lock the sysadmins from that server. Presuming you've root access and just you utilizeOrrequire that server you can alter the root password and then any other passwords around the server.

  3. Do what you are presently doing and then try to make something secure even if somebody that should not connect has root accessibility server. By doing this sounds tricky and insecure even at best.

I've got a contribution for (3):

I am speculating (I would be wrong) you do not really have sensitive information inside your database, you want to allow it to be unfeasible for somebody from our network to make use of all of your stuff.

If that is the situation, you can simply make it harder to allow them to read your computer data by encrypting the information within the database and getting your (put together) code decrypt it before utilizing it.

By doing this, any sysadmin who's just interested in the information or really wants to change his hiscore to 13371337 won't want to undergo the problem of decompiling your code and/or cracking your file encryption (throughout your demo) as well as your (assumed) problem is going to be solved.

I've no clue if the can help you whatsoever, I suppose Among the finest to express you might like to have a look at the problem again. Because you can't keep your sysadmins from your stuff, you might want to have a different approach like which makes it less helpful for them.