Good morning,
What I can do to allow developers have access to view the jobs I created
with out giving them administrator permission?
Thanks.Hi
Doesn't member of db_owner fixed database role have an access to the jobs?
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:4315658A-3079-41F7-B8E9-45225924CDAF@.microsoft.com...
> Good morning,
> What I can do to allow developers have access to view the jobs I created
> with out giving them administrator permission?
> Thanks.|||Thans. but I don't want them to be a member of db_owner.
"Uri Dimant" wrote:
> Hi
> Doesn't member of db_owner fixed database role have an access to the job
s?
>
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:4315658A-3079-41F7-B8E9-45225924CDAF@.microsoft.com...
>
>|||There are no special roles for job management in 2000. There are in 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:4315658A-3079-41F7-B8E9-45225924CDAF@.microsoft.com...
> Good morning,
> What I can do to allow developers have access to view the jobs I created
> with out giving them administrator permission?
> Thanks.|||There is a role in msdb called TargetserverRole, which allows members to vie
w
the jobs in EM.
Just keep in mind this is undocumented and subject to change. For instance,
permissions this role had were changed with SP3. So if you make use of it,
test in dev before slapping SP4 on in production (if/when it comes out).
I got above info from following discussion at sqlservercentral:
[url]http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=108953[
/url]
"Matthew Z" wrote:
> Good morning,
> What I can do to allow developers have access to view the jobs I created
> with out giving them administrator permission?
> Thanks.
Showing posts with label view. Show all posts
Showing posts with label view. Show all posts
Friday, March 30, 2012
Job View History is disappearing
I've created new maintenance plans and while I can view the maintenance plan
history, the job view history is deleted somehow. Where is this controlled?
The maintenance plan is not deleting job history and I don't see any other
jobs or maintenance plans that are deleting history.
This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
the job history, but I don't see that in 2005. Is there a default somewhere
I'm missing?
Thanks
RonRon,
In SSMS, right-click on SQL Agent, select Properties, go to the History
page. This is where you can set the size of history.
RLF
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:0EB1F324-BF2B-4F24-87AC-585FAB4071E3@.microsoft.com...
> I've created new maintenance plans and while I can view the maintenance
> plan
> history, the job view history is deleted somehow. Where is this
> controlled?
> The maintenance plan is not deleting job history and I don't see any
> other
> jobs or maintenance plans that are deleting history.
> This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
> the job history, but I don't see that in 2005. Is there a default
> somewhere
> I'm missing?
> Thanks
> Ron|||Thanks - I'll bump it up and see if that's the issue.
"Russell Fields" wrote:
> Ron,
> In SSMS, right-click on SQL Agent, select Properties, go to the History
> page. This is where you can set the size of history.
> RLF
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:0EB1F324-BF2B-4F24-87AC-585FAB4071E3@.microsoft.com...
> > I've created new maintenance plans and while I can view the maintenance
> > plan
> > history, the job view history is deleted somehow. Where is this
> > controlled?
> > The maintenance plan is not deleting job history and I don't see any
> > other
> > jobs or maintenance plans that are deleting history.
> >
> > This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
> > the job history, but I don't see that in 2005. Is there a default
> > somewhere
> > I'm missing?
> >
> > Thanks
> >
> > Ron
>
>
history, the job view history is deleted somehow. Where is this controlled?
The maintenance plan is not deleting job history and I don't see any other
jobs or maintenance plans that are deleting history.
This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
the job history, but I don't see that in 2005. Is there a default somewhere
I'm missing?
Thanks
RonRon,
In SSMS, right-click on SQL Agent, select Properties, go to the History
page. This is where you can set the size of history.
RLF
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:0EB1F324-BF2B-4F24-87AC-585FAB4071E3@.microsoft.com...
> I've created new maintenance plans and while I can view the maintenance
> plan
> history, the job view history is deleted somehow. Where is this
> controlled?
> The maintenance plan is not deleting job history and I don't see any
> other
> jobs or maintenance plans that are deleting history.
> This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
> the job history, but I don't see that in 2005. Is there a default
> somewhere
> I'm missing?
> Thanks
> Ron|||Thanks - I'll bump it up and see if that's the issue.
"Russell Fields" wrote:
> Ron,
> In SSMS, right-click on SQL Agent, select Properties, go to the History
> page. This is where you can set the size of history.
> RLF
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:0EB1F324-BF2B-4F24-87AC-585FAB4071E3@.microsoft.com...
> > I've created new maintenance plans and while I can view the maintenance
> > plan
> > history, the job view history is deleted somehow. Where is this
> > controlled?
> > The maintenance plan is not deleting job history and I don't see any
> > other
> > jobs or maintenance plans that are deleting history.
> >
> > This is SQL2005 SE SP2. I remember in SQL2000 you could limit the size of
> > the job history, but I don't see that in 2005. Is there a default
> > somewhere
> > I'm missing?
> >
> > Thanks
> >
> > Ron
>
>
Friday, March 23, 2012
Job Schedule
I would like to view all the scheduled jobs , sorted by Next Run Date. When
I use Enterprise Manager and sort by that column, they are not sorted
correctly.
Suggestions?Hopefully following query can give you the required result.
select sj.name, sj.description,
case sj.enabled
when 0 then 'Enabled'
else 'Disabled' end as 'Job Status',
sjs.next_run_date,
right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
where sj.job_id = sjs.job_id
order by sjs.next_run_date, sjs.next_run_time
Please let us know whether this helped you or not?
"John Carlton" wrote:
> I would like to view all the scheduled jobs , sorted by Next Run Date. When
> I use Enterprise Manager and sort by that column, they are not sorted
> correctly.
> Suggestions?|||Yes, perfect. Thanks!
"Absar Ahmad" wrote:
> Hopefully following query can give you the required result.
> select sj.name, sj.description,
> case sj.enabled
> when 0 then 'Enabled'
> else 'Disabled' end as 'Job Status',
> sjs.next_run_date,
> right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
> from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
> where sj.job_id = sjs.job_id
> order by sjs.next_run_date, sjs.next_run_time
> Please let us know whether this helped you or not?
> "John Carlton" wrote:
> > I would like to view all the scheduled jobs , sorted by Next Run Date. When
> > I use Enterprise Manager and sort by that column, they are not sorted
> > correctly.
> > Suggestions?
I use Enterprise Manager and sort by that column, they are not sorted
correctly.
Suggestions?Hopefully following query can give you the required result.
select sj.name, sj.description,
case sj.enabled
when 0 then 'Enabled'
else 'Disabled' end as 'Job Status',
sjs.next_run_date,
right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
where sj.job_id = sjs.job_id
order by sjs.next_run_date, sjs.next_run_time
Please let us know whether this helped you or not?
"John Carlton" wrote:
> I would like to view all the scheduled jobs , sorted by Next Run Date. When
> I use Enterprise Manager and sort by that column, they are not sorted
> correctly.
> Suggestions?|||Yes, perfect. Thanks!
"Absar Ahmad" wrote:
> Hopefully following query can give you the required result.
> select sj.name, sj.description,
> case sj.enabled
> when 0 then 'Enabled'
> else 'Disabled' end as 'Job Status',
> sjs.next_run_date,
> right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
> from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
> where sj.job_id = sjs.job_id
> order by sjs.next_run_date, sjs.next_run_time
> Please let us know whether this helped you or not?
> "John Carlton" wrote:
> > I would like to view all the scheduled jobs , sorted by Next Run Date. When
> > I use Enterprise Manager and sort by that column, they are not sorted
> > correctly.
> > Suggestions?
Job Schedule
I would like to view all the scheduled jobs , sorted by Next Run Date. When
I use Enterprise Manager and sort by that column, they are not sorted
correctly.
Suggestions?Hopefully following query can give you the required result.
select sj.name, sj.description,
case sj.enabled
when 0 then 'Enabled'
else 'Disabled' end as 'Job Status',
sjs.next_run_date,
right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
where sj.job_id = sjs.job_id
order by sjs.next_run_date, sjs.next_run_time
Please let us know whether this helped you or not?
"John Carlton" wrote:
> I would like to view all the scheduled jobs , sorted by Next Run Date. Wh
en
> I use Enterprise Manager and sort by that column, they are not sorted
> correctly.
> Suggestions?|||Yes, perfect. Thanks!
"Absar Ahmad" wrote:
[vbcol=seagreen]
> Hopefully following query can give you the required result.
> select sj.name, sj.description,
> case sj.enabled
> when 0 then 'Enabled'
> else 'Disabled' end as 'Job Status',
> sjs.next_run_date,
> right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
> from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
> where sj.job_id = sjs.job_id
> order by sjs.next_run_date, sjs.next_run_time
> Please let us know whether this helped you or not?
> "John Carlton" wrote:
>
I use Enterprise Manager and sort by that column, they are not sorted
correctly.
Suggestions?Hopefully following query can give you the required result.
select sj.name, sj.description,
case sj.enabled
when 0 then 'Enabled'
else 'Disabled' end as 'Job Status',
sjs.next_run_date,
right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
where sj.job_id = sjs.job_id
order by sjs.next_run_date, sjs.next_run_time
Please let us know whether this helped you or not?
"John Carlton" wrote:
> I would like to view all the scheduled jobs , sorted by Next Run Date. Wh
en
> I use Enterprise Manager and sort by that column, they are not sorted
> correctly.
> Suggestions?|||Yes, perfect. Thanks!
"Absar Ahmad" wrote:
[vbcol=seagreen]
> Hopefully following query can give you the required result.
> select sj.name, sj.description,
> case sj.enabled
> when 0 then 'Enabled'
> else 'Disabled' end as 'Job Status',
> sjs.next_run_date,
> right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
> from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
> where sj.job_id = sjs.job_id
> order by sjs.next_run_date, sjs.next_run_time
> Please let us know whether this helped you or not?
> "John Carlton" wrote:
>
Job Schedule
I would like to view all the scheduled jobs , sorted by Next Run Date. When
I use Enterprise Manager and sort by that column, they are not sorted
correctly.
Suggestions?
Hopefully following query can give you the required result.
select sj.name, sj.description,
case sj.enabled
when 0 then 'Enabled'
else 'Disabled' end as 'Job Status',
sjs.next_run_date,
right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
where sj.job_id = sjs.job_id
order by sjs.next_run_date, sjs.next_run_time
Please let us know whether this helped you or not?
"John Carlton" wrote:
> I would like to view all the scheduled jobs , sorted by Next Run Date. When
> I use Enterprise Manager and sort by that column, they are not sorted
> correctly.
> Suggestions?
|||Yes, perfect. Thanks!
"Absar Ahmad" wrote:
[vbcol=seagreen]
> Hopefully following query can give you the required result.
> select sj.name, sj.description,
> case sj.enabled
> when 0 then 'Enabled'
> else 'Disabled' end as 'Job Status',
> sjs.next_run_date,
> right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
> from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
> where sj.job_id = sjs.job_id
> order by sjs.next_run_date, sjs.next_run_time
> Please let us know whether this helped you or not?
> "John Carlton" wrote:
sql
I use Enterprise Manager and sort by that column, they are not sorted
correctly.
Suggestions?
Hopefully following query can give you the required result.
select sj.name, sj.description,
case sj.enabled
when 0 then 'Enabled'
else 'Disabled' end as 'Job Status',
sjs.next_run_date,
right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
where sj.job_id = sjs.job_id
order by sjs.next_run_date, sjs.next_run_time
Please let us know whether this helped you or not?
"John Carlton" wrote:
> I would like to view all the scheduled jobs , sorted by Next Run Date. When
> I use Enterprise Manager and sort by that column, they are not sorted
> correctly.
> Suggestions?
|||Yes, perfect. Thanks!
"Absar Ahmad" wrote:
[vbcol=seagreen]
> Hopefully following query can give you the required result.
> select sj.name, sj.description,
> case sj.enabled
> when 0 then 'Enabled'
> else 'Disabled' end as 'Job Status',
> sjs.next_run_date,
> right('000000' + convert(varchar(6),sjs.next_run_time),6) 'Next Run Time'
> from msdb.dbo.sysjobs sj, msdb.dbo.sysjobschedules sjs
> where sj.job_id = sjs.job_id
> order by sjs.next_run_date, sjs.next_run_time
> Please let us know whether this helped you or not?
> "John Carlton" wrote:
sql
Job reports failure, but bak file created
The view history of a job created from a maintenance plan reports that it
failed, and the log says that it failed in the backup operation because
"A nonrecoverable I/O error occurred on file
"\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707110001.bak:" 64(The specified network name is no longer available.).
And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it was a
valid backup, as I just confirmed by restoring it to a test database. So why
the error?
Also, this does not happen consistently. The reporting of this apparent
non-error has occured twice out of the last five runs.Does the backup process include a Verify? IF so the error is most likely
occurring on the verify process which is done after the backup is complete.
Backup & Verify is an intensive operation and if you are backing up across
the network there is plenty of time for the network to drop packets etc.
Sounds like you have an unstable network or networks equipment.
--
Andrew J. Kelly SQL MVP
"Bev Kaufman" <BevKaufman@.discussions.microsoft.com> wrote in message
news:AF302871-2972-420D-A932-408F42EA1EA9@.microsoft.com...
> The view history of a job created from a maintenance plan reports that it
> failed, and the log says that it failed in the backup operation because
> "A nonrecoverable I/O error occurred on file
> "\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707110001.bak:"
> 64(The specified network name is no longer available.).
> And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it was
> a
> valid backup, as I just confirmed by restoring it to a test database. So
> why
> the error?
> Also, this does not happen consistently. The reporting of this apparent
> non-error has occured twice out of the last five runs.|||On Jul 11, 9:16 am, Bev Kaufman <BevKauf...@.discussions.microsoft.com>
wrote:
> The view history of a job created from a maintenance plan reports that it
> failed, and the log says that it failed in the backup operation because
> "A nonrecoverable I/O error occurred on file
> "\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707=11=AD0001.bak:" 64(The specified network name is no longer available.).
> And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it wa=s a
> valid backup, as I just confirmed by restoring it to a test database. So= why
> the error?
> Also, this does not happen consistently. The reporting of this apparent
> non-error has occured twice out of the last five runs.
Are you utilizing a third party backup tool? We use RedGate in our
SQL Server 2000 (SP3a - don't ask) environment and have encountered
this on a daily basis. When we used normal backup procedures, no
errors were reported. I have the same issue though, but figured it
might be resolved with a newer service pack. The only thing I can
think of is possibly disk contention of you are utilizing a SAN
environment, but not sure.
Maybe if we put our heads together, we can figure it out. I haven't
put a whole lot of effort into it once I realized that the backups are
working properly (as verified by the restores). I know, terrible, but
sometimes other fires are hotter :)
failed, and the log says that it failed in the backup operation because
"A nonrecoverable I/O error occurred on file
"\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707110001.bak:" 64(The specified network name is no longer available.).
And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it was a
valid backup, as I just confirmed by restoring it to a test database. So why
the error?
Also, this does not happen consistently. The reporting of this apparent
non-error has occured twice out of the last five runs.Does the backup process include a Verify? IF so the error is most likely
occurring on the verify process which is done after the backup is complete.
Backup & Verify is an intensive operation and if you are backing up across
the network there is plenty of time for the network to drop packets etc.
Sounds like you have an unstable network or networks equipment.
--
Andrew J. Kelly SQL MVP
"Bev Kaufman" <BevKaufman@.discussions.microsoft.com> wrote in message
news:AF302871-2972-420D-A932-408F42EA1EA9@.microsoft.com...
> The view history of a job created from a maintenance plan reports that it
> failed, and the log says that it failed in the backup operation because
> "A nonrecoverable I/O error occurred on file
> "\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707110001.bak:"
> 64(The specified network name is no longer available.).
> And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it was
> a
> valid backup, as I just confirmed by restoring it to a test database. So
> why
> the error?
> Also, this does not happen consistently. The reporting of this apparent
> non-error has occured twice out of the last five runs.|||On Jul 11, 9:16 am, Bev Kaufman <BevKauf...@.discussions.microsoft.com>
wrote:
> The view history of a job created from a maintenance plan reports that it
> failed, and the log says that it failed in the backup operation because
> "A nonrecoverable I/O error occurred on file
> "\\\\BIGPETE\\E\\data\\Backups\\Daily\\MCR_SFPMS\\MCR_SFPMS_backup_200707=11=AD0001.bak:" 64(The specified network name is no longer available.).
> And yet MCR_SFPMS_backup_200707110001.bak does exist, and moreover, it wa=s a
> valid backup, as I just confirmed by restoring it to a test database. So= why
> the error?
> Also, this does not happen consistently. The reporting of this apparent
> non-error has occured twice out of the last five runs.
Are you utilizing a third party backup tool? We use RedGate in our
SQL Server 2000 (SP3a - don't ask) environment and have encountered
this on a daily basis. When we used normal backup procedures, no
errors were reported. I have the same issue though, but figured it
might be resolved with a newer service pack. The only thing I can
think of is possibly disk contention of you are utilizing a SAN
environment, but not sure.
Maybe if we put our heads together, we can figure it out. I haven't
put a whole lot of effort into it once I realized that the backups are
working properly (as verified by the restores). I know, terrible, but
sometimes other fires are hotter :)
Wednesday, March 21, 2012
Job History hangs Enterprise Manager
Hi
I have Enterprise Manager on my local machine and administer a server from
it. When I go to jobs and right click and choose view job history I get an
hour glass and then EM Hangs and also pretty much kills my machine.
Has this happened to anyone else? Is there a reason and/or fix for it?
It only seems to happen on one server and I administer several others from
my machine with no problem. I am running SQL Server 2000 SP4
I have google but couldn't find anything helpfull.
ThanksHi
I am not sure about your particular problem you may want to use SQL Profiler
to check out what SQL it is running and/or run sp_help_jobhistory from Query
Analyser. If you have a very long job history you could run
sp_purge_jobhistory to remove it.
Other things you may want to do is to run DBCC CHECKDB on MSDB.
John
"Bri" wrote:
> Hi
> I have Enterprise Manager on my local machine and administer a server from
> it. When I go to jobs and right click and choose view job history I get an
> hour glass and then EM Hangs and also pretty much kills my machine.
> Has this happened to anyone else? Is there a reason and/or fix for it?
> It only seems to happen on one server and I administer several others from
> my machine with no problem. I am running SQL Server 2000 SP4
> I have google but couldn't find anything helpfull.
> Thanks
>|||Bri wrote:
> Hi
> I have Enterprise Manager on my local machine and administer a server from
> it. When I go to jobs and right click and choose view job history I get an
> hour glass and then EM Hangs and also pretty much kills my machine.
> Has this happened to anyone else? Is there a reason and/or fix for it?
> It only seems to happen on one server and I administer several others from
> my machine with no problem. I am running SQL Server 2000 SP4
> I have google but couldn't find anything helpfull.
> Thanks
>
When it "hangs", open up Query Analyzer and look at sysprocesses on the
server, see if there is something blocking you, or if there is a
waittype specified for your spid. You could just have an exceptionally
long history for the given job.
I have Enterprise Manager on my local machine and administer a server from
it. When I go to jobs and right click and choose view job history I get an
hour glass and then EM Hangs and also pretty much kills my machine.
Has this happened to anyone else? Is there a reason and/or fix for it?
It only seems to happen on one server and I administer several others from
my machine with no problem. I am running SQL Server 2000 SP4
I have google but couldn't find anything helpfull.
ThanksHi
I am not sure about your particular problem you may want to use SQL Profiler
to check out what SQL it is running and/or run sp_help_jobhistory from Query
Analyser. If you have a very long job history you could run
sp_purge_jobhistory to remove it.
Other things you may want to do is to run DBCC CHECKDB on MSDB.
John
"Bri" wrote:
> Hi
> I have Enterprise Manager on my local machine and administer a server from
> it. When I go to jobs and right click and choose view job history I get an
> hour glass and then EM Hangs and also pretty much kills my machine.
> Has this happened to anyone else? Is there a reason and/or fix for it?
> It only seems to happen on one server and I administer several others from
> my machine with no problem. I am running SQL Server 2000 SP4
> I have google but couldn't find anything helpfull.
> Thanks
>|||Bri wrote:
> Hi
> I have Enterprise Manager on my local machine and administer a server from
> it. When I go to jobs and right click and choose view job history I get an
> hour glass and then EM Hangs and also pretty much kills my machine.
> Has this happened to anyone else? Is there a reason and/or fix for it?
> It only seems to happen on one server and I administer several others from
> my machine with no problem. I am running SQL Server 2000 SP4
> I have google but couldn't find anything helpfull.
> Thanks
>
When it "hangs", open up Query Analyzer and look at sysprocesses on the
server, see if there is something blocking you, or if there is a
waittype specified for your spid. You could just have an exceptionally
long history for the given job.
Monday, March 19, 2012
Job History
If you right click on job (in 2000) and do View History, Ent Mgr displays
(from what i can tell) only a certain number of lines. But I have a job that
runs every couple of minutes and I need to see much more history than that.
Is there somewhere this information is kept and is there a way I can change
the default on the number of history lines? Thx...
You should probably just query the DB. See MSDB.dbo.sysjobhistory
Ryan
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
that
> runs every couple of minutes and I need to see much more history than
that.
> Is there somewhere this information is kept and is there a way I can
change
> the default on the number of history lines? Thx...
|||Right click on the SQL Agent folder and choose properties. Then have a look
at the tabs and you will see a place to change the history retention
settings.
Andrew J. Kelly SQL MVP
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
> that
> runs every couple of minutes and I need to see much more history than
> that.
> Is there somewhere this information is kept and is there a way I can
> change
> the default on the number of history lines? Thx...
(from what i can tell) only a certain number of lines. But I have a job that
runs every couple of minutes and I need to see much more history than that.
Is there somewhere this information is kept and is there a way I can change
the default on the number of history lines? Thx...
You should probably just query the DB. See MSDB.dbo.sysjobhistory
Ryan
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
that
> runs every couple of minutes and I need to see much more history than
that.
> Is there somewhere this information is kept and is there a way I can
change
> the default on the number of history lines? Thx...
|||Right click on the SQL Agent folder and choose properties. Then have a look
at the tabs and you will see a place to change the history retention
settings.
Andrew J. Kelly SQL MVP
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
> that
> runs every couple of minutes and I need to see much more history than
> that.
> Is there somewhere this information is kept and is there a way I can
> change
> the default on the number of history lines? Thx...
Job History
If you right click on job (in 2000) and do View History, Ent Mgr displays
(from what i can tell) only a certain number of lines. But I have a job tha
t
runs every couple of minutes and I need to see much more history than that.
Is there somewhere this information is kept and is there a way I can change
the default on the number of history lines? Thx...You should probably just query the DB. See MSDB.dbo.sysjobhistory
Ryan
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
that
> runs every couple of minutes and I need to see much more history than
that.
> Is there somewhere this information is kept and is there a way I can
change
> the default on the number of history lines? Thx...|||Right click on the SQL Agent folder and choose properties. Then have a look
at the tabs and you will see a place to change the history retention
settings.
Andrew J. Kelly SQL MVP
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
> that
> runs every couple of minutes and I need to see much more history than
> that.
> Is there somewhere this information is kept and is there a way I can
> change
> the default on the number of history lines? Thx...
(from what i can tell) only a certain number of lines. But I have a job tha
t
runs every couple of minutes and I need to see much more history than that.
Is there somewhere this information is kept and is there a way I can change
the default on the number of history lines? Thx...You should probably just query the DB. See MSDB.dbo.sysjobhistory
Ryan
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
that
> runs every couple of minutes and I need to see much more history than
that.
> Is there somewhere this information is kept and is there a way I can
change
> the default on the number of history lines? Thx...|||Right click on the SQL Agent folder and choose properties. Then have a look
at the tabs and you will see a place to change the history retention
settings.
Andrew J. Kelly SQL MVP
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
> that
> runs every couple of minutes and I need to see much more history than
> that.
> Is there somewhere this information is kept and is there a way I can
> change
> the default on the number of history lines? Thx...
Job History
If you right click on job (in 2000) and do View History, Ent Mgr displays
(from what i can tell) only a certain number of lines. But I have a job that
runs every couple of minutes and I need to see much more history than that.
Is there somewhere this information is kept and is there a way I can change
the default on the number of history lines? Thx...You should probably just query the DB. See MSDB.dbo.sysjobhistory
Ryan
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
that
> runs every couple of minutes and I need to see much more history than
that.
> Is there somewhere this information is kept and is there a way I can
change
> the default on the number of history lines? Thx...|||Right click on the SQL Agent folder and choose properties. Then have a look
at the tabs and you will see a place to change the history retention
settings.
--
Andrew J. Kelly SQL MVP
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
> that
> runs every couple of minutes and I need to see much more history than
> that.
> Is there somewhere this information is kept and is there a way I can
> change
> the default on the number of history lines? Thx...
(from what i can tell) only a certain number of lines. But I have a job that
runs every couple of minutes and I need to see much more history than that.
Is there somewhere this information is kept and is there a way I can change
the default on the number of history lines? Thx...You should probably just query the DB. See MSDB.dbo.sysjobhistory
Ryan
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
that
> runs every couple of minutes and I need to see much more history than
that.
> Is there somewhere this information is kept and is there a way I can
change
> the default on the number of history lines? Thx...|||Right click on the SQL Agent folder and choose properties. Then have a look
at the tabs and you will see a place to change the history retention
settings.
--
Andrew J. Kelly SQL MVP
"CLM" <CLM@.discussions.microsoft.com> wrote in message
news:BEC60862-A013-4509-80CD-2259731B5DEC@.microsoft.com...
> If you right click on job (in 2000) and do View History, Ent Mgr displays
> (from what i can tell) only a certain number of lines. But I have a job
> that
> runs every couple of minutes and I need to see much more history than
> that.
> Is there somewhere this information is kept and is there a way I can
> change
> the default on the number of history lines? Thx...
Monday, March 12, 2012
job fails
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.look here
http://support.microsoft.com/default.aspx?scid=kb;en-us;223758
Originally posted by aadil
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.|||Also
http://search.microsoft.com/search/results.aspx?st=b&na=83&qu=80040E14&View=en-us
Originally posted by aadil
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.|||Also this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q269074 to schedule DTS as job and resolve the issue.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.look here
http://support.microsoft.com/default.aspx?scid=kb;en-us;223758
Originally posted by aadil
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.|||Also
http://search.microsoft.com/search/results.aspx?st=b&na=83&qu=80040E14&View=en-us
Originally posted by aadil
I have a DTS job that runs every hour.
it truncates destination table and copies from the source table.
it has failed with the following error in view job history
"error-214721900(80040E14);provider error 14262.(37B6)"
error source Microsoft ole db provider error
pls help in this
how can i solve this, i tried restarting the job but its failing again.|||Also this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q269074 to schedule DTS as job and resolve the issue.
Subscribe to:
Posts (Atom)