Am wanting to utilize Visual Studio 2005 to edit / debug Transact SQL for MS SQL Server 2000 as a stepping board towards further programming challenges.

Have created projects, attached to databases, but in running my SQL scripts I'm finding the debugging and tracking errors (especially with long scripts with several batches) to be difficult with VS 2005, compared to Query Analyzer.

Examples so far:

-no F5 to run a script

-no parser to check for syntax

-when viewing errors in output window, double clicking on the error doesn't take you to the batch in question

Looking for guidance in utilizing VS 2005 with the features that I'm used to with Query Analyzer (figuring it would be better).

Thanks,