Update to SQLCmdScriptExpander => 0.2.0.0 is out

re: Update to SQLCmdScriptExpander => 0.2.0.0 is out

JensSuessmeyer — Fri, 22 Feb 2013 22:31:37 GMT

Hi Frank,

thanks for the Feedback. To the points:

1. Thanks for reporting, I will fix that.

2. I understand that this does not make sense in most cases, will recreate the file instead.

3. That seems to be a bug which I will also fix.

4. Replaced with what actually ? The replacement would have to be done on runtime of the script. A script can be e.g. ´called with SQMCMD, there you have the -v command to pass in values for parameters. I didn not want to copy any existing functionality, just add missing functionality in my tools. So here is how I use it and what I suggest you.

-Expand the files with the ScriptExpander tool.

-Once being expanded, call the created script from SQLCMD and use the -v Switch to pass in parameters.

For the other things, watch out the next Version which I will tag as the Frank Edition ;-)

-Jens

re: Update to SQLCmdScriptExpander => 0.2.0.0 is out

Frank — Fri, 22 Feb 2013 16:06:58 GMT

I was looking for a tool just like the one you wrote. I find the lack of this functionality in sqlcmd a big disappointment.

I tried your tool and I found some issues. The first three very very minor.

1.- In the help usage OutputfFile has two 'f's.

2.- Every time i run it if the output file exists it appends to it.

3.- I must explicitly specify an encoding when you have a default one.

4.- I was really expecting to have the :setvar VarName "VarValue" to be also found and replaced properly in the outputfile.

Your previous post implies that your tool :

"In addition, the executing person needs to have a command line interpreter (like SQLCMD) capable of understanding the syntax of :r to pickup the referenced files".

If you could fix at least the last one, it would be appreciated.

Thanks