Append output from SQLCMD in batch file

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 General Discussion » Append output from SQLCMD in batch file

20 posts, Page 1 of 2

1 2 »»

Append output from SQLCMD in batch file

Rate Topic

Display Mode

Topic Options

Author

Message

carissa.chris

Posted Friday, June 12, 2009 4:06 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, May 17, 2012 3:32 PM
Points: 4, Visits: 18

I have a batch file that runs all the sql scripts in a specified folder. The output is written to output.txt. However, each time a sql script is executed, the output.txt file is overwritten. Is there a way to append to the output.txt file?

Here is my batch file:

for %%a in ("E:\Source\APP_30\SQL\Structure\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"

for %%a in ("E:\Source\APP_30\SQL\SP\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"

for %%a in ("E:\Source\APP_30\SQL\Triggers\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"

Post #734169

WayneS

Posted Friday, June 12, 2009 4:20 PM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 3:13 PM
Points: 6,386, Visits: 8,286

carissa.chris (6/12/2009)

for %%a in ("E:\Source\APP_30\SQL\Structure\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"

for %%a in ("E:\Source\APP_30\SQL\SP\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"

for %%a in ("E:\Source\APP_30\SQL\Triggers\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"

Well, BOL clearly states that the output file will be overwritten.
I suggest you make the output filename dynamic:

for %%a in ("E:\Source\APP_30\SQL\Structure\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\%%aoutput.txt"

Wayne
Microsoft Certified Master: SQL Server 2008

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Links: For better assistance in answering your questions, How to ask a question, Performance Problems, Common date/time routines,
CROSS-TABS and PIVOT tables Part 1 & Part 2, Using APPLY Part 1 & Part 2, Splitting Delimited Strings

Post #734172

Jeff Moden

Posted Friday, June 12, 2009 10:47 PM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 4:58 PM
Points: 33,108, Visits: 27,034

Leave the first "-o" alone. Change all of the other "-o" to ">>".

Old DOS warrior trick. Tongue

--Jeff Moden

"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #734251

WayneS

Posted Friday, June 12, 2009 11:42 PM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 3:13 PM
Points: 6,386, Visits: 8,286

Jeff Moden (6/12/2009)

Leave the first "-o" alone. Change all of the other "-o" to ">>".

Old DOS warrior trick. Tongue

Ahem. It's not very often that someone gets to tell Jeff that he's wrong, AND can prove it...

for %%a in ("E:\Source\APP_30\SQL\Structure\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"
for %%a in ("E:\Source\APP_30\SQL\SP\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"
for %%a in ("E:\Source\APP_30\SQL\Triggers\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"

Jeff's suggestion is to change it to:

for %%a in ("E:\Source\APP_30\SQL\Structure\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a -o "E:\output.txt"
for %%a in ("E:\Source\APP_30\SQL\SP\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a >> "E:\output.txt"
for %%a in ("E:\Source\APP_30\SQL\Triggers\*.sql") do SQLCMD -S ServerName -d DatabaseName -E -i %%a >> "E:\output.txt"

The first line is processing each .sql file in the "Structure" directory. For each file, it runs the SQLCMD, which will have the -o parameter, overwriting the output file if it already exists. So if there are 3 .sql files in this directory, the output will only have the output from the third file.
It's not until you get to the second "for" line that Jeff's suggestion will start appending the results to the file.

Edit: added this suggestion:
if you were to start off with:
echo %date% %time% > E:\output.txt
you could then replace ALL of the -o with >>

Wayne
Microsoft Certified Master: SQL Server 2008

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Post #734260

Jeff Moden

Posted Saturday, June 13, 2009 11:40 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 4:58 PM
Points: 33,108, Visits: 27,034

WayneS (6/12/2009)

Ahem. It's not very often that someone gets to tell Jeff that he's wrong, AND can prove it...

Heh... wrong for what? If you want to keep the log forever, then yes, you need to replace the first "-o" with the ">>". But if you want the log to be only for the batch, the leave the first "-o" as it is. Tongue

Didn't know which way the OP wanted to go and I probably should have said so. Hehe

--Jeff Moden

Post #734396

WayneS

Posted Saturday, June 13, 2009 6:03 PM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 3:13 PM
Points: 6,386, Visits: 8,286

Okay, here's some code to demonstrate what I'm talking about.

Save this code as a batch file, and run it:

for %%a in ("%windir%\*.exe") do SQLCMD -S ServerName -d master -E -Q"set nocount on;select '%%a'" -o "%temp%\output.txt"
type %temp%\output.txt
pause
cls
echo %date% %time% > "%temp%\output.txt
for %%a in ("%windir%\*.exe") do SQLCMD -S ServerName -d master -E -Q"set nocount on;select '%%a'" >> "%temp%\output.txt"
type %temp%\output.txt
pause

del %temp%\output.txt

At the first pause, the contents of the output file are displayed. All that is in it is the last *.exe.
At the second pause, the contents of the output file are again displayed. The prior contents are erased, and all exe files are listed.
This demonstrates the point the OP was making.

Wayne
Microsoft Certified Master: SQL Server 2008

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Post #734483

Jeff Moden

Posted Sunday, June 14, 2009 9:23 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 4:58 PM
Points: 33,108, Visits: 27,034

WayneS (6/13/2009)

Okay, here's some code to demonstrate what I'm talking about.

Save this code as a batch file, and run it:

for %%a in ("%windir%\*.exe") do SQLCMD -S ServerName -d master -E -Q"set nocount on;select '%%a'" -o "%temp%\output.txt"
type %temp%\output.txt
pause
cls
echo %date% %time% > "%temp%\output.txt
for %%a in ("%windir%\*.exe") do SQLCMD -S ServerName -d master -E -Q"set nocount on;select '%%a'" >> "%temp%\output.txt"
type %temp%\output.txt
pause

del %temp%\output.txt

You've added a line of code the OP didn't have in the original problem and that new line is the one responsible for the incorrect operation.

echo %date% %time% > "%temp%\output.txt

You've neglected to use ">>" in that line of code and that's what resets file. Wink

--Jeff Moden

Post #734611

WayneS

Posted Sunday, June 14, 2009 9:54 AM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 3:13 PM
Points: 6,386, Visits: 8,286

Jeff Moden (6/14/2009)

You've added a line of code the OP didn't have in the original problem and that new line is the one responsible for the incorrect operation.

echo %date% %time% > "%temp%\output.txt

You've neglected to use ">>" in that line of code and that's what resets file. Wink

Correct, I reset the file between the runs, to demonstrate the effects of the two different methods. If the OP wants the file reset between runs, then use this line. If not, then get rid of it.

But the point was that with using the "-o" in the first part, the file is reset for every file being processed. Which is the behavior that the OP was trying to get rid of.

Wayne
Microsoft Certified Master: SQL Server 2008

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Post #734619

Jeff Moden

Posted Sunday, June 14, 2009 10:59 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 4:58 PM
Points: 33,108, Visits: 27,034

WayneS (6/14/2009)

Jeff Moden (6/14/2009)

You've added a line of code the OP didn't have in the original problem and that new line is the one responsible for the incorrect operation.

echo %date% %time% > "%temp%\output.txt

You've neglected to use ">>" in that line of code and that's what resets file. Wink

Understood. My point is that I wasn't sure if the OP was going for a continuous "forever" log or just wanted a single log with the results of all the individual steps for a single run of the batch. I posted the solution for the latter. It wasn't wrong, it just wasn't what you expected. Smile

--Jeff Moden

Post #734634

matt stockham

Posted Sunday, June 14, 2009 12:28 PM

Right there with Babe

Group: General Forum Members
Last Login: Thursday, June 06, 2013 9:36 AM
Points: 750, Visits: 2,946

Jeff Moden (6/14/2009)

I agree with Wayne. Your method wouldn't give a "forever" log or the results of all steps ... if there were 2 files for example, the results of the first iteration of the first step would be lost as the second iteration would overwrite the log.

Post #734663

« Prev Topic | Next Topic »

20 posts, Page 1 of 2

1 2 »»

Permissions