SQL script in BTDF

Topics: General Questions
Jan 24, 2011 at 4:23 AM

How to deploy SQL script using BTDF.

Could you give me a clear picture of it?

Thanks in Advance.

Jan 24, 2011 at 5:15 AM

There is no built-in support for running SQL scripts.  However, you can create a <Target Name="CustomPostDeployTarget"></Target> in your .btdfproj, and within that include an <Exec> MSBuild task to call osql.exe or sqlcmd.exe, whatever is appropriate for your version of SQL Server.  To include the SQL script itself into your MSI, you can create an ItemGroup with AdditionalFiles elements (same format as Schemas, Orchestrations, etc.).


Jan 24, 2011 at 5:52 AM

Do i need to add anything to the environmental settings file



Jan 24, 2011 at 6:00 AM

Not to do the basic form of what I described, but if you need to pass a SQL Server name to osql/sqlcmd and the name is different in each environment (and if you want to run the script in more than just your production environment), then you might use the settings spreadsheet.

If you want to have a parameter value available that is different in each environment, you would:

  1. Add a row to the settings spreadsheet and fill in the value for each environment (like the server name)
  2. In .btdfproj, locate the <PropsFromEnvSettings> property and add to it the name of your setting (first column of the spreadsheet), semicolon delimited.  That creates an MSBuild property that holds the value from the spreadsheet.
  3. Reference the setting name as an MSBuild property where needed, as $(TheSettingName)


Jan 24, 2011 at 7:00 AM

fine thats clear,i will try it out.


       <AdditionalFiles Include="SQLQuery.sql">

  <Import Project="$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets" />

    <Target Name="CustomDeployTarget">

        <Exec Command="sqlcmd.exe &quot;SQLQuery.sql&quot;" />




does the script i wrote to excecute sqlcmd.exe is correct?

Jan 24, 2011 at 10:38 AM

i got the sql script executed.



Jan 24, 2011 at 4:25 PM

Great.  One observation: avoid using explicit paths in your ItemGroups, because they will only work on your computer.  You can use relative paths -- the starting location will be always be the Deployment project folder.  Normally ".." will get to your solution root.


Jan 25, 2011 at 3:19 AM

Yes, Tom i will use relative path instead of explicit path.