InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 07:35:05 GMT20http://www.sqlservercentral.com/Forums/Topic1432087-392-1.aspx[quote][b]sestell1 (3/19/2013)[/b][hr][quote][b]CapnHector (3/18/2013)[/b][hr]I always use a close parentheses ")" at the top of my code sheets (be careful if you add a go it may not work exactly, tend not to break any thing into batches except in roll out scripts.) This generates a parse error and stops the batch from running.[/quote]Simple and effective, I like it![/quote]That or SELECT * FROM FakeTable will only stop single batch from executing if your script has multiple batches (separated by GO), only the one will be terminated by having such "parse" errors, other batches will not be affected. If you want to terminate your script for sure use high severity error:[code="sql"]RAISERROR ('Stop here',20,1) WITH LOG[/code]Nothing will pass the above;-)Tue, 19 Mar 2013 07:57:59 GMTEugene Elutinhttp://www.sqlservercentral.com/Forums/Topic1432087-392-1.aspx[quote][b]CapnHector (3/18/2013)[/b][hr]I always use a close parentheses ")" at the top of my code sheets (be careful if you add a go it may not work exactly, tend not to break any thing into batches except in roll out scripts.) This generates a parse error and stops the batch from running.[/quote]Simple and effective, I like it!Tue, 19 Mar 2013 07:05:17 GMTsestell1http://www.sqlservercentral.com/Forums/Topic1432087-392-1.aspxThanks so much for all the help, I really appreciate your time. The select statement seems to be the most risk free ofcourse and works best for me. Cheers!Mon, 18 Mar 2013 21:53:59 GMTakberali67http://www.sqlservercentral.com/Forums/Topic1432087-392-1.aspx[quote][b]sestell1 (3/18/2013)[/b][hr][quote][b]akberali67 (3/18/2013)[/b][hr]Hi,I have a query window with a lot of code but I do not want to run it entirely in error, is there something I can place in the beginning of the code that will throw me a message?Thanks,Akber.[/quote]The easiest thing to put at the top would be a simple select query referencing a table that does not exist. Something like [code="sql"]SELECT * FROM Table_That_Does_Not_Exist[/code].[/quote]I always use a close parentheses ")" at the top of my code sheets (be careful if you add a go it may not work exactly, tend not to break any thing into batches except in roll out scripts.) This generates a parse error and stops the batch from running.Mon, 18 Mar 2013 14:21:50 GMTCapnHectorhttp://www.sqlservercentral.com/Forums/Topic1432087-392-1.aspx[quote][b]akberali67 (3/18/2013)[/b][hr]Hi,I have a query window with a lot of code but I do not want to run it entirely in error, is there something I can place in the beginning of the code that will throw me a message?Thanks,Akber.[/quote]The easiest thing to put at the top would be a simple select query referencing a table that does not exist. Something like [code="sql"]SELECT * FROM Table_That_Does_Not_Exist[/code].Mon, 18 Mar 2013 14:06:50 GMTsestell1http://www.sqlservercentral.com/Forums/Topic1432087-392-1.aspx[quote][b]akberali67 (3/18/2013)[/b][hr]Hi,I have a query window with a lot of code but I do not want to run it entirely in error, is there something I can place in the beginning of the code that will throw me a message?Thanks,Akber.[/quote]To return a message to caller during T-SQL code execution you can use PRINT command.To throw an error use RAISERROR, together with using BEGIN TRY .. CATCH, it will immediately re-direct code into error handling section.Problem with PRINT, is that the message is not guaranteed to be returned at the exact moment of execution of the command, as it has a low processing priority, you may find that messages are returned at the end of the whole code execution. RAISERROR causes immediate termination of the process when used with TRY ... CATCH. There is one more option:[code="sql"]RAISERROR ('Return message immidiately', 10,1) WITH NOWAIT;[/code]The above command raises error with such low severity which doesn't transferring control to the CATCH block making RAISERROR to behave exactly as PRINT (you can use formatting capability of RAISERROR there). WITH NOWAIT hint makes this command to execute with highest priority, so you will get message back as soon as execution hits this line.Mon, 18 Mar 2013 03:24:11 GMTEugene Elutinhttp://www.sqlservercentral.com/Forums/Topic1432087-392-1.aspxHi,I have a query window with a lot of code but I do not want to run it entirely in error, is there something I can place in the beginning of the code that will throw me a message?Thanks,Akber.Mon, 18 Mar 2013 00:41:51 GMTakberali67