SQL Server Performance Forum – Threads Archive
First thoughts of SQL Server Management StudioHello! <br /><br />Here is a post of my first thoughts of some of the new features in SQL Server Management Studio.<br /><br /><br />The query window.<br />At start I could not find how to write a query.. WHERE IS QUERY ANALYZER? <img src=’/community/emoticons/emotion-5.gif’ alt=’‘ /><br />When I finally found it I thought it was pretty.. err different, and for a while I actually used Query Analyzer instead. That was mostly because I didnt know where to find all functions that I was used to use. I had problems with showing execution plan, and that sort of things. Im starting to like it more and more, and i’m sure i’ll get use to it. <img src=’/community/emoticons/emotion-1.gif’ alt=’‘ /> Actually there is nothing much to complain about here. I found one thing though. When I execute a SP that executes a dynamic sql with sp_executesql inside. Then I need to have "include actual execution plan" for it to be correct. If I use "display estimated execution plan", I will just get mostly useless information.<br /><br />The function/SP window.<br />I like this! The help with choosing owner, scalar/table function, help with in/out/length etc of tha parameters. It rocks! One thing though.. Why isnt it possible to sort my parameters? I want them in a certain order, but I have not found any way to do that. Any suggestions?<br /><br />The properties window.<br />This is really good.. All in one place, easy to manage and such. For example when changing properties of a user or a database.<br /><br /><br />I react about one thing though. When I start the program I always get a question about what server I want to connect to. Now since I have already registered some servers I dont want to connect to any so I have to press cancel. I wonder what is most frequent. That you register a server and use that, or that you manually enter information about the server everytime during startup. Maybe this will be fixed in a later version though.<br /><br />Overall this tool is good. Like the management of indexes. Now you can choose if your index is primary key or not. That will probably take away all the misunderstandings of pk/index. Also you can choose wheter it should be clustered or not. I like that too. I have not used all tools yet, but I can say that all tools that were before are included but they are easier to use.<br /><br /><br />Anyone more want to share their thoughts of the new tools?
It’ll take some getting used to. But so did the MMC-based Enterprise Manager after SQL Server 6.5! I’m sure it’ll be better when it’s familiar.. Tom Pullen
DBA, Oxfam GB
Did anyone else notice how much memory (phyiscal & virtual) the Studio consumes?<br /><br />One thing I really like about QA is the fact it doesn’t use much memory so you can open multiple sessions without problems. I prefer this than multiple connections in one session as I can Alt Tab between them.<br /><br />I hate to think what will happen to my PC’s memory when I open multiple seesions of the Studio and have multiple connections open, queries running etc etc.<br /><br />Then maybe I’m just being fussy. I liked it otherwise! [<img src=’/community/emoticons/emotion-1.gif’ alt=’‘ />]
.. have you tried this on a proper server from a client’s machine. Satya SKJ
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.