SQL and Batch File: (Microsoft SQL SERVER) by Souvik Ghosh (516964)

This document describes using a batch file to execute SQL scripts against multiple databases. It explains: 1. The problem of needing to regularly run SQL scripts against multiple databases as code changes. 2. How a batch file can be used to loop through SQL scripts in a folder, execute each one against multiple databases, and output any errors to individual files for each database. 3. The components of the batch file code including deleting old errors, executing scripts with sqlcmd, and outputting errors to unique files per database.

Uploaded by

Amita Sinha

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

49 views

SQL and Batch File: (Microsoft SQL SERVER) by Souvik Ghosh (516964)

Uploaded by

Amita Sinha

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 5

SQL and Batch File

(Microsoft SQL SERVER)

By
Souvik Ghosh
(516964)
Introduction
Have you ever wanted a simple and effective tool that can execute a bunch of SQL scripts from a folder? If
you have, and did not want to use 3rd party tools for getting the job done, then this article is what you need.

Problem Statement
As part of a development team, our daily work includes fixing bugs and adding new changes to SQL
scripts. We also need to check that code into our Version Control System (VCS). That means every time
another developer changes any script, we need to execute the same script on our database so that it is up-
to date.We need to do this at least every day, if not every couple of hours.

So once we have the latest script, we can use this cool trick to update multiple databases in one go. We
need two folders with scripts. For my illustration, I have two folders called:

1. Create Scripts

2. Change Scripts

You can see this in the image below.

Each folder has its own set of scripts:

The Magic
Open your favorite text Editor or Notepad, if you prefer, and enter the following:

@@echo off

del errors /f /s /q

rd Errors

md Errors

FOR %%A IN (*.SQL) DO ( sqlcmd -S SERVERNAME -d DATABASE1 -U username -P

password -i "%%A" -o "Errors\%%AError_DB1.txt" -I )

FOR %%A IN (*.SQL) DO ( sqlcmd -S SERVERNAME -d DATABASE2 -U username -P

password -i "%%A" -o "Errors\%%AError_DB2.txt" -I )

You would need to change the following as per your Database Name(s) and credentials in the above script:

 SERVERNAME – Your Database Server Name.

 DATABASE1 – Your Database name.

 Username – Your SQL Username.

 Password – Your SQL Password.

Save this file with the Extension as .bat in one of your scripts folder.
Copy this batch file to the other script folder.

The Explanation
Here is an explanation of each section of the code.
del errors /f /s /q
When executing the scripts, we dump all errors to a folder called Errors. This needs to be cleaned up. This
will delete the contents of folder silently.
rd Errors
This will delete the folder Errors.
md Errors
This will create a new folder names Errors. I know it is redundant, but why not start with a clean slate.
FOR %%A IN (*.SQL) DO ( sqlcmd -S MANU -d DATABASE1 -U username -P password -i "%%A" -o
"Errors\%%AError_DB1.txt" -I )
Using a FOR loop we select each file name in sequential order as per the name of the file which ends
with .sql extension in the current folder and pass the file name to execute with Server Name, Username,
Password and the database name using SQLCMD.
%%A
here denotes the name of the current file name in the loop.
–o
outputs any errors/messages from the script to a file in the errors folder followed by the Database name.
Adding the database name can help you differentiate the error files when you add multiple FOR Loops for
multiple databases. You can have n number of loops to n number of databases as in the example.
Ready,Set and Run
Now all you have to do is double click the batch file in the respective folders to execute all the scripts.