Hello.

I'm slowly coming to terms with the SQL Server Management Studio 2005.

I've really tried, but cannot figure out how to restrict the SSMS to
only look at one database.

Ideally what I want is for SSMS to open, connect to a server and set a
specified database as the root of the Object Explorer - this would
prevent the operator inadvertantly performing an operation on the
wrong database.

If setting the Object Explorer root is not possible, how can I at
least get SMSS to open to a particular database and have the object
explorer closed?

Thanks for your time.

First, you can set the default database for the users to be the
specified database. Next you can deny VIEW ANY DATABASE to the user.
Then make sure the user is DBO for the specified database, and that will
provide the filtering.

As far as hiding the object explorer, under Tools -> Options in SSMS,
you can set Environment at startup to open only a new query, or empty
environment. That will hide the object explorer.

--
Plamen Ratchev
http://www.SQLStudio.com

(ildam@moon.sm) writes:
> If setting the Object Explorer root is not possible, how can I at
> least get SMSS to open to a particular database and have the object
> explorer closed?

Create a shortcut for SSMS and add the parameters

-S server -d db -E

-E is for Windows Authentication. If you want to use SQL authentication,
use -U and -P instead.

To have Object Explorer closed on startup, use Tools->Options. There is a
setting on the first page.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Thanks to you both for your replies.

I assume from your replies that SSMS cannot change the root of the
Object explorer at all? This seems a very obvious requirement to me

> First, you can set the default database for the users to be the
> specified database. Next you can deny VIEW ANY DATABASE to the user.
> Then make sure the user is DBO for the specified database, and that will
> provide the filtering.

Unfortunately changing the permissions on any of the servers is not
viable - each of my users requires access to many SQLServers and
multiple databases on each one.

> Create a shortcut for SSMS and add the parameters
> -S server -d db -E

The command line parameters only open an SQL query window to the
specified database - what my users need is really a shortcut that
opens SSMS to the Summary view of the database so they can drill down
to see Tables, Views etc. This means they could have multiple SMSS
windows open, each restricted to looking at a single database.

(ildam@moon.sm) writes:
> Thanks to you both for your replies.
>
> I assume from your replies that SSMS cannot change the root of the
> Object explorer at all? This seems a very obvious requirement to me

There are many obvious requirements in SSMS that are not implemented.

The place to tell Microsoft about this is
http://connect.microsoft.com/SqlServer/Feedback/


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

On 3 Oct, 22:24, Erland Sommarskog <esq...@sommarskog.se> wrote:

> There are many obvious requirements in SSMS that are not implemented.
>
> The place to tell Microsoft about this ishttp://connect.microsoft.com/SqlServer/Feedback/


Done. Thanks again.