Starting Query Analyzer

  • Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/yShlafman/startingqueryanalyzer.asp

  • Yakov,

    Like you said, there are several ways to get in to QA. One other method of starting QA that you didn't mention, and the one I tend to use the most, is to start it from within Enterprise Manager. By using the appropriate shortcut keys for the Enterprise Manager "Tools" and then "SQL Query Analyzer" menu options you can fire off QA with a combination of "Alt+T", "Q" keystrokes. This method has the added feature of using whatever credentials you are currently running EM with.

    Another method you could use would be to assign a "Shortcut Key" combination to the QA entry in your Program Files - this can be done by right-clicking the QA entry and looking under its properties. I don't actually have a shortcut key combination set up for QA but I have set up several others which save me time on a regular basis (e.g. Ctrl+Alt+W to load Word, Ctrl+Alt+X to load Excel, Ctrl+Alt+N to load Notepad, Ctrl+Alt+E to load Enterprise Manager...)

    I know it's personal preference but if I can ever find a way of doing things without a mouse, or any other pointing device, I will.

    Mark

  • Of course, there are other, MUCH simpler ways of adding shortcuts to your Quick Launch bar, and of opening the Run dialogue.

    First, shortcuts. Click on Start, and navigate to the program you want to add to Quick Launch (QL). Instead of the 6 steps to 'Send it to your desktop', then drag it from your desktop to the QL bar, just RIGHT click and drag straight from the Programs menu to the QL bar. When you relaes the mouse, select 'Copy To' rather than the default 'Move To' otherwise it will dissapear from the Programs menu.

    To launch 'Run', just use the 'WindowsKey + R' shortcut - much easier than adding another shortcut to the QL bar (WindowsKey + E also opens Explorer a great deal faster than using any menus).

    The command line switches were useful. Unless you try each Windows executable from a command line, it is not always obvious which support switches and which don't. Query Analyser supports several more of them too. Open the Run dialogue, and enter isqlw /? to get a full list.

    Regards

    Adam

  • After all these years as a dba, finally someone has shown me how to become a power user!

     

    Fantastic, thank you all!

  • This is what my start menu looks like

    Start Menu

     

    Windows Key followed by 1 Opens QA, Windows Followed by 2 EM.  I also have short cuts assigned on the Shortcuts, so I can press Ctrl + Alt + 1 for QA etc.

     

     


    http://glossopian.co.uk/
    "I don't know what I don't know."

  • One of my most used command-line switches is -C. This loads a previously saved configuration file. Comes in very handy when you have a couple of people working on a server via remote desktop and they each have their own favourite fonts

    Also, one little know tip for the Quick Launch menu, re-size the toolbar so that only the double arrows are visible, if you click the arrows a popup menu appears and you can select your shortcut from the menu. Below is a screenshot of how this looks on my home computer with the toolbar title visible.

    You can also create your own toolbars full of whatever shortcuts you need. Just choose "New Toolbar..." from the Toolbars menu. I have 4 on my work computer, "Quick Launch", "SQL Admin", "Development" and "Remote Desktops".

    --------------------
    Colt 45 - the original point and click interface

  • Being able to run Query Analyzer from the command line was worth the price of admission, that is the time I took to read the article. I will use that alot!

  • Another quick way would be to assign a combination of keys to the shortcut and then you could open it with ctrl-alt-q for example.

    You can do this by right clicking the shortcut, properties, short cut key.

    I use this technique a lot because I have a bad hand and moving from keyboard to mouse is difficult so I use keyboard shortcuts with keys I can press with the left hand.

     

  • Philcart

    Also, one little know tip for the Quick Launch menu, re-size the toolbar so that only the double arrows are visible, if you click the arrows a popup menu appears and you can select your shortcut from the menu. Below is a screenshot of how this looks on my home computer with the toolbar title visible.

    That would certainly save task bar space, especially if you have other tool bars. I can't get my QuickLaunch bar that small though - the smallest it will go is 3 icons wide. Is there some trick to make it smaller?

    You can also create your own toolbars full of whatever shortcuts you need. Just choose "New Toolbar..." from the Toolbars menu. I have 4 on my work computer, "Quick Launch", "SQL Admin", "Development" and "Remote Desktops".

    This is an excellent idea, especially the Remote desktop one (I often have 4 or 5 desktops open at any one time). You can then create a seperate .rdp file for each shortcut, to save the settings for that remote server, including the password (if you want to save it) for instananeous log in. Thanks!

    Incidentaly, as this thread started by discussing command line switches, there is a really good one for TerminalServer/Remote Desktops. If you add the switch /console to the command in the shortcut (or start RD by entering mstsc /console into the Run dialogue) then you get the actual deskop of the server, not a virtual console. If someone is using the console at the time, they get logged off, unless you are using the same account, in which case you get to takeover their session (they are still locked out though). This is the only mode remote sessions to XP machines work, and is an optional switch on Win2K3 remote desktops. It doesn't work when connecting to a Win2K machine though

    Regards

    Adam

  • If you have a particular database, or group of databases, you use regularly you can modify the properties of your shortcut in the quick launch bar (or your desktop, for that matter) by doing the following.

    1. Right-click on the Query Analyzer Shortcut, select "Properties".

    2. Modify the Target to be something like this ""C:\Program Files\Microsoft SQL Server\80\Tools\Binn\isqlw.exe" -SYourServerName -dYourDBName -E".

    Naturally, if you are using a SQL Login, you'll need to make a few adjustments, but hopefully y'all get the idea. It sure saves time! One click and you are in Query Analyzer using the Server and DB you need. I several shortcuts in my quick launch bar, one for each server/database I use repeatedly throughout the day.

  • Also, one little know tip for the Quick Launch menu, re-size the toolbar so that only the double arrows are visible, if you click the arrows a popup menu appears and you can select your shortcut from the menu. Below is a screenshot of how this looks on my home computer with the toolbar title visible.

    That would certainly save task bar space, especially if you have other tool bars. I can't get my QuickLaunch bar that small though - the smallest it will go is 3 icons wide. Is there some trick to make it smaller?

    You need to show the toolbar title. The title comes from the folder name, so just make it a short name.

     

    --------------------
    Colt 45 - the original point and click interface

  • Of course, there is always another way to start QA

    How about creating an association to a script file extension - I guess most of us use .SQL.  The association can be set via the QA Options - General Tab.  Set "Select SQL Query Analyser as the default editor ... etc" to true.  Then a simple "double-click" of the script file from Windows Explorer initiates the loading of QA.  Make sure you choose the correct database before executing the script.

    There is a down side to this if you use an external text editor for creating scripts.  Obviously, that editor will no longer act as the double-click default.  To overcome this, there is always the "open With" option when you right-click a script file.  WinXP will remember this after the first time it is done (you may have to go through selecting a program the first time it is done) so that QA always appears as an option thereafter.

    It is also not a great method if you are working with multiple databases/servers.  But for DBAs predominantly working on a single database it certainly provides a fast method of opening QA with the added advantage of already displaying the script you want.

    So there you have YAC - yet another choice - just what everyone needs.

     

    Rowan Shattky

    --------------

    Life is not a chair to sit on, but a cliff to hang from.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply