Hardy21 (11/23/2010)

---

Try

INSERT INTO # 
SELECT 'ASDF'
GO 0

GO <ZERO> --- SQL doesn't throw any complilation error but when you execute the code, status bar should display: "Query completed with errors".

DougieCow (11/23/2010)

---

Nope, doesn't like the 0 (zero) either.

I think it is the old version of SQL... further investigation does seem to suggest it.

Hardy21 (11/23/2010)

---

I have executed the code against SQL Server 2008 R2.

Brigadur (11/23/2010)

---

I have also executed on SQL Server 2008 R2. It gave "Query completed with errors" but no error message.

select * from # 
GO 0

Nils Gustav Stråbø (11/23/2010)

---

It's also worth mentioning that GO is not a T-SQL statement. It is a command only recognized by SSMS, sqlcmd and osql, so it can't be used in any T-SQL code that is not executed in any of the three applications mentioned. In other words, SQL Server does not know what GO is.

da-zero (11/23/2010)

---

Hmm. I seem to recall that I have used GO in Execute SQL Tasks in SSIS without a problem. (Or does that fall in the 3 categories you mentioned, because I only know the first one )

DECLARE @i int = 1;
WHILE @i <= 100
BEGIN;
  INSERT (...);
  SET @i += 1;
END;

DougieCow (11/23/2010)

---

(...)
when I did actually try to run the code it didn't seem to like the "100"... I got...

(1 row(s) affected)

Server: Msg 170, Level 15, State 1, Line 3
Line 3: Incorrect syntax near '100'.

The code is identical... I'm running this on a SQL Server 2000 box, but I don't think that matters...

da-zero (11/23/2010)

---

I like the point the question tried to make, namely using the GO statement as an instrument to loop, but I do not like the trickery with the # name. At first, I did not even notice the GO 100 statement, as I was focusing on the table name. So I'm confused what this question actually tried to do: teach us about GO n (mission accomplished), or about the various options for table names or was it just to trick people into choosing the wrong answer?