Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
stephe40
Posting Yak Master
218 Posts |
 Posted - 2007-01-22 : 11:05:00
|
| This is something that has always bugged me with SQL Server. We have always gotten around this limitation by outputting our script output to external files. So I am curious... Is there any way to increase the size of the buffer used to hold the script output in agent. I know that I can increase the duration of the history, but we have some scripts that output lots of information that is captured by SQL Agent, but only the first couple hundred characters are stored when you view the job history. I was just curious if there was a system table in msdb or something that I could increase the size of, or is this limitation enforced at the application code level? Also does anyone know how to get carriage return/line feeds to acutally show up when you view the job history.- Eric |
|
|
schuhtl
Posting Yak Master
102 Posts |
Posted - 2007-01-22 : 11:57:39
|
| When you output your script output to a external file are you using the advanced tab>output file for that job step or are you using something else? |
 |
|
|
stephe40
Posting Yak Master
218 Posts |
Posted - 2007-01-22 : 14:48:29
|
| No I am not using the advanced output file option for the step. I am coding in my vb script that I am running to create a file and write to it as well as the console. This way I can have each run of the script time stamped in the file name. I can also then quickly delete old log files that are not needed. I was under the impression that using the advance output file option of the step would write the output to the same file, overwriting it each time. I did see that append check box, so that would be an alternative, but then over time we would have some really large log files that dont get cleaned up.- Eric |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-01-22 : 15:19:03
|
| No. The output is limited by the size of column message in table msdb.dbo.sysjobhistory, NVARCHAR(1024), and it is limited to one row per job step per job execution.CODO ERGO SUM |
|
|
|
|
|
|
SQL Agent Step Output