FWIW, I use a generic project for that. I created it once and I use that for debugging scripts as needed whenever... Not ideal, but it works. I think any sort of debugging needs to run through a solution in VS, and that's why you need to set this up in VS.

+++ Rick ---


>>Hi Claudio,
>
>Hi, Cathi! :)
>
>>In VS.NET, you can edit your SPs by using the Server Explorer. You just need to tree down and find your stored procedure to edit. Right-click on the SP and choose Edit Stored Procedure. You can also run SPs by right-clicking on the SP and choosing Run Stored Procedure. If there are any parameters, VS.NET will prompt for their values.
>
>yup. I found that. However, I don't want to create a SP. What I actually want is the ability to open a .SQL script file and run it through VS.NET IDE. I saw that I can create a new Database Project, and then create a new query... but that's too many steps.
>
>Let me explain a little better:
>
>If I double-click a .SQL file in Windows Explorer, it'll run VS.NET, as it's set as the default program for this extension. VS then open my file, but I'm not able to run it. That's what I'd like to do. :)
>
>Tks anyway for taking your time! ;)