I agree Management Studio is a step in the right direction. Let's hope it's more stable than EM.
A couple things I wish they would have carried over from EM:
OBJECT SEARCH
What a handy tool. Why on Earth would they drop this? Sure, you can use the INFORMATION_SCHEMA views, but it was nice not to have to crank out a new select statement each time I want to find all the occurrences of "InvoiceNumber" in a db.
Also gone is the ability to copy a table from EM, paste it into QA and have the Create Table statement done for you. Not the end of the world, but it was handy.
Maybe they will add these back in one day?
Maybe it's just me but I find the combination of the issues below make it unusable. I have reverted back to SQL2k QA after several thwarted attempts to use Man Studio successfully. (I am a database developer using SQL 2000)
You can't change the default scripting options as mentioned earlier in this thread. QA had the ability to switch on and off DROP object scripts and permissions scripts when you script a CREATE object. Man Studio won't let you change any options for scripting a single object (from the object browser tree) as far as I can see. I also don't want the USE statement for every object that I script but you can't turn this off either. I find myself continually cutting and pasting just to get what you could easily tailor in QA.
The text editor is now like VS but for me this is just a further annoyance. If you press Shift + Home QA (and pretty much every other text editor that I've used) will highlight the whole of the current line. Man Studio "cleverly" highlights from the first character. Whereas this is useful in VS when there is a lot of indenting it has little or no value (for me) in writing T-SQL.
If anyone knows how to change this behaviour I'll more than grateful if you can point me in the right direction.
>> A couple things I wish they would have carried over from EM:
>> OBJECT SEARCH
The only replacement I have found equivalent to the Object Search in EM is by using the filters in the Object Explorer window; however, this is fairly anemic compared with the original object search. I have not found a way to extend the properties in the Filter Settings, as you only can filter on Name, Schema, or Creation Date. The dialog does not appear very extensible, as the property settings are bundled into the ObjectExplorer.dll, so this would be another request to dear Microsoft. It would be nice to filter on date modified to see your recent changes, etc.
Also, while we're still griping a little, I do miss QA's ability to start the server when connecting to a new database. Not a production thing, just more of a development issue because I maintain so many different copies of SQL Servers on my machine, that I do not start them all by default. I find myself jumping back to SQL2K Service Manager to start the database engines, which at least it can crank up 2005 db's.
