Search results matching tags 'denali' and 'debugging'http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&tag=denali,debugging&orTags=0Search results matching tags 'denali' and 'debugging'en-USCommunityServer 2.1 SP2 (Build: 61129.1)SQL Server v.Next (Denali) : Some Management Studio bugs you should vote forhttp://sqlblog.com/blogs/aaron_bertrand/archive/2010/11/29/sql-server-v-next-denali-some-management-studio-bugs-you-should-vote-for.aspxMon, 29 Nov 2010 18:14:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:31091AaronBertrand<p>It's been a while since I hosted a true Connect <strike>pity party</strike> digest, trying to pimp your votes for the issues I think are worthwhile.&nbsp; And okay, some of these bugs haven't been filed in the Denali time frame - but those are still in Denali's version of SSMS.&nbsp; And since we are not expecting a release for a year, and the next CTP won't be here until early 2011 sometime, what better time to build some momentum and hopefully sneak some of these fixes in?&nbsp; It won't happen without votes, so please check out any that you can appreciate. <br><br></p><p><font size="5">The "Change Connection" dialog</font>&nbsp; <br></p><blockquote><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/542304" title="http://connect.microsoft.com/SQLServer/feedback/details/542304" target="_blank">#542304 : Change Connection should order instance names in a better way</a><br>It would be great if we could customize this, but I'll take at least a defined and predictable sort order, regardless of what they choose.&nbsp; Alphabetical seems to make the most sense to me, though others (such as <a href="http://twitter.com/AdamMachanic" title="http://twitter.com/AdamMachanic" target="_blank">@AdamMachanic</a>) might argue that most recently connected would be more logical.<br></p></blockquote><blockquote><a href="http://connect.microsoft.com/SQLServer/feedback/details/424800" title="http://connect.microsoft.com/SQLServer/feedback/details/424800" target="_blank">#424800 : SSMS : Expose "Connect to Server" MRU list to users</a><br>The most important problem here is that you can have duplicates in the list - one for Windows Authentication, and potentially one for each SQL Authentication login you've used.&nbsp; So when you pull from the list again, it is trial and error to pick the right server + credential combination - like Forrest Gump not knowing which chocolate he's going to get.&nbsp; What I've requested here is a way to see and prune this list (and by extension, possibly even re-order it, addressing Adam's point above).&nbsp; Don't be fooled by the bug's current status - it says "Closed as Fixed," but the last Microsoft comment (from November 18) clearly states: "We will be [sic] try to fix this bug in next major release..." - which doesn't sound too fixed to me just yet.</blockquote><blockquote><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/621507" title="http://connect.microsoft.com/SQLServer/feedback/details/621507" target="_blank">#621507 : [Denali SSMS] : Prompt about previously registered servers is too sticky</a><br>While not completely related to the Change Connection dialog, this prompt comes back for me every time I try to change a connection by right-clicking within a query window.&nbsp; It also keeps coming back every time I launch SSMS, no matter how many times I check the "Do not show this message again" checkbox.&nbsp; For other users (e.g. <a href="http://twitter.com/SQLSoldier" title="http://twitter.com/SQLSoldier" target="_blank">@SQLSoldier</a>), they can't get this prompt to show up at all. <br></p></blockquote><p><br><font size="5">Keyboard shortcuts</font></p><blockquote><p>In the move to the VS shell, we have lost a LOT of keyboard functionality that we were used to in prior iterations of SSMS, and gained a few undesirable behaviors as well. <br></p></blockquote><blockquote><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/616721" title="http://connect.microsoft.com/SQLServer/feedback/details/616721" target="_blank">#616721 : SSMS Short Cut key "CTRL + E" is not working to execute any query</a> <br>Along with Ctrl + N, this functionality is missed by many users.&nbsp; Thankfully, it seems this bug will be fixed for the next CTP.<br></p><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/614413" title="http://connect.microsoft.com/SQLServer/feedback/details/614413" target="_blank">#614413 : [Denali SSMS] CTRL+U keybaord shortcut no longer works</a><br>Ctrl + U stopped working because of the next item: the keyboard shortcut for lower case (Ctrl + Shift + L) was reassigned.&nbsp; Jamie probably didn't notice the new functionality of Ctrl + U because he didn't have any text selected at the time (or it was already lower case).<br></p><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/625257" title="http://connect.microsoft.com/SQLServer/feedback/details/625257" target="_blank">#625257 : [Denali SSMS] : Ctrl + Shift + L no longer issues lower case</a><br>As described above - this keyboard shortcut was inexplicably changed to a very unintuitive key combination.&nbsp; Yet Ctrl + Shift + U still handles upper case. <br></p><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/623863" title="http://connect.microsoft.com/SQLServer/feedback/details/623863" target="_blank">#623863 : [Denali SSMS] : Ctrl + Shift + M no longer raises template parameter dialog</a><br>This keystroke omission practically destroys the functionality of templates.<br>
</p><a href="http://connect.microsoft.com/SQLServer/feedback/details/625260" title="http://connect.microsoft.com/SQLServer/feedback/details/625260" target="_blank">#625260 : [Denali SSMS] : F5 in Object Explorer no longer refreshes; triggers debug instead</a><br>"Start debugging" is supposed to be triggered by Alt + F5, not F5 on its own.&nbsp; And I shouldn't be able to start debugging when I am focused in Object Explorer anyway.<br><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/623498" title="http://connect.microsoft.com/SQLServer/feedback/details/623498" target="_blank">#623498 : Error when pressing the F1 key in SSMS</a><br>In older versions of SSMS, pressing F1 without focus on a relevant object would just be a no-op; now it yields a pretty badly-handled error.<br></p></blockquote><br><font size="5">Just plain old inconsistency, or promoting bad practices</font><br><blockquote><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/623865" title="http://connect.microsoft.com/SQLServer/feedback/details/623865" target="_blank">#623865 : [Denali SSMS] : Inconsistency : Non-Clustered vs. Nonclustered</a><br>This is just a simple inconsistency that should be easy to correct, but they're already making excuses about why they can't correct it in the next 12 months.<br><br><a href="http://connect.microsoft.com/SQLServer/feedback/details/623864" title="http://connect.microsoft.com/SQLServer/feedback/details/623864" target="_blank">#623864 : [Denali SSMS] : Inconsistency : Is it Template Explorer or Template Browser?</a><br>Another simple inconsistency that should be easy to fix.&nbsp; I think it's just a case of the left hand not knowing what the right hand is doing.<br><br><a href="http://connect.microsoft.com/SQLServer/feedback/details/622784" title="http://connect.microsoft.com/SQLServer/feedback/details/622784" target="_blank">#622784 : [Denali SSMS] : Proliferation of the use of deprecated system tables (e.g. sysobjects)</a><br>There should be a standard way to prevent the dev team from implementing code that uses deprecated objects.&nbsp; It's kind of embarrassing when we spread the word that you should stop using sysobjects in your scripts, and then Microsoft goes along and keeps using it...<br><br><a href="http://connect.microsoft.com/SQLServer/feedback/details/623047" title="http://connect.microsoft.com/SQLServer/feedback/details/623047" target="_blank">#623047 : Incorrect SET options for New Service Broker Application</a><br>As above, they need to follow better standards and be on the same page as far as scripting conventions and defaults.<br></p><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/623049" title="http://connect.microsoft.com/SQLServer/feedback/details/623049" target="_blank">#623049 : master misspelled in new Service Broker tasks</a><br>All code that gets called within or generated by Management Studio and other shipped components should be tested on a case sensitive collation.<br></p></blockquote><br><font size="5">Poor behavior</font><br><blockquote><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/625266" title="http://connect.microsoft.com/SQLServer/feedback/details/625266" target="_blank">#625266 : Denali SSMS Incorrectly Reports session_id for connected tabs</a><br>Pretty scary that SSMS can get into a confused state and not know which SPID is which.&nbsp; I believe the symptom is related to SSMS losing connectivity with the server, whether it be because of a network blip of some kind or because the service restarted or failed over.<br></p><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/615766" title="http://connect.microsoft.com/SQLServer/feedback/details/615766" target="_blank">#615766 : [Denali SSMS] : Execution plan tooltip causes very slow behavior</a><br>I see this bug constantly - I swear every time I accidentally hover over the query portion of an execution plan.&nbsp; I have showed one of the program managers - in person - how to reproduce this bug, so I expect that it will get corrected (preferably just by eliminating the useless tooltip altogether).<br></p><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/623735" title="http://connect.microsoft.com/SQLServer/feedback/details/623735" target="_blank">#623735 : Denali CTP1 SSMS Error Message Click doesn't return to error line</a><br>This is a behavior that is sorely missed.&nbsp; It is currently non-functional because of the transition to the Errors List that Visual Studio developers know and love (I talked about this a bit at the bottom of an earlier <a href="http://sqlblog.com/blogs/aaron_bertrand/archive/2010/11/23/sql-server-11-denali-the-new-vs-shell.aspx" title="http://sqlblog.com/blogs/aaron_bertrand/archive/2010/11/23/sql-server-11-denali-the-new-vs-shell.aspx" target="_blank">blog post about "the new SSMS"</a>).&nbsp; I hope there is middle ground here somewhere.<br><br><a href="http://connect.microsoft.com/SQLServer/feedback/details/425661" title="http://connect.microsoft.com/SQLServer/feedback/details/425661" target="_blank">#425661 : SSMS : unable to register local servers</a><br>This bug has been around for a long time, but Microsoft continuously insists that it can't reproduce.&nbsp; If you have any further evidence of this problem, please comment / vote / validate!<br></p></blockquote><br><font size="5">Toolbar customization</font><br><blockquote><p><a href="http://connect.microsoft.com/SQLServer/feedback/details/615154" title="http://connect.microsoft.com/SQLServer/feedback/details/615154" target="_blank">#615154 : [Denali SSMS] : Can no longer drag buttons within or off the toolbar</a><br>While most of the T-SQL developers out there are clamoring for better debugging support in Management Studio, I am still "old school" and want nothing else but to remove the Debug icon from the toolbar.&nbsp; I've found that customizing the toolbar has become a lot more cumbersome in Denali.<br></p></blockquote><br><font size="5">Debugging</font><blockquote><p>I mentioned four Connect items about debugging in a post a few days ago.&nbsp; Rather than repeat them here, I'll just point you at <a href="http://sqlblog.com/blogs/aaron_bertrand/archive/2010/11/24/debugging-t-sql-in-sql-server-v-next-denali-you-can-make-a-difference.aspx" title="http://sqlblog.com/blogs/aaron_bertrand/archive/2010/11/24/debugging-t-sql-in-sql-server-v-next-denali-you-can-make-a-difference.aspx" target="_blank">that blog post</a>. <br></p><p>&nbsp; <br></p></blockquote>Debugging T-SQL in SQL Server v.Next (Denali) : You can make a difference!http://sqlblog.com/blogs/aaron_bertrand/archive/2010/11/24/debugging-t-sql-in-sql-server-v-next-denali-you-can-make-a-difference.aspxWed, 24 Nov 2010 19:23:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:31009AaronBertrand<p>This afternoon, Adam Machanic (<a href="http://sqlblog.com/blogs/adam_machanic/" title="http://sqlblog.com/blogs/adam_machanic/" target="_blank">blog</a> | <a href="http://twitter.com/AdamMachanic" title="http://twitter.com/AdamMachanic" target="_blank">twitter</a>) reminded me how the current T-SQL debugger in Management Studio is ineffective.&nbsp; Sure, there are some enhancements coming in Denali (I <a href="http://sqlblog.com/blogs/aaron_bertrand/archive/2010/11/23/sql-server-11-denali-the-new-vs-shell.aspx" title="http://sqlblog.com/blogs/aaron_bertrand/archive/2010/11/23/sql-server-11-denali-the-new-vs-shell.aspx" target="_blank">mentioned them briefly yesterday</a>), but there are some real key elements missing.&nbsp; One of the most glaring omissions is the ability to see the contents of #temp tables and @table variables during a debugging session.&nbsp; For stored procedures that can take a long time to run, it is quite cumbersome to edit the procedure to dump the contents of the #temp table as a resultset, which can obviously interfere with the operation of the procedure (especially if applications currently rely on its interface).&nbsp; As Adam eloquently stated, "All I want right now is a debugger that helps with real challenges. Scalar variables are not enough."</p><p>Hear, hear.&nbsp; This is one of the reasons I have yet to step back from my curmudgeony debugging methods: PRINT, RAISERROR, and (since 2005) TRY/CATCH.&nbsp; I don't come from an OOP background, but I do understand why many people value a more formal method of debugging.</p><p>So, how can you help?&nbsp; Well, I know some of you do not believe in Connect, but for those that do - this issue of not being able to see into #temp tables and @table variables is covered by no fewer than four Connect items.&nbsp; I am asking that you go and vote for all four of them, because Connect doesn't have a good way for us peons to close duplicates and focus on a single item.&nbsp; (I'd love to pick just one and tell you to vote there, but with my luck, Microsoft will choose a different one to keep alive, if they ever get around to consolidating.)</p><blockquote><p><a href="http://connect.microsoft.com/SQL/feedback/details/623353" title="http://connect.microsoft.com/SQL/feedback/details/623353" target="_blank">Connect #623353 : View contents of table variables and temp tables in SSMS debugger</a> <br></p><a href="http://connect.microsoft.com/SQL/feedback/details/582167" title="http://connect.microsoft.com/SQL/feedback/details/582167" target="_blank">Connect #582167 : Debugger should hyperlink into CTE-s, table variables, temp tables and changed rows</a><br><p><a href="http://connect.microsoft.com/SQL/feedback/details/454870" title="http://connect.microsoft.com/SQL/feedback/details/454870" target="_blank">Connect #454870 : No way to see contents of table valued variable in debugger</a></p><p><a href="http://connect.microsoft.com/SQL/feedback/details/363054" title="http://connect.microsoft.com/SQL/feedback/details/363054" target="_blank">Connect #363054 : temp table and table variable visibility through debug</a> <br></p></blockquote> <p>So please, if you value debugging and you want to see better improvements than just being able to watch scalar variables, vote on these items.&nbsp; And if someone tells you they're going to create a new Connect item in a similar vein, please tell them to search first.&nbsp; Having multiple items covering the same issue just spreads out the votes and makes it less likely that the issue will be tackled.&nbsp; Thanks! <br>&nbsp;<br></p>