locked
Sqlserver 2012 Database Access After Deploy RRS feed

  • Question

  • Hi Friends,

    Please I  to inquire that when we are deploying software solution to clients I want they could not access  sqlserver 2012 from backup is there any way to protect so no one can restrict the access of database after deploying solution 

    thank you.

    regards,

    asad


    asad

    Friday, January 20, 2017 8:06 AM

Answers

  • I' not sure what you want, but I have a guess. The owner/administrator of a computer can always access the SQL Server that is installed on that computer. If you deploy your application to a customers computer, since they are administrators, they can connect to the SQL Server as members of the sysadmin fixed server role, manage the backups, move data files, etc. For more information, see Connect to SQL Server When System Administrators Are Locked Out https://msdn.microsoft.com/library/dd207004.aspx If you are worried about your intellectual property, that's a matter for lawyers and your license agreement.

    If the clients are not administrators on the computers, you can prevent access by the clients. You can use TDE to encrypt the data files, and you can encrypt backups. (But admins of the SQL Server computer can reverse both of those.)

    There are various ways to configure client access without installing SQL Server on your client computer. The easiest is probably using Azure SQL Database so the clients are not admins. You can also host a SQL Server on your own network, and allow client access through your network.

    Sorry if this is not related to your question.


    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    • Proposed as answer by Olaf HelperMVP Friday, January 20, 2017 5:22 PM
    • Marked as answer by malikasad Saturday, January 21, 2017 10:12 AM
    Friday, January 20, 2017 4:04 PM

All replies

  • Well, your requirements are too complicated.

    - How do you deploy the software?

    - Do you want the client to be resricted from restoring a database backup file after the deployment?

    - You want to create a database with your deployment, but you do not want your client to access to the database?

    - You want to create a database and you want your client to access to the database but you do not want anyone to be able to restrict the access to any other user on the database?

    Please clarify, so that we can help.


    http://ekremonsoy.blogspot.com | http://www.ekremonsoy.com | @EkremOnsoy

    Friday, January 20, 2017 9:13 AM
  • I' not sure what you want, but I have a guess. The owner/administrator of a computer can always access the SQL Server that is installed on that computer. If you deploy your application to a customers computer, since they are administrators, they can connect to the SQL Server as members of the sysadmin fixed server role, manage the backups, move data files, etc. For more information, see Connect to SQL Server When System Administrators Are Locked Out https://msdn.microsoft.com/library/dd207004.aspx If you are worried about your intellectual property, that's a matter for lawyers and your license agreement.

    If the clients are not administrators on the computers, you can prevent access by the clients. You can use TDE to encrypt the data files, and you can encrypt backups. (But admins of the SQL Server computer can reverse both of those.)

    There are various ways to configure client access without installing SQL Server on your client computer. The easiest is probably using Azure SQL Database so the clients are not admins. You can also host a SQL Server on your own network, and allow client access through your network.

    Sorry if this is not related to your question.


    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    • Proposed as answer by Olaf HelperMVP Friday, January 20, 2017 5:22 PM
    • Marked as answer by malikasad Saturday, January 21, 2017 10:12 AM
    Friday, January 20, 2017 4:04 PM
  • yes I want to restrict client to access database and database backup will be our responsibility in addition I want to totally lock the database  after deployment no one can access if its possible, accept who has valid password.

    asad

    Saturday, January 21, 2017 12:52 AM
  • yes I want to restrict client to access database and database backup will be our responsibility in addition I want to totally lock the database  after deployment no one can access if its possible, accept who has valid password

    asad

    Saturday, January 21, 2017 12:52 AM
  • Then, Rick Byham has already answered your question I think. Please mark that reply as an answer if you also agree that it's the answer of your question.

    http://ekremonsoy.blogspot.com | http://www.ekremonsoy.com | @EkremOnsoy

    Saturday, January 21, 2017 6:58 AM
  • Ok let me Mark as answer

    asad

    Saturday, January 21, 2017 7:30 AM
  • thank you for reply, I got answer regarding database access, please I want to inquire about hosting sqlserver over azure i think its expensive further I its also required strong internet connect. As I am looking less costly and it should work with weak internet connection, please I am not about azure  its serving the both purpose, As I developed application in vb.net winforms and want use for multi location branches for small retail shops 

    asad

    Saturday, January 21, 2017 7:37 AM
  • Actually you have a chance to give it a try for 30 days for free. Here's the link.

    I think for many cases it's a good deal. Here's the Price Calculator to give you an idea about the pricing and possible costs of Azure.

    However, if your application is hosted on client sites and you need a good response time and without a good internet/network infrastructure, hosting your database on cloud does not sound like a good idea. Either you must host your application on the cloud with the databases or host your databases with your applications on the client site. If you designed your application as a web based one, it would not only be much easier to migrate to the cloud all together, but also the maintenance and scalability of the application would be much easier I think.


    http://ekremonsoy.blogspot.com | http://www.ekremonsoy.com | @EkremOnsoy

    Saturday, January 21, 2017 8:01 AM