Skip to main content

SQLCMD -- Part VIII (:r and about concatenating string with spaces)

Theory:

:r -- parses additional T-SQL statements and sqlcmd commands from the file specified by into the statement cache.

In this article we would see the usage of :r as well as handling spaces in SQLCMD.

In SQL Mgmt Studio:

Step 1: 01VariableInitialization.sql

:setvar filepath "C:\Vadivel\SQL Related\Scripts\sqlcmd"
:r $(filePath)\02TableCreation.sql


Step 2: 02TableCreation.sql

Create table tblTest
(
Sno int identity,
FName varchar(20)
)
Go

:r $(filePath)\03InsertScripts.sql


Step 3: 03InsertScripts.sql

Insert into tblTest (Fname) values ('alpha')

Explanation of each file:

01VariableInitialization.sql -- In this file we create a scripting variable 'filePath' which will hold the path of the .sql files which we use for this demo. Then it executes 02TableCreation.sql.

02TableCreation.sql -- In this, we create tables of our choice. Also we make use of the scripting variable created in the previous file here to call another .sql file to insert records into this table.

It's advisable to check whether that table exists before creating it.

03InsertScripts.sql -- Insert records into our dummy table.

In Command Prompt:

Now open command prompt (start >> Run >> cmd) and connect to a DB server to execute the first .sql file alone.

Step 4: SQLCMD -i "C:\Vadivel\SQL Related\Scripts\sqlcmd\01VariableInitialization.sql"

Till now everything would have worked properly.

Step 5: If at all you have your 01VariableInitialization.sql as shown below:

:setvar filepath "C:\Vadivel"
:r $(filePath)\SQL Related\Scripts\sqlcmd\02TableCreation.sql


If you try this it would fail. Why? Because there is a space within the string which we have concatenated with our scripting variable. So if we have space then we need to enclose the string within quotes.

Is this the way to add quotes?
:r $"(filePath)\SQL Related\Scripts\sqlcmd\02TableCreation.sql"

No this would throw an syntax error!!

The correct way to add quotes is shown below:

:r $(filePath)"\SQL Related\Scripts\sqlcmd\02TableCreation.sql"

So the lesson learned is add quotes only for the string which is being concatenated with a scripting variable (that too if it has spaces in it).

Hope this helps!

Comments

Anonymous said…
Thanks - I thought there must be way to do it!
Anonymous said…
Hi!

I was wondering if you knew if it was possible to assign a variable from another. ie.

:setvar a 1
:setvar b 2

I would like to define a third variable c equal to (1,2)

I tried

:setvar c ($(a),$(b)) but it doesn't work?

select '$(c)' returns ($(a),$(b)) not (1,2) ...is this even possible?

Popular posts from this blog

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul

AWS fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request

While using AWS and trying to copy a file from a S3 bucket to my EC2 instance ended up with this error message. Command Used: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ Error: fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request The error goes off if we add the region information to the command statement. I am using Asia Pacific (Mumbai) so used ap-south-1 as the region name. Modified Command: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ --region ap-south-1

[Non Tech] Want to know the recipe for Omelette :)

Fed up with Bread - Jam and Curd Rice, today i wanted to eat Omelette. Interesting part is I wanted to cook it myself :) So in the first picture you see all the items which are needed for preparing an Omelette. When I had a closer look at the eggs I see that almost all the eggs are broken. But believe me when I bought it couple of days back it was in perfect condition! I was wondering whether the eggs have become rotten or pretty old to consume! I tried taking an egg and break it but couldn't break it at all :) Since I have kept in the freezer all the eggs have frozen and looked like a iron ball :) After trying for few minutes of trying i removed the shell of the egg and then kept that iron ball :) into a bowl and placed it within Oven. I heated it for 1 minute and checked. It melted only to a limit. So i just set it for another 2 minutes and checked it later. It has melted but the part of the egg white has become a Omelette :( I didn't leave it there. I took the bowl out of