>>>>>>Thank you for the explanation. Now I just need to see some lines of code that, for example, would need to be run in the SSMS and must have GO.
>>>>>
>>>>>Just comment out each GO in any long script you have, and then wait for SQL to complain :).
>>>>
>>>>I suppose so far I have not done anything that complicated that requires a GO.
>>>
>>>
>>>These:
>>>

>>>UPDATE SomeTable SET ....
>>>
>>>GO --mandatory
>>>
>>>ALTER/CREATE TRIGGER ...
>>>

>>
>>Thank you, Borislav. Just to clarify, if the line after UPDATE was another UPDATE and not ALTER/CREATE trigger, the GO would not be mandatory, right?
>
>Correct. This is what we started from in this thread, did we not? :)
>
>The CREATE/ALTER PROCEDURE, CREATE/ALTER FUNCTION, CREATE/ALTER TRIGGER commands must be in a single batch. If we want to have them in the same batch, we need to use dynamic SQL.

I didn't connect what you said about Create Procedure with Create/Alter Trigger. I got it now. Thank you.