sql server management studio

[scotspine]

i'll check that out s/cadet - once i've finished this iteration

weltchy tsk tsk

[Weltchy]

something about haste and speed comes to mind

Less Hash, more Speed?

PS - I am, in no way, endorsing Drug use!!!

[Spacecadet]

it sounds as though you've read the manual???

Thats not always such a bad thing

Seriously though, Query Analyser in Sql Server 2000 behaved exactly the same way and this behaviour was carried through to 2005 and 2008
Don't know about version 7 - I only ever did some basic admin work on that

[scotspine]

its not magically "switching" you just don't know how to use it!

it sounds as though you've read the manual???

[Spacecadet]

its not magically "switching" you just don't know how to use it!

The behaviour is perfectly consitant, predictable and documented

[Not So Wise]

If you know knew the amount of times I ran queries against "Master" by mistake on my home system because of the switching

Luckily have policy at work to always use "Use DBName"

[Spacecadet]

"it will open a session to which ever database you are currently connected to"

hmmmm..in theory, yes. i still think my copy of ssm studio has an attitude problem though.

try clicking on a db in the object explorer then click on new query
see which db you are connected to

then with the query window active click new query
see which db you are connected to

select a different db in the object explorer and click new query (whilst the object explorer window is still maintaining the application focus)
again see which db you are connected to

[scotspine]

"it will open a session to which ever database you are currently connected to"

hmmmm..in theory, yes. i still think my copy of ssm studio has an attitude problem though.

"use "dbname""

i know, i know. i ought to do this but sometimes....you just want to be productive and get on with things...something about haste and speed comes to mind

[Spacecadet]

when you click on new query (or hit control-N) it will open a session to which ever database you are currently connected to. This is not constrained to the query windows.

So if you were browsing the live system in the object explorer tree and the window focus was on there then SSMS will open a DB connection to the Live database.

Once you understand the behaviour you'll realise its not just switching... its doing what it is supposed to do and it does it very consitantly.

As JoJoGabor pointed out though - adding the use <dbname> will make sure your scripts are always diverted to the correct database (unless your running a partial section of the query by highlighting then executing)

[DimPrawn]

Just put the statement at the start of the script:

use "dbname"

WHS/WSS

[JoJoGabor]

Just put the statement at the start of the script:

use "dbname"

[scotspine]

this thing has a mind of it's own. it keeps switching the active database so that unless you're *really* careful, you can end up running a script against a database other than the one you think you are!!!!! grrrrrr