blank query window- how to get?

In Sql Server Query Analyzer, to get a blank query window, it seems that I
must first edit an existing stored procedure, at which point the "New
window" button is enabled.
Is there a way to get an empty window without first having to edit another
query? If I launch Query Analyzer, I have an empty instance of the app..how
do I get a blank query window?
thx1. You must be connected to an instance of sqlserver.
2. [ctrl]+[N] should open a new window/connection to the connected instance.
-oj
"mrmagoo" <-> wrote in message news:eO$AWA6TGHA.4956@.TK2MSFTNGP09.phx.gbl...
> In Sql Server Query Analyzer, to get a blank query window, it seems that I
> must first edit an existing stored procedure, at which point the "New
> window" button is enabled.
> Is there a way to get an empty window without first having to edit another
> query? If I launch Query Analyzer, I have an empty instance of the
> app..how
> do I get a blank query window?
> thx
>|||that's my point...it doesn't.
I launch query analyzer, and pick the server. It connects.
By default it does open an empty query window. If I close that, there's no
way that I can see to get another one unless I edit another stored
procedure. THEN I can Ctrl + N to get as many new windows as I want.
"oj" <nospam_ojngo@.home.com> wrote in message
news:udqvtV6TGHA.224@.TK2MSFTNGP10.phx.gbl...
> 1. You must be connected to an instance of sqlserver.
> 2. [ctrl]+[N] should open a new window/connection to the connected
instance.
> --
> -oj
>
> "mrmagoo" <-> wrote in message
news:eO$AWA6TGHA.4956@.TK2MSFTNGP09.phx.gbl...
I
another
>|||When you close the last window, there is nothing left in "query window"
cache to use to reinitiate a new connection for another query window. This
is by design and would not be enhanced - QA is now replaced with Management
Studio (sqlwb) in sql2k5.
-oj
"mrmagoo" <-> wrote in message news:eGUfXo6TGHA.4740@.TK2MSFTNGP14.phx.gbl...
> that's my point...it doesn't.
> I launch query analyzer, and pick the server. It connects.
> By default it does open an empty query window. If I close that, there's no
> way that I can see to get another one unless I edit another stored
> procedure. THEN I can Ctrl + N to get as many new windows as I want.
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:udqvtV6TGHA.224@.TK2MSFTNGP10.phx.gbl...
> instance.
> news:eO$AWA6TGHA.4956@.TK2MSFTNGP09.phx.gbl...
> I
> another
>|||ok..thanks...
"oj" <nospam_ojngo@.home.com> wrote in message
news:eGk2Jk8TGHA.4900@.TK2MSFTNGP12.phx.gbl...
> When you close the last window, there is nothing left in "query window"
> cache to use to reinitiate a new connection for another query window. This
> is by design and would not be enhanced - QA is now replaced with
Management
> Studio (sqlwb) in sql2k5.
> --
> -oj
>
> "mrmagoo" <-> wrote in message
news:eGUfXo6TGHA.4740@.TK2MSFTNGP14.phx.gbl...
no
>|||"mrmagoo" <-> wrote in message news:eO$AWA6TGHA.4956@.TK2MSFTNGP09.phx.gbl...
> In Sql Server Query Analyzer, to get a blank query window, it seems that I
> must first edit an existing stored procedure, at which point the "New
> window" button is enabled.
> Is there a way to get an empty window without first having to edit another
> query? If I launch Query Analyzer, I have an empty instance of the
> app..how
> do I get a blank query window?
> thx
>
CTRL+O
or
Select File / Connect...
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||thanks!
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:eYLv$gEUGHA.2444@.TK2MSFTNGP14.phx.gbl...
> "mrmagoo" <-> wrote in message
news:eO$AWA6TGHA.4956@.TK2MSFTNGP09.phx.gbl...
I
another
> CTRL+O
> or
> Select File / Connect...
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>