>>I have this line in a script:
>>
>>

>>EXEC MASTER.dbo.xp_cmdshell @Merge_Script, no_output
>>

>>
>>When there is only one time for it to execute, it works great. It seems that if it needs to execute multiple times, it hangs up, or at least "Executing Query" does. It's hard to tell where it's stuck as there is no debugger in SQL Server MS. Is there something I can do to make sure it's a clean run for the exe? Sort of like CLEAR or RELEASE in Foxpro?
>>
>>UPDATE: Or, do I need to pause or something to let the EXE finish maybe? It runs fast though.
>
>Are you working on your own $$, or can you convince your employer to pick up VS2005 or 2008 PRO so you can have a good debugger for SQL 2005? If you are doing a fair amount of work in SPs or functions, it can be extremely handy.

This is close to a one-time thing. Once the scripts are in place we will reuse them, but not much more new stuff for quite awhile.