sqlcmd

As part of our database revision control (and auto-installation) procedures we need to be able run sqlcmd.exe on various .sql files from within an ASP page. The code I'm using to do this is: Dim cmd : cmd = "sqlcmd -S " & DATABASE_SERVER & " -U " & DATABASE_UID & " -P " & DATABASE_PWD & " -d " & DATABASE_NAME & " -i """ & scriptPath & """ -b" Dim wshShell : Set wshShell = Server.CreateObject("WScript.Shell") Dim return : return = wshShell.Run(cmd, 0, True) I have the code working on my development machine (running XP) but now that I've deployed it to our Windows 2003 server it's having

When running a script in SQLCMD, is there a setting, parameter or any other way of making it effectively run a GO command at the end of each SQL statement? This would prevent the need to insert periodic GO commands into very large scripts. No. SQLCMD would have to implement a full T-SQL parser itself in order to determine where the statement boundaries are. Whereas as it currently exists, all it has to do is find lines with "GO" on them. Determining statement boundaries can be quite tricky, given that ";" terminators are still optional for most statements. Hmmm, I guess this is not going to

I have a script file e.g. test.sql. I want to call this from another script, say caller.sql, in sqlcmd mode using :r test.sql. This works fine, but I want to use a scripting variable in test.sql. When I call test.sql from caller.sql I can set the scripting variable and all is well. However, I want to use a default value for the scripting value so that if the caller does not set the variable, or if I run test.sql directly (not from caller.sql) then the scripting variable defaults to a set value. I have tried things such as begin try select '$(grip)' select 'grip value was found' end try begin

I'm trying to export data from SQL Server into CSV format. I have a bat task to do this that's run at regular intervals. Command is: SQLCMD.EXE -d [db details] -i c:\export.sql -o c:\export.csv -s"," -W The SQL file is just a SELECT * from a view. This works except that some of the rows have commas in the data, so the values need to be quoted. I could change the column separator to be "','", but then I'd need SQL Server to escape single quotes in the data as well. Unfortunately changing the separator to another character is unlikely to solve the problem in 100% of cases as one of the fields

We were experiencing problems with Powershell and SQLCMD, when there was sapces in the -v parameter variable powershell wouldn't run the command. e.g. sqlcmd ... -v VAR="Some space" Has anyone experienced this before or know how to fix the problem? Thanks, B The syntax above works for the PS commandline but fails within a script. We struggled a long time with how to make this work. One of our very clever QA guys finally came up with the following: $variableWithSpaces="one two three" $mySqlCmd = "sqlcmd -E -S $dbServer -i $script -v var=```"$variableWithSpaces```" " Invoke-Expression $mySqlCmd