Problem Sometimes there is a need to execute the same command or set of commands over and over again. This may be to insert or update test data or it may be to put a load on your server for performance testing. Whatever the need the easiest way to do this is to setup a while loop and execute your code, but in SQL 2005 there is an even easier way to do this.
Solution In both SQL Server 2000 and SQL Server 2005 the keyword GO tells SQL Server to execute the preceding code as one batch. In SQL Server 2005 you have the ability to add a number after the GO command to tell SQL Server how many times to execute the batch. So let's take a look at a couple of examples:
Let's say you want to create a test table and load it with 1000 records. You could issue the following command and it will run the same command 1000 times:
CREATE TABLE dbo.TEST (ID INT IDENTITY (1,1), ROWID uniqueidentifier) GO INSERT INTO dbo.TEST (ROWID) VALUES (NEWID()) GO 1000
Here is another example that executes both INSERT statements 1000 times. As you can see you can add more and more statements to the batch to be run the set number of times that is specified after the GO.
CREATE TABLE dbo.TEST (ID INT IDENTITY (1,1), ROWID uniqueidentifier) CREATE TABLE dbo.TEST2 (ID INT IDENTITY (1,1), ROWID uniqueidentifier) GO INSERT INTO dbo.TEST (ROWID) VALUES (NEWID()) INSERT INTO dbo.TEST2 (ROWID) VALUES (NEWID()) GO 1000
To do something similar to this in SQL Server 2000 you would need to write code such as the following. It is not that big a deal, but writing GO 1000 seems a bit easier to me.
CREATE TABLE dbo.TEST (ID INT IDENTITY (1,1), ROWID uniqueidentifier) CREATE TABLE dbo.TEST2 (ID INT IDENTITY (1,1), ROWID uniqueidentifier) GO
DECLARE @counter INT SET @counter = 0 WHILE @counter < 1000 BEGIN INSERT INTO dbo.TEST (ROWID) VALUES (NEWID()) INSERT INTO dbo.TEST2 (ROWID) VALUES (NEWID()) SET @counter = @counter + 1 END
Add this new trick to your list of tricks to make running the same batch faster then having to write a while loop
Check out these other great new SQL Server 2005 features:
As the cleandata process from my asp.net web application, If I want to clean historical data from a bunch of tables(around 50 plus tables, some tables are really large) from a database, is it a good practise to include GO after each delete statement or can I simply write all delete statements without a Go included. Can you please explain.
Not totally sure what you need, but you can either pass in the variable which means you would need to modify your SPs if you are passing it in as another parameter or do what you are mentioning with a global ## temporary table.
Is there a way to keep the current iteration of the batch? Using a variable like @GoCount won't work, because it goes out of scope with each time. I can write it to a temp table and increment, but that seems a little heavy-weight. Is there a method that is more straight-forward?
Hallo.can someone please help me with sql batches , i really dont know how to use them even though they seem to be the answer to the problem i have.here is my problem: im trying to write a student management system and the problem i have is to link student to their classes.the relationship beetween student and class is a many to many and i broke it with a StudentClass Table.so the problem im encountering now is to choose one student and assign him/her to their classes.and im using a checkedlist box control to poplulate classes and when i try to assign as many classes to a student,im getting a Violation of Foriegn Key constraint error and each time i use the GO keyword in my VB application, it is not recognise,so i don't really know how to approach the problem,please help.Thank you