Search
Active

40
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 355238
Opened: 7/7/2008 10:06:11 AM
Access Restriction: Public
2
Workaround(s)
20
User(s) can reproduce this bug
Don't get me wrong. I think the new columns we've added to Object Explorer Details are very valuable and provide very quick at-a-glance insight into all of the databases on our server(s) (similar to what TaskPad used to do in Enterprise Manager).

However, many of the columns make the entire view useless unless you have permissions to view that data on ALL databases on the server. Which is never going to be the case when you are accessing your database in a hosted environment.

This is partially related to items 354322 / 354291 but I think this goes beyond the obvious error with columns like "Collation" when Auto-Close is enabled. You can see my rant about that here:

http://sqlblog.com/blogs/aaron_bertrand/archive/2008/07/07/a-little-management-studio-oops.aspx

While a lot of people work in closed environments, where they connect to SQL Server using sa or a domain admin account, a lot of people do not, and need this functionality to be more flexible.
Details (expand)
Product Language
English

Version

SQL Server 2008 Release Candidate 0

Category

Tools (SSMS, Agent, Profiler, etc.)

Operating System

Not Applicable
Operating System Language
US English
Steps to Reproduce
Connect to a remote SQL Server where you only have access to some of the databases on the instance. In Object Explorer Details, right-click the column header list and enable "Data Space Used (kb)".
Actual Results
An error message:

http://www.aaronbertrand.com/voodoo/db_list_error_message.gif

And an empty window.
Expected Results
A window with the list of all databases, and in the data space used (kb) column, actual data for the databases I have access to, and N/A for the databases I don't. Or at least, the list should show all information in the columns, but the rows should be restricted to the databases I have access to.
Platform
X64
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 7/8/2008 at 9:07 AM
Aaron - good catch. I'll keep this one to be fixed.

- Buck
Posted by KS2005 on 7/14/2008 at 7:45 AM
I work in a development environment where we have many servers with SQL running on them. Any given server may or may not be accessible at any given point. This sort of issue will be a big problem in this environment as well.
Posted by bobbydigiscale on 10/26/2008 at 2:04 PM
When will this issue be resolved? Any word on this?
Posted by MarkTab on 1/26/2009 at 4:37 PM
Thanks Aaron -- I received this error -- SSMS for 2008 connecting to a shared 2005 hosting environment
Posted by ModuleKev on 3/27/2009 at 6:56 AM
I've experienced this issue with two developers connecting to two different machines in the last week. We're slowly moving over to SQL 2008 from SQL 2000. If it weren't for people like Aaron and their blogs I could have spent days if not longer trying to get this sorted. Is a patch going to be made available or coming out in a new release?
Posted by Beer Will on 4/2/2009 at 6:18 AM
I have just spent 4 days trying to get my hosting provider to fix my connection problem, and it turns out to be this? This should be fixed as soon as possible. Surely it isn't that big a deal? Please MS, fix now.
© 2009 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement