If I have foo.sql and bar.sql in the same folder, foo.sql can reference bar.sql when run from SSDT in sqlcmd mode with :r ".\bar.sql". However, SSMS won't find it. Procmon shows SSMS is looking in %systemroot%\syswow64:

Annotated Procmon screenshot

How do I tell SSMS to look in the folder that the current script is saved to without explicitly declaring the path?

3 Answers 3


Getting a relative path in SSMS is not that straight-forward since you are not executing the script; SSMS has loaded the script into memory and is executing its text. So the current directory/folder is the default process starting folder. You can see this by running the following in SQLCMD mode in SSMS:

!! PWD

However, I did find a kinda-sorta way to do this. I admit that this is not the super-most ideal way to do this, however, it currently seems to be the only way to get a true relative path (given that setting the path in a variable isn't really "relative" per se).

So what you can do is:

  1. Execute a DOS command to find foo.sql and store the path to that file in a text file in a folder that you can get from SSMS, either because it is a hard-coded path or because it uses an environment variable that is available to both the DOS command and to SQLCMD mode in SSMS
  2. When storing the path in that file, store it as a SQLCMD mode command that sets a variable to that path
  3. Import that text file into SSMS using :r and it will set that variable to the desired path
!! CD C:\ & FOR /F %B IN ('DIR /B /A -HS /S foo.sql') DO ECHO :setvar mypath "%~dpB" > %TEMP%\relative_path.txt

:r $(TEMP)\relative_path.txt

:r $(mypath)\bar.sql


  • The above method assumes only 1 file on the system is named foo.sql. If more than one file has that name, the last one found will be the path set in the relative_path.txt file

  • Doing the CD C:\ will start at the root of the C: drive. This is probably not the most efficient place to start. If you generally have your SQL files in an area such as C:\Users{YourLogin}\Documents\Visual Studio 2013\Projects, then just change the CD command to get closer to the destination, such as:

    !! CD C:\Users\{YourLogin}\Documents\Visual Studio 2013 & FOR ...
  • That's creative, but to slow and disk intensive. Feb 6, 2015 at 19:11
  • 2
    @JustinDearing As I said in my answer, it is a) non-ideal, and b) slow if starting from a root directory, but c) the only way I can see to do it that is technically relative. I am not sure if indexing the hard-drive would remove the performance issue. Feb 6, 2015 at 19:16
  • Though this makes me sad, this is definitively the best answer that does not involve setting the path from another command script or hard coding it into the file. Dec 19, 2016 at 5:50

I could be wrong, but I don't think that it is possible. Please see these links for an example of what others have done (none are ideal).



  • Well ok that sucks, but I guess it encourages SSDT usage. Feb 6, 2015 at 16:30

I recommend saving your sqlcmd variables file in 'C:\Users\your_nt_login_name\AppData\Local\Temp' and referencing it from all my projects as $(TEMP)\sqlcmd_variables.sql.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.