Job History

Hello all,
Is there a way to define how much history will be logged in the Job History
window?
I need to save history from the whole last week's run, but it keeps been
deleted.
Thanks
Liran
Take a look at sysjobhistory system table
"Liran" <Liran@.discussions.microsoft.com> wrote in message
news:C03C14C4-43ED-4E97-BE97-E71FD083F331@.microsoft.com...
> Hello all,
> Is there a way to define how much history will be logged in the Job
> History
> window?
> I need to save history from the whole last week's run, but it keeps been
> deleted.
> Thanks
|||Actually, I did, but the solution is to change the dafault log size in the
SQL Server Agent Property window.
"Uri Dimant" wrote:

> Liran
> Take a look at sysjobhistory system table
> "Liran" <Liran@.discussions.microsoft.com> wrote in message
> news:C03C14C4-43ED-4E97-BE97-E71FD083F331@.microsoft.com...
>
>
|||Liran
To modify the maximum number of records maintained in sysjobhistory open
Enterprise Manager and expand the Server to modify. Expand Managment and
Right Click SQL Server Agent and select Properties.
Under the Job System tab there is two text boxes. Maximum job history log
size (rows) and Maximum job hisory rows per job.
-rows per job is the maximum number of rows in sysjobhistory for a
partilcuar job
-log size (rows) is the maximum number rows in sysjobhistory for all jobs
Updating these values will modify how many rows are maintained.
-Peter Ward
WARDY IT Solutions
"Liran" wrote:
[vbcol=seagreen]
> Actually, I did, but the solution is to change the dafault log size in the
> SQL Server Agent Property window.
>
> "Uri Dimant" wrote:

Job History

Hello all,
Is there a way to define how much history will be logged in the Job History
window?
I need to save history from the whole last week's run, but it keeps been
deleted.
ThanksLiran
Take a look at sysjobhistory system table
"Liran" <Liran@.discussions.microsoft.com> wrote in message
news:C03C14C4-43ED-4E97-BE97-E71FD083F331@.microsoft.com...
> Hello all,
> Is there a way to define how much history will be logged in the Job
> History
> window?
> I need to save history from the whole last week's run, but it keeps been
> deleted.
> Thanks|||Actually, I did, but the solution is to change the dafault log size in the
SQL Server Agent Property window.
"Uri Dimant" wrote:

> Liran
> Take a look at sysjobhistory system table
> "Liran" <Liran@.discussions.microsoft.com> wrote in message
> news:C03C14C4-43ED-4E97-BE97-E71FD083F331@.microsoft.com...
>
>|||Liran
To modify the maximum number of records maintained in sysjobhistory open
Enterprise Manager and expand the Server to modify. Expand Managment and
Right Click SQL Server Agent and select Properties.
Under the Job System tab there is two text boxes. Maximum job history log
size (rows) and Maximum job hisory rows per job.
-rows per job is the maximum number of rows in sysjobhistory for a
partilcuar job
-log size (rows) is the maximum number rows in sysjobhistory for all jobs
Updating these values will modify how many rows are maintained.
-Peter Ward
WARDY IT Solutions
"Liran" wrote:
[vbcol=seagreen]
> Actually, I did, but the solution is to change the dafault log size in the
> SQL Server Agent Property window.
>
> "Uri Dimant" wrote:
>

Job History

Hello all,
Is there a way to define how much history will be logged in the Job History
window?
I need to save history from the whole last week's run, but it keeps been
deleted.
ThanksLiran
Take a look at sysjobhistory system table
"Liran" <Liran@.discussions.microsoft.com> wrote in message
news:C03C14C4-43ED-4E97-BE97-E71FD083F331@.microsoft.com...
> Hello all,
> Is there a way to define how much history will be logged in the Job
> History
> window?
> I need to save history from the whole last week's run, but it keeps been
> deleted.
> Thanks|||Actually, I did, but the solution is to change the dafault log size in the
SQL Server Agent Property window.
"Uri Dimant" wrote:
> Liran
> Take a look at sysjobhistory system table
> "Liran" <Liran@.discussions.microsoft.com> wrote in message
> news:C03C14C4-43ED-4E97-BE97-E71FD083F331@.microsoft.com...
> > Hello all,
> >
> > Is there a way to define how much history will be logged in the Job
> > History
> > window?
> > I need to save history from the whole last week's run, but it keeps been
> > deleted.
> >
> > Thanks
>
>|||Liran
To modify the maximum number of records maintained in sysjobhistory open
Enterprise Manager and expand the Server to modify. Expand Managment and
Right Click SQL Server Agent and select Properties.
Under the Job System tab there is two text boxes. Maximum job history log
size (rows) and Maximum job hisory rows per job.
-rows per job is the maximum number of rows in sysjobhistory for a
partilcuar job
-log size (rows) is the maximum number rows in sysjobhistory for all jobs
Updating these values will modify how many rows are maintained.
-Peter Ward
WARDY IT Solutions
"Liran" wrote:
> Actually, I did, but the solution is to change the dafault log size in the
> SQL Server Agent Property window.
>
> "Uri Dimant" wrote:
> > Liran
> > Take a look at sysjobhistory system table
> >
> > "Liran" <Liran@.discussions.microsoft.com> wrote in message
> > news:C03C14C4-43ED-4E97-BE97-E71FD083F331@.microsoft.com...
> > > Hello all,
> > >
> > > Is there a way to define how much history will be logged in the Job
> > > History
> > > window?
> > > I need to save history from the whole last week's run, but it keeps been
> > > deleted.
> > >
> > > Thanks
> >
> >
> >

Job execution logged as an error

I have a special necessity in which I need that the result of failed jobs in
SQL Server Agent be logged as errors in Windows Event Viewer.
Normally they are logged as Warnings.
We developed a solution that uses active scripting for writing the errors in
Event Viewer. However, the policy configured prevents the execution of active
scripting.
Is there any other way of writing the result of failed jobs as errors in
Event Viewer?
I was hoping that there was a configuration that could be done to change the
type of event written in Event Viewer.
ThanksMaybe something using a job step of raiserror with log as a
failure branch in the job might work for you.
-Sue
On Tue, 03 Oct 2006 15:51:32 GMT, "jaimefelipe" <u27450@.uwe>
wrote:
>I have a special necessity in which I need that the result of failed jobs in
>SQL Server Agent be logged as errors in Windows Event Viewer.
>Normally they are logged as Warnings.
>We developed a solution that uses active scripting for writing the errors in
>Event Viewer. However, the policy configured prevents the execution of active
>scripting.
>Is there any other way of writing the result of failed jobs as errors in
>Event Viewer?
>I was hoping that there was a configuration that could be done to change the
>type of event written in Event Viewer.
>Thanks|||Thanks for your reply Sue.
I tried the command sugested but, in order to run it, the job has to be
configured as sysadmin and this is not allowed in my company.
Is there other way?
Sue Hoegemeier wrote:
>Maybe something using a job step of raiserror with log as a
>failure branch in the job might work for you.
>-Sue
>>I have a special necessity in which I need that the result of failed jobs in
>>SQL Server Agent be logged as errors in Windows Event Viewer.
>[quoted text clipped - 12 lines]
>>Thanks|||xp_logevent?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jaimefelipe" <u27450@.uwe> wrote in message news:673a0cf792feb@.uwe...
> Thanks for your reply Sue.
> I tried the command sugested but, in order to run it, the job has to be
> configured as sysadmin and this is not allowed in my company.
> Is there other way?
>
> Sue Hoegemeier wrote:
>>Maybe something using a job step of raiserror with log as a
>>failure branch in the job might work for you.
>>-Sue
>>I have a special necessity in which I need that the result of failed jobs in
>>SQL Server Agent be logged as errors in Windows Event Viewer.
>>[quoted text clipped - 12 lines]
>>Thanks
>|||Tibor Karaszi wrote:
>xp_logevent?
>> Thanks for your reply Sue.
>[quoted text clipped - 13 lines]
>>Thanks
I order to run it, the user also has to be sysyadmin or db_owner of the
master database and there is a policy in my company that does not allow it.
So that does not solve my problem yet, but thanks.|||> I order to run it, the user also has to be sysyadmin or db_owner
Did you try it? Below executes just fine on my 2005 installation:
CREATE LOGIN x WITH PASSWORD = 'y'
CREATE USER x
GRANT EXECUTE ON xp_logevent TO x
EXECUTE AS LOGIN = 'X'
GO
EXEC xp_logevent 50001, 'My error', 'ERROR'
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jaimefelipe" <u27450@.uwe> wrote in message news:673aaf26ce58d@.uwe...
> Tibor Karaszi wrote:
>>xp_logevent?
>> Thanks for your reply Sue.
>>[quoted text clipped - 13 lines]
>>Thanks
>
> I order to run it, the user also has to be sysyadmin or db_owner of the
> master database and there is a policy in my company that does not allow it.
> So that does not solve my problem yet, but thanks.
>

Job entries in eventlist

Hi all
in enterprise manager of aur SQL-Server 2000, we defined some backup-jobs.
All these jobs are logged in the eventlist, although the control field in th
e
job proprties are deactivated. The list contains tons of event entries every
day of all backups and so much the worse die log backups.
It's this a fault in the enterprise manager or SQL-server? And, have any one
a reason for this problem?
Thanks
FieteIf I understand you question correctly:
It isn't Agent that log each time a backup is performed. It is SLQ Server.
And you cannot turn it
off, I'm afraid. Considering posting such a request to sqlwish@.microsoft.com
.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Fiete" <Fiete@.discussions.microsoft.com> wrote in message
news:AC1F6A5E-64E4-48CB-AD8E-BA39535BFD37@.microsoft.com...
> Hi all
> in enterprise manager of aur SQL-Server 2000, we defined some backup-jobs.
> All these jobs are logged in the eventlist, although the control field in
the
> job proprties are deactivated. The list contains tons of event entries eve
ry
> day of all backups and so much the worse die log backups.
> It's this a fault in the enterprise manager or SQL-server? And, have any o
ne
> a reason for this problem?
> Thanks
> Fiete

Job entries in eventlist

Hi all
in enterprise manager of aur SQL-Server 2000, we defined some backup-jobs.
All these jobs are logged in the eventlist, although the control field in the
job proprties are deactivated. The list contains tons of event entries every
day of all backups and so much the worse die log backups.
It's this a fault in the enterprise manager or SQL-server? And, have any one
a reason for this problem?
Thanks
FieteIf I understand you question correctly:
It isn't Agent that log each time a backup is performed. It is SLQ Server. And you cannot turn it
off, I'm afraid. Considering posting such a request to sqlwish@.microsoft.com.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Fiete" <Fiete@.discussions.microsoft.com> wrote in message
news:AC1F6A5E-64E4-48CB-AD8E-BA39535BFD37@.microsoft.com...
> Hi all
> in enterprise manager of aur SQL-Server 2000, we defined some backup-jobs.
> All these jobs are logged in the eventlist, although the control field in the
> job proprties are deactivated. The list contains tons of event entries every
> day of all backups and so much the worse die log backups.
> It's this a fault in the enterprise manager or SQL-server? And, have any one
> a reason for this problem?
> Thanks
> Fiete

Job entries in eventlist

Hi all
in enterprise manager of aur SQL-Server 2000, we defined some backup-jobs.
All these jobs are logged in the eventlist, although the control field in the
job proprties are deactivated. The list contains tons of event entries every
day of all backups and so much the worse die log backups.
It's this a fault in the enterprise manager or SQL-server? And, have any one
a reason for this problem?
Thanks
Fiete
If I understand you question correctly:
It isn't Agent that log each time a backup is performed. It is SLQ Server. And you cannot turn it
off, I'm afraid. Considering posting such a request to sqlwish@.microsoft.com.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Fiete" <Fiete@.discussions.microsoft.com> wrote in message
news:AC1F6A5E-64E4-48CB-AD8E-BA39535BFD37@.microsoft.com...
> Hi all
> in enterprise manager of aur SQL-Server 2000, we defined some backup-jobs.
> All these jobs are logged in the eventlist, although the control field in the
> job proprties are deactivated. The list contains tons of event entries every
> day of all backups and so much the worse die log backups.
> It's this a fault in the enterprise manager or SQL-server? And, have any one
> a reason for this problem?
> Thanks
> Fiete