April 8, 2008 at 12:03 am
Hi, in SQL 2000 (using SSMS) I could generate a .txt file at a desired location that would capture the output both custom and otherwise from the running job.
From Job - Step - Advanced I could click on view and then the file would open (assuming I had the correct permissions).
I find in SQL 2005 I can set the output file up the same but the "View" button is dimmed.
I heard that when a SQL 2005 database is viewed this button is unavailable!!!
Does anybody know if this is correct?
Is their another way or when a job fails do I have to go to the server or open a share on the server, navigate to the file and manually open it which is royal pain in the butt.
Thanks
April 8, 2008 at 8:11 am
That button is disabled on mine also. I never realized that was ever a feature in 2000.
But to me it seems just as easy to just UNC to the folder where the logs are. If you really want to save time, map a drive on your workstation to the db server.
The Redneck DBA
April 8, 2008 at 11:48 pm
Does the output file exist yet? My recollection is that on 2005 (unlike 2000) the button will be disabled (dimmed) if the file has not been created yet.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
April 9, 2008 at 3:16 am
Hi, yes the output file has been created.
I have double checked and when SSMS is connecting to a SQL 2000 DB the 'view' button is enabled and the output txt file will open. When the job is on a 2005 (9.0) DB then this button is dimmed.
It is still possible to go to the share and manually open the file.
I was just wondering if this is a design feature [the lack of 'view' button functionality] or I have not turned something on. I have found other features in 205 that are off by default as oppossed to on by default in 2000.
April 9, 2008 at 6:18 am
Not a feature as far as I know, the button works on all of my Sql2005 boxes.
The only other thing that I can think of is a permissions issue, either in SqlServer, or in the Windows accounts that it uses. Remeber that the Sql Server service account is different from the Agent's account.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
April 9, 2008 at 2:05 pm
Maybe this answers my question!!
http://msdn2.microsoft.com/en-us/library/ms191142.aspx
To view job step output
In the Job Step Properties dialog, click the Advanced page.
Depending on the version of SQL Server you are connected to, you can view either the job step output file or table as follows:
When you are connected to Microsoft SQL Server 2000, you can click View to view the output file in Notepad. Job steps cannot be logged to a table in SQL Server 2000.
When you are connected to Microsoft SQL Server 2005, you can click View only when Log to table is checked. In this case, the job step output is written to the sysjobstepslogs table in the msdb database.
In SQL Server 2005, the View button is disabled when job step output is written to a file. To view a job step output file, use Notepad.
April 9, 2008 at 2:32 pm
Mark Avis (4/9/2008)
When you are connected to Microsoft SQL Server 2005, you can click View only when Log to table is checked. In this case, the job step output is written to the sysjobstepslogs table in the msdb database.
In SQL Server 2005, the View button is disabled when job step output is written to a file. To view a job step output file, use Notepad.
Boy that's a lame 'feature'....I always thought it was a bug that they just never fixed.
Your friendly High-Tech Janitor... 🙂
April 9, 2008 at 8:17 pm
I have found that if I log to a table as suggested and then after the job has run for the first time click on 'view' and then the output is displayed as a notepad file (although it is stored in a table)
I suppose the end result is the same and viewing directly from a file is probably legacy to 2000 that is only there for backward compatabilty.
September 23, 2010 at 5:31 am
I would still call this a bug in SSMS. Since there is a new View button presented for log table output. If the ability to view a file is removed from the product, why leave it present on the UI? Either make the button work or remove it from the UI?
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply