Question on Job history

Please could someone enlight me.
In enterprise manager -> management-> jobs -> view history
I could normally see the historic runs of the jobs.
I have a server, for some reason, only hold one historic
record of each job. Each time a job is run the history is
then refreshed and delete with only the latest job remain.
Where can I set in Enterprise Manager so I could adjust
the amount of the history held for the jobs?
Thanks
AlexAlex Au wrote:

> Please could someone enlight me.
> In enterprise manager -> management-> jobs -> view history
> I could normally see the historic runs of the jobs.
> I have a server, for some reason, only hold one historic
> record of each job. Each time a job is run the history is
> then refreshed and delete with only the latest job remain.
See How to resize the job history log (Enterprise Manager)
http://msdn.microsoft.com/library/d...>
aem_8xpj.asp
Why not create Your Own SQL Server Job Management System?
http://www.sql-server-performance.com/rd_jobs.asp
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Sebastian
Thanks for this. I have checked and found that the Job
agent setting no different from other servers. I think the
real issue seem to be in the time the job history are
kept.. All the jobs that have only one history are only
run once a month, and I have jobs that run daily - they
have all the job history up to a month.
Alex
>--Original Message--
>Alex Au wrote:
>
history
is
remain.
>
>See How to resize the job history log (Enterprise Manager)
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>Why not create Your Own SQL Server Job Management System?
>http://www.sql-server-performance.com/rd_jobs.asp
>sincerely,
>--
>Sebastian K. Zaklada
>Skilled Software
>http://www.skilledsoftware.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>|||The trouble is that if you have a job that runs very often e.g once every
minute, it can quickly eat up the 1000 rows that is the default job history
log size. This setting applies to the server so even if the job history rows
per job is 100, it will not honour this if the max history log size >1000.
Thus it might be worth lowering the rows per job and increasing the max log
size to find the balance that works for you.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:2d9401c40075$21391820$a601280a@.phx.gbl...
> Sebastian
> Thanks for this. I have checked and found that the Job
> agent setting no different from other servers. I think the
> real issue seem to be in the time the job history are
> kept.. All the jobs that have only one history are only
> run once a month, and I have jobs that run daily - they
> have all the job history up to a month.
> Alex
> history
> is
> remain.
> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
> confers no rights.|||Thanks Jasper. This is exactly the problem, and your
suggested solution is spot on.
Alex
>--Original Message--
>The trouble is that if you have a job that runs very
often e.g once every
>minute, it can quickly eat up the 1000 rows that is the
default job history
>log size. This setting applies to the server so even if
the job history rows
>per job is 100, it will not honour this if the max
history log size >1000.
>Thus it might be worth lowering the rows per job and
increasing the max log
>size to find the balance that works for you.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:2d9401c40075$21391820$a601280a@.phx.gbl...
the
historic
history
Manager)
System?
and
>
>.
>

Question on Job history

Please could someone enlight me.
In enterprise manager -> management-> jobs -> view history
I could normally see the historic runs of the jobs.
I have a server, for some reason, only hold one historic
record of each job. Each time a job is run the history is
then refreshed and delete with only the latest job remain.
Where can I set in Enterprise Manager so I could adjust
the amount of the history held for the jobs?
Thanks
AlexAlex Au wrote:
> Please could someone enlight me.
> In enterprise manager -> management-> jobs -> view history
> I could normally see the historic runs of the jobs.
> I have a server, for some reason, only hold one historic
> record of each job. Each time a job is run the history is
> then refreshed and delete with only the latest job remain.
See How to resize the job history log (Enterprise Manager)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_automaem_8xpj.asp
Why not create Your Own SQL Server Job Management System?
http://www.sql-server-performance.com/rd_jobs.asp
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Sebastian
Thanks for this. I have checked and found that the Job
agent setting no different from other servers. I think the
real issue seem to be in the time the job history are
kept.. All the jobs that have only one history are only
run once a month, and I have jobs that run daily - they
have all the job history up to a month.
Alex
>--Original Message--
>Alex Au wrote:
>> Please could someone enlight me.
>> In enterprise manager -> management-> jobs -> view
history
>> I could normally see the historic runs of the jobs.
>> I have a server, for some reason, only hold one historic
>> record of each job. Each time a job is run the history
is
>> then refreshed and delete with only the latest job
remain.
>
>See How to resize the job history log (Enterprise Manager)
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>Why not create Your Own SQL Server Job Management System?
>http://www.sql-server-performance.com/rd_jobs.asp
>sincerely,
>--
>Sebastian K. Zaklada
>Skilled Software
>http://www.skilledsoftware.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>|||The trouble is that if you have a job that runs very often e.g once every
minute, it can quickly eat up the 1000 rows that is the default job history
log size. This setting applies to the server so even if the job history rows
per job is 100, it will not honour this if the max history log size >1000.
Thus it might be worth lowering the rows per job and increasing the max log
size to find the balance that works for you.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:2d9401c40075$21391820$a601280a@.phx.gbl...
> Sebastian
> Thanks for this. I have checked and found that the Job
> agent setting no different from other servers. I think the
> real issue seem to be in the time the job history are
> kept.. All the jobs that have only one history are only
> run once a month, and I have jobs that run daily - they
> have all the job history up to a month.
> Alex
> >--Original Message--
> >Alex Au wrote:
> >
> >> Please could someone enlight me.
> >>
> >> In enterprise manager -> management-> jobs -> view
> history
> >> I could normally see the historic runs of the jobs.
> >>
> >> I have a server, for some reason, only hold one historic
> >> record of each job. Each time a job is run the history
> is
> >> then refreshed and delete with only the latest job
> remain.
> >
> >
> >See How to resize the job history log (Enterprise Manager)
> >http://msdn.microsoft.com/library/default.asp?
> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
> >
> >Why not create Your Own SQL Server Job Management System?
> >http://www.sql-server-performance.com/rd_jobs.asp
> >
> >sincerely,
> >--
> >Sebastian K. Zaklada
> >Skilled Software
> >http://www.skilledsoftware.com
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >.
> >|||Thanks Jasper. This is exactly the problem, and your
suggested solution is spot on.
Alex
>--Original Message--
>The trouble is that if you have a job that runs very
often e.g once every
>minute, it can quickly eat up the 1000 rows that is the
default job history
>log size. This setting applies to the server so even if
the job history rows
>per job is 100, it will not honour this if the max
history log size >1000.
>Thus it might be worth lowering the rows per job and
increasing the max log
>size to find the balance that works for you.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:2d9401c40075$21391820$a601280a@.phx.gbl...
>> Sebastian
>> Thanks for this. I have checked and found that the Job
>> agent setting no different from other servers. I think
the
>> real issue seem to be in the time the job history are
>> kept.. All the jobs that have only one history are only
>> run once a month, and I have jobs that run daily - they
>> have all the job history up to a month.
>> Alex
>> >--Original Message--
>> >Alex Au wrote:
>> >
>> >> Please could someone enlight me.
>> >>
>> >> In enterprise manager -> management-> jobs -> view
>> history
>> >> I could normally see the historic runs of the jobs.
>> >>
>> >> I have a server, for some reason, only hold one
historic
>> >> record of each job. Each time a job is run the
history
>> is
>> >> then refreshed and delete with only the latest job
>> remain.
>> >
>> >
>> >See How to resize the job history log (Enterprise
Manager)
>> >http://msdn.microsoft.com/library/default.asp?
>> url=/library/en-us/howtosql/ht_automaem_8xpj.asp
>> >
>> >Why not create Your Own SQL Server Job Management
System?
>> >http://www.sql-server-performance.com/rd_jobs.asp
>> >
>> >sincerely,
>> >--
>> >Sebastian K. Zaklada
>> >Skilled Software
>> >http://www.skilledsoftware.com
>> >This posting is provided "AS IS" with no warranties,
and
>> confers no rights.
>> >
>> >
>> >.
>> >
>
>.
>

Question on automatic copying table from one datbase to another on same SQL Serv

Currently have two databases. A live database and a history database. Also have the ability to purge data from the live to the history database. What I'm looking for is the ability, if the table doesn't exist in history, to automatically create the table in the history database using the format of the table within the live database. Any help would be greatly appreciated. ThanksLog Shipping sounds like a plan

[BOL] Log shipping|||Originally posted by Ruprect
Log Shipping sounds like a plan

[BOL] Log shipping Within the same server? Kinda overkill, isn't it?|||live to history kinda set me off i'm working on something like this right now so i have log shipping on the brain.

i do believe that you do know what i will suggest as his second option?|||Originally posted by Ruprect
live to history kinda set me off i'm working on something like this right now so i have log shipping on the brain.

i do believe that you do know what i will suggest as his second option?

I figure if I have to an option would be to use the sys tables for the information and build the create table string on the fly but was hoping there was a quicker and easier way ^_^|||Originally posted by Ruprect
live to history kinda set me off i'm working on something like this right now so i have log shipping on the brain.

i do believe that you do know what i will suggest as his second option? Hmmm, get a real job? OK, that was a joke ;)

Trx Replication? I don't know, still sounds too heavy. I'd drop the idea of having "live history" database residing on the same server. I'd worry about that one once a day, at midnight, after all backups are done.|||How about INSERT INTO (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ia-iz_5cl0.asp) if the table exists, or SELECT INTO (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sa-ses_9sfo.asp) if the target table does not exist?

-PatP|||i was gonna go with dts...
a scheduled import export but this could be handled with a vbscript looking for the existence of the table and running one of two possible sub packages depending on the table's design
the only problem is the fact that this doesnot rely on the actual table's schema. you would have to know that already.

in the case of the actual question, i think that pat has hit on the easiest solution.|||After you do the insert into, won't you still need to create the matching indexes and relationships, or are you not worried about that.|||I would second Ruprect suggestion about using Log shipping and say using your own log shipping you can achieve the task.