A couple bugs or pita's in Em 2005

[jsteph]

Hello all,
In EM 2005 (or Object Explorer, Management Studio, whatever the term of the day is) there are a couple of quirks that I'm wondering if someone can point me to settings for, or at least tell me we're just stuck with it this way:

1.It seems that it takes much, much longer to connect than the old (2000) version, and it also seems that it must re-connect every single time I do 'New Query' or go into design-view of a table. Is there some auto timeout setting I might change, or a lazy-close option?

2. When I've expanded a database for instance, and am, say altering tables, building sp's, whatever, sometimes I'll click on 'New Query' to do some other work on that data. Instead of defaulting to *the database I'm working in*, it defaults to master. Is there a setting to wake this thing up and help it at least default to a database that I'll actually be working in?

Thanks for any info,
--Jim

 

[onpnt]

1.It seems that it takes much, much longer to connect than the old (2000) version, and it also seems that it must re-connect every single time I do 'New Query' or go into design-view of a table. Is there some auto timeout setting I might change, or a lazy-close option?

This is an added security measure which I think is a good one. If you save the login information though it will not ask you repeatedly. Simply check "Remember password" (or something to that effect)

2. When I've expanded a database for instance, and am, say altering tables, building sp's, whatever, sometimes I'll click on 'New Query' to do some other work on that data. Instead of defaulting to *the database I'm working in*, it defaults to master. Is there a setting to wake this thing up and help it at least default to a database that I'll actually be working in?

This hasn't changed at all from the previous versions of SQL Server. This is the default database specified in your login. In order to alter this you change that value. If you are (hopefully not) using something like sa then it will always be master as the default.

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[jsteph]

onpnt,
Thanks for the reply. I do check the Save Password, and it doesn't ask me, though it does pop up the window and takes a while to connect.

I understand about the default database, but it just seems like a good user-friendly thing to look and see the last db that was being worked in, and use that...

...being that this is from the company that reads over your shoulder when writing a Word doc, and pops up paper-clip-guy with help based on the type of letter it assumes you're typing...
--Jim

 

[onpnt]

being that this is from the company that reads over your shoulder when writing a Word doc, and pops up paper-clip-guy with help based on the type of letter it assumes you're typing

That is fairly far fetched of a comparison. Yeah, Microsoft produces these two products but comparing the functionality of the user interface to a enterprise database server and word is a bit off. I'm sure someone on the team that developed SQL Server 2005 like Ken Henderson would be slightly offended his product and all his work was compared to a user application like a word processor.

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[jsteph]

Understood...I was being facetious. But in general MS tends to go for a homogenized feel throughout their apps, and this would fall under a 'context-sensitive default'.

And, for the sake of friendly rejoinder to the Ken Henderson argument...I'm sure a CEO might feel offended that the app in which he pens his billion-dollar decisions is compared to a lowly database where his greasy widget inventory is stored. It's all in the point of view...
--Jim

 

[mrdenny]

1.It seems that it takes much, much longer to connect than the old (2000) version, and it also seems that it must re-connect every single time I do 'New Query' or go into design-view of a table. Is there some auto timeout setting I might change, or a lazy-close option?

It so take a while to open the new window. That's probably do to the fact the GUI is not a .NET app and .NET apps typically take longer to open than c++ apps do. This is actually the same way that QA worked in SQL 2000 and earlier. Each new window logges into the database seperattly.

2. When I've expanded a database for instance, and am, say altering tables, building sp's, whatever, sometimes I'll click on 'New Query' to do some other work on that data. Instead of defaulting to *the database I'm working in*, it defaults to master. Is there a setting to wake this thing up and help it at least default to a database that I'll actually be working in?

If the object explorer is the active window when you click New Query it will use what ever database you are in. If a query window is the active widow when you click on New Query then it uses your default database as the database to drop you in to.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com