June 15, 2009 at 10:08 am
carissa.chris (6/15/2009)
I wanted a "forever" log and the ">> E:\output.txt" accomplishes exactly what I needed. Thanks for all the input.π
Ok... you guys can remove the handrails, now. π
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 1:28 pm
Jeff Moden (6/15/2009)
Ok... you guys can remove the handrails, now. π
..... getting out the reciprocating saw .... or will that cause too much damage where the handrails are installed at? :w00t:
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
June 15, 2009 at 1:46 pm
WayneS (6/15/2009)
Jeff Moden (6/15/2009)
Ok... you guys can remove the handrails, now. π
..... getting out the reciprocating saw .... or will that cause too much damage where the handrails are installed at? :w00t:
Heh.... no.... a simple "unscrewing" will do. π
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 8:22 pm
Jeff Moden (6/15/2009)
WayneS (6/15/2009)
Jeff Moden (6/15/2009)
Ok... you guys can remove the handrails, now. π
..... getting out the reciprocating saw .... or will that cause too much damage where the handrails are installed at? :w00t:
Heh.... no.... a simple "unscrewing" will do. π
You know Jeff, I have to admit that you have a way of bringing a smile to my face... Thanks!
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
December 1, 2009 at 6:21 am
[Borrowing the thread]
The ">>" "operator" was exactly was I was looking for (wanted appending feature to sqlcmd), it does what I want.
Unfortunately it seems not to support the same "codepage (1252)" as "-o" does.
Being in Sweden I miss my "special" characters.
Any workarounds/tricks on that βissueβ Jeff?
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply