"R Baker" <nospamx@nospamx.com> wrote in message
news:eZgV9pvUDHA.2192@TK2MSFTNGP09.phx.gbl...
> Is there a way to grant access to a SQL Server database while not
permitting
> connections via SQL Enterprise Manager. We find that it is showing all the
> database names (even those for which the connecting user has no
> access/permissions), and this is a security exposure.
>
> Thanks!
>
>

"R Baker" <nospamx@nospamx.com> wrote in message
news:eTyFtyvUDHA.1916@TK2MSFTNGP12.phx.gbl...
> "R Baker" <nospamx@nospamx.com> wrote in message
> news:eZgV9pvUDHA.2192@TK2MSFTNGP09.phx.gbl...
> > Is there a way to grant access to a SQL Server database while not
> permitting
> > connections via SQL Enterprise Manager. We find that it is showing all
the
> > database names (even those for which the connecting user has no
> > access/permissions), and this is a security exposure.
> >
> > Thanks!
> >
> >
>
> Ok, removing SELECT permission from the sysdatabases table in the MASTER
> database from the "public" role seems to do the trick, but this seems a
wee
> bit like overkill. Is there a more structured way. Ideally, users could
see
> the databases they had been granted access to.
>
>

"Kevin" <ReplyTo@Newsgroups.only> wrote in message
news:#xUO#nRVDHA.2156@TK2MSFTNGP11.phx.gbl...
> There is no supported way to do this, you found one way -
>
> Question: What is the specific requirement here, are you storing sensitive
> information in your database names?
>

>
> --
> ----------------------------------------------------
> The views expressed here are my own
> and not of my employer.
> ----------------------------------------------------
> "R Baker" <nospamx@nospamx.com> wrote in message
> news:eTyFtyvUDHA.1916@TK2MSFTNGP12.phx.gbl...
> > "R Baker" <nospamx@nospamx.com> wrote in message
> > news:eZgV9pvUDHA.2192@TK2MSFTNGP09.phx.gbl...
> > > Is there a way to grant access to a SQL Server database while not
> > permitting
> > > connections via SQL Enterprise Manager. We find that it is showing all
> the
> > > database names (even those for which the connecting user has no
> > > access/permissions), and this is a security exposure.
> > >
> > > Thanks!
> > >
> > >
> >
> > Ok, removing SELECT permission from the sysdatabases table in the MASTER
> > database from the "public" role seems to do the trick, but this seems a
> wee
> > bit like overkill. Is there a more structured way. Ideally, users could
> see
> > the databases they had been granted access to.
> >
> >
>
>

"R Baker" <nospamx@nospamx.com> wrote in message
news:eTyFtyvUDHA.1916@TK2MSFTNGP12.phx.gbl...
> "R Baker" <nospamx@nospamx.com> wrote in message
> news:eZgV9pvUDHA.2192@TK2MSFTNGP09.phx.gbl...
> > Is there a way to grant access to a SQL Server database while not
> permitting
> > connections via SQL Enterprise Manager. We find that it is showing all
the
> > database names (even those for which the connecting user has no
> > access/permissions), and this is a security exposure.
> >
> > Thanks!
> >
> >
>
> Ok, removing SELECT permission from the sysdatabases table in the MASTER
> database from the "public" role seems to do the trick, but this seems a
wee
> bit like overkill. Is there a more structured way. Ideally, users could
see
> the databases they had been granted access to.
>
>