Ok, so there's a lot of chat at the moment about Denali SSMS not supporting X, Y and Z keyboard shortcut that it used to support, etc. I was wondering what people thought about it? Personally, I am a big fan of the breaking change. I am glad that Microsoft have deprecated a lot of stuff in .NET because they didn't actually get it right in the first place. I am also certainly in favour of making stuff more common between database and development environments. Having SSMS based on Visual Studio is a big step towards that, but keyboard shortcut commonality etc is a big plus - certainly, I have tried to do that in my editor where possible - especially with the more useful chords (for example, Ctrl+K,C for comment lines, Ctrl+K,U for uncomment). So my question is, should the fat be trimmed and the feature set bought more into line with todays standards, or should it still be supporting keyboard shortcuts from v6.5? And, should it still be supporting old-style features where newer style features exist (a case in point being old-style templates versus new style snippets)... ?
@Matt - great question +1. I reckon that a break from the old is a good thing. VS as the backbone for SSMS is a vast improvement, seeing the language engine usage really does show how "broken" SSMS/Query Analyser really are as IDEs. It is great to see MS finally giving T-SQL developers some love! They are also steering those devs into the direction of structured development/release cycles, which as a DBA, I can only applaud. Integrating the schema comparison abilities more into the tool is a great move, I can only hope that source control integration works as well (although there is no reason for it not doing that). As far as parity with v 6.5 and the like - I'm sorry, but people will have to get with the times! SQL 2000 is no longer supported, I know it is still probably the most used DB engine from MS (aside from Access!), but you cannot keep holding back the IDEs etc. to support stuff that is over a decade old. MS do need to keep some of the stuff though - as you say about useful chords. I can't imagine it being too much of a problem - I think they even mentioned that the current CTP didn't have all the chords supported, but it is going to support the newer/sensible stuff later on. I realise that they are stealing some of your and redgate's market by introducing some of the stuff you have, but it was long in the coming and needed to be addressed. I am sure that you will keep ahead of anything they have to offer - the stuff you produce seems to pop-up in a way that makes me think "God - why hasn't anyone made this yet!".
I'm all for change that in convergent and therefore allows the users actions to be IDE agnostic. In order to achieve this everyone will have to accept change to a greater or lesser extent. Where it comes to templates vs snippets then my main concern would be that there is a tool/facility to convert from one to the other. If thats there then all well and good. Note: This is all without seeing Denali as I dont have access to an OS that it will install on.
I don't have any heartburn over keyboard shortcuts, but do have to wonder what is the problem with keeping this available as an option. Maybe it's the famous non-developer comment "it's just a drop-down box" ![alt text] I'm sure it's incredibly difficult to maintain one keyboard mapping for a management tool and a separate one for an Integrated Development Environment (IDE). Let's acknowledge that SQL Server Management Studio is, in fact, a management tool and not an IDE -- Microsoft admits as much in the product name. If you want an IDE and its related keyboard shortcuts, MS will sell you [Visual Studio Team System Database Edition] (VSTSDB) Do you want to create a script-based source control integrated database project -- something widely acknowledged to be a best practice? SSMS won't do it for you, but VSTSDB will. Do you want to compare database schema and/or data? SSMS won't do it for you, but VSTSDDB will. On the other hand, if you want a good SQL Server management tool to - monitor your server's activity. VSTSDB won't do it, but SSMS will. - manage all aspects of your database server and databases. VSTSDB won't do it, but SSMS will. I'm a big fan of convergence where convergence makes sense, I'm just not sure that Visual Studio is the right place to do day-to-day server maintenance. These gradual migrations of SSMS into the Visual Studio paradigm should only be done with careful thought and due diligence. Just because a keyboard shortcut worked in SQL Server 6.5 isn't reason enough, by itself, to throw it out. : /upfiles/keyboard_shortcut_mapping_1.png :