Hi, Lately I identified a strange behaviour. Where a GO statement executed without error. And the same statement failed on another machine. Below is the code and please suggest what could be the possible reason for this. Create table #temp ( id int ) GO Insert into #temp Values (1). On one machine this give an error "#temp not found" which I believe is right as insert is now a separate batch. But the same query expected fine in another machine having same sql server versio (2014 enterprise edition). Is their any specific server property which can override the GO functionality. Kindly suggest.