Re: restrict access to a database

From: Hari Prasad (hari_prasad_k_at_hotmail.com)
Date: 05/17/05

  • Next message: Bad Beagle: "Design information" 
    Date: Tue, 17 May 2005 12:08:40 +0530

    Hi,

    Since the SQL SERVER machine is in the clients place and DBA needs to
    perform administrative tasks ( BACKUP , RECOVERY , DBCC, REINDEX..),
    it is very difficult to restrict the DBA. Only way to restrict is change the
    OS Level admin password and SA password for sql server and do not hand it to
    client side DBA. In this case he can not perform any administrative tasks.

    Also, another requirement is that we do NOT want them to see the DB
    structures, the tables, the data in the Databse!!!!

    See Application roles in Books online.

    Thanks
    Hari
    SQL Server MVP

    "D.Rudiani" <rudi@www.com> wrote in message
    news:%23dJk2anWFHA.2448@TK2MSFTNGP12.phx.gbl...
    > Hi all,
    >
    > Okay, we've got a product which has SQL Server as the backend database.
    > The client has the product as well as the database.
    > But the DBA at the clients end messes up with the data & we are held
    > responsible (that the product is what is messing up the data & NOT their
    > DBA).
    > How can we prevent this,
    > ie. try to encrypt the database or restrict access to the database to the
    > DBA.
    > Also, another requirement is that we do NOT want them to see the DB
    > structures, the tables, the data in the Databse!!!!
    >
    > options,
    >
    > 1. Get them to install a new instance of SQL Server & NOT give the DBA or
    > anyone the password & have the password embeded in the application (thus
    > only the application can access the SQL Database).
    >
    > NOTE : THe product and the SQL Servers WILL have to be at the clients end.
    >
    > any other options?
    >
    >

  • Next message: Bad Beagle: "Design information"

    Relevant Pages

    • Re: Why not Access...?
      ... It well depends how the database is used, such as the data access work load, ... When using Jet database, either VB front-end or Access front/back ... On the other hand, a database server, like SQL Server, gives you a lot more ... > 9i just can't work on these machines, and my clients are having these ...
      (microsoft.public.sqlserver.server)
    • Re: Is SQL required for 15 users
      ... their own front-end mdb and the back end should be at least one mdb. ... database designer that was hired to fix this problem recommended that we ... Two clients are using Office 2000, ... recommend I roll-in a SQL server? ...
      (microsoft.public.sqlserver.server)
    • Re: Why not Access...?
      ... The first point is, yes, Jet, not Access, is a file based, Pseudo-RDBMS. ... Jet database will corrupt and become ... MS Jet/Access, MSDE, and SQL Server 2005 Express Edition. ... > I am developing a desktop application using VB as front-end for some clients> where the a large number of regular entries are done but there is a rare need> to delete old customers. ...
      (microsoft.public.sqlserver.server)
    • Re: Page Splits sec
      ... and available database size when you defrag. ... If you are right, the DBA will ... A first step can be to implement your suggestions on a test database and see ... If you know how SQL Server work, these things aren't really that difficult, ...
      (microsoft.public.sqlserver.server)
    • restrict access to a database
      ... we've got a product which has SQL Server as the backend database. ... But the DBA at the clients end messes up with the data & we are held ... THe product and the SQL Servers WILL have to be at the clients end. ...
      (microsoft.public.sqlserver.security)