Is this possible? Even SUPERADMIN should not be able to look up the data in a schema.

  • How would I acieve the following scenario

    1. You have a SQL*Server database for your application.

    2.  It has a schema

    3. What you want to do is a SYSADMINISTRATOR could go and setup the skeleton of the database.

    4. You would setup the schema and the tables and the data by running scripts.

    5. When SYSADMIN/DBA logs in back again you do not want them to be able to access this schema or change any data.

    6. But you still want the DBA to be able to access the DB itself to do backups and other maintenance.

    To Add to the Above here are some additional points.

    1. We want the scripts to create minimum 2 users for the Database when deployed on the SQL Server Environment of the Client.

      1. LRRDBA account who has the similar privileges as a “sa” account of a SQL Server, and as you rightly pointed out this user will be used to administer our Specific Database instance. He might not have the privileges to do the maintenance task’s for other database Instances.
      2. LRRUser account who has the privileges and can do DML but not DDL

  • you need to understand the difference between roles, users and permissions. This is well covered in BOL.  I'm not sure you understand these concepts so maybe a training course would be useful. I'm sure there's been a couple of articles about user accounts for 2005 written on the site, but to be honest what you're asking would be too lengthy to put in a post and would struggle in an article.

    Sysadmin can always administer, that's the point - I'm not quite sure where you're going unless you're developing a database app as a third party and don't want the client to have rights ( which is very very tricky ) especially with the designated requirements.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply