Results 1 to 8 of 8
  1. #1
    Join Date
    Jan 2006
    Posts
    54

    Unanswered: Hide Other Databases

    I am creating several logins for different databases that sit on the same server.

    Each user will have access to 1 database and none of the others

    After creating 1 login, I tested it to see if the denyreader works - However, I can still physically see the other databases themselves - I can't access any of the databases - is there a way of hiding the databases completely that I shouldn't have access to?

  2. #2
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    1) Create a login
    2) Grant it access to only one database
    3) Completely ignore the other databases
    4) Log out
    5) Log in using newly created login
    6) You should be good to go

    -PatP

  3. #3
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Created the login as sa?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  4. #4
    Join Date
    Jan 2006
    Posts
    54
    Quote Originally Posted by Pat Phelan
    1) Create a login
    2) Grant it access to only one database
    3) Completely ignore the other databases
    4) Log out
    5) Log in using newly created login
    6) You should be good to go

    -PatP
    This prevents the user from accessing any other databases, but they are still able to physically see other database names (which I want to prevent)

  5. #5
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    So they can see a name...what's the big deal?

    Create separate instances if it's so important, 1 db per instance
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  6. #6
    Join Date
    Jan 2006
    Posts
    54
    Quote Originally Posted by Brett Kaiser
    So they can see a name...what's the big deal?

    Create separate instances if it's so important, 1 db per instance
    That's overkill for something I hoped would be built in.

    As for seeing the name - They can see what else is being hosted on the same server.

    They see other DB's and then want access themselves

    Cheers for the helpful reply

  7. #7
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Quote Originally Posted by michaelro
    This prevents the user from accessing any other databases, but they are still able to physically see other database names (which I want to prevent)
    No. I just tried with SQL2000, SQL2005, and SQL2008. The newly created login can only "see" the databases that they have access to when they use the Microsoft tools.

    -PatP

  8. #8
    Join Date
    Jan 2006
    Posts
    54
    Quote Originally Posted by Pat Phelan
    No. I just tried with SQL2000, SQL2005, and SQL2008. The newly created login can only "see" the databases that they have access to when they use the Microsoft tools.

    -PatP
    Must be doing something wrong then....

    I followed these steps:
    1) Login to Server with windows authentication (Using MSSM Studio 2008)
    2) In Security / Logins Right Click and Select New Login
    3) Create SSA Login
    4) Change Default DB to required DB
    5) In User Mapping Select Required DB and default Schema to dbo
    6) Close down SQL Server and login as new user

    I can still see all of the other databases on the server

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •