Why there is "GO" after USE db" in T-SQL examples?

Question

Looking at the msdn, there was an example on "GO" command. Why there is:

USE somedb
GO
...
...

It it neccesary to select db in different batch? Thanks for explanation!

It is not. I know what is GO good for. But I cannot see any advantagee in using it after "USE db". — Petr
– Petr, Commented May 31, 2010 at 10:37

Cade Roux · Accepted Answer · 2010-05-31 14:16:16Z

20

Is it necessary to select db in different batch?

No, however, some commands have to be the first statement in the batch.

Examples include CREATE VIEW, CREATE PROCEDURE and CREATE TRIGGER.

Thus if you want to do:

USE DB

CREATE VIEW X AS SELECT * FROM Y

Then you need to do:

USE DB
GO

CREATE VIEW X AS SELECT * FROM Y

If you are only running one USE DB statement, the GO has no usefulness.

Some commands do not require that they are the first statement in a batch:

USE DB
SELECT * FROM X

Sometimes in code generation, all the GO commands might not be necessary, but it's just easier to generate them.

answered May 31, 2010 at 14:16

Cade Roux

90.1k42 gold badges186 silver badges268 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Incognito · Accepted Answer · 2010-05-31 10:22:09Z

2

It signals the end of a batch of Transact-SQL statements to the SQL Server utilities. You can check here for more details : GO (Transact-SQL)

answered May 31, 2010 at 10:22

Incognito

16.6k9 gold badges54 silver badges75 bronze badges

I know and I was asking about GO after USE which is exactly on page you reference.