It threw me. I assumed SSMS would behave the same way as isqlw so gave the wrong answer. I'm inclined to consider the SMSS behaviour a bug, as making sense out of using "go" as an identifier is just making it easier to write obscure bugs - but in fact SQLS 2000 isqlw is just as bad as small adjustments to the script can demonstrate.