Hello,

i am using (well: want to use) SSMS Express 2008 to access our database on
the server of our hoster. Previously i did that with the 2005-version of
SSMS.

On that server there are several databases installed and we have only access
to two of them. When i connect to the server and open the node "Databases"
in SSMS i get an error message that i do not have the right to access some
of the databases (which is correct) and SSMS does not list ANY database in
that node, not even the ones that we are allowed to access.

Is it possible to create a connection to a single database, not listing the
others, with SSMS (i know the database names, so it would be no problem)? I
mean like in Visual Studio where i can add a connection to A SINGLE database
in the sever explorer.

Thnaks in advance,
Ralf

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote:

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote:

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote:

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote:

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote:

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote:

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote:

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote:

Connect to a different (e.g. local) server, open Object Explorer Details and
turn off all the unnecessary columns, particularly collation, last backup
date, last log backup date, data space used, owner (in case it is NULL), and
the like. Only enable the bare minimum here. These have tripped me up in
the past because several of them have to go each individual database in a
loop to get the results. Of course in a hosted scenario you very rarely
will have the rights to do so, and that is where the error message comes
from.

Please vote so that this will get fixed in a service pack.

http://connect.microsoft.com/SQL/fee...edbackID=35523
8

http://connect.microsoft.com/SQL/fee...edbackID=35432
2

http://connect.microsoft.com/SQL/fee...edbackID=35429
1

Also see here for some more background info (I complained about this pretty
loudly back in July):

http://is.gd/3EwP

Actually I just noticed that you are using SSMS Express, not SSMS. Does
SSMS Express have an Object Explorer Details pane? Sorry, I don't have any
system where I can load it myself to check if the fix will be the same...





On 10/7/08 9:17 AM, in article O7ESO8HKJHA.5704 (AT) TK2MSFTNGP02 (DOT) phx.gbl, "Ralf
Kaiser" <rk (AT) lingosmart (DOT) de> wrote: