I'm finding that VS2005 makes for a poor editor of stored procs.

1) If I right click and choose Run, it pops up a messagebox prompting me about saving the .sql file first. I looked for some option to turn off the "prompt before save" feature and didn't find it. Have I just missed it?

2) Why don't we get back full compile error messages? If there is a syntax error in the SP VS just gives me back this in the output window:

No rows affected.
(0 row(s) returned)
Incorrect syntax near the keyword 'Case'.
No rows affected.
(0 row(s) returned)

There are no errors listed in the error window.

While SQL Mgmt Studio (like Query Analyzer) gives the line no:

Msg 156, Level 15, State 1, Procedure xyz, Line 19
Incorrect syntax near the keyword 'Case'.

and I can dblclick the error message and the edit window goes to the error in the source.

3) Is there any intellisense in either tool? ie if I type tablename. why don't I get a list of columns?

4) The VS Design SQL Block functionality screws up all my code formatting.

5) SQL MS still doesn't do any sort of intelligent indenting while typing code.