History of a SQL Job Deletion

Does anyone know if there is a record kept of a deleted SQL Agent Job? I
need to track down why a job is going away but I haven't been able to
figure out how to do it.
Thanks!
--
Posted via http://dbforums.comThe SQL Jobs are all stored within the msdb database. If you have been
backing up msdb you should be able to get the job back
--
HTH
Ryan Waight, MCDBA, MCSE
"MrSanity" <member40366@.dbforums.com> wrote in message
news:3390116.1063975524@.dbforums.com...
> Does anyone know if there is a record kept of a deleted SQL Agent Job? I
> need to track down why a job is going away but I haven't been able to
> figure out how to do it.
>
> Thanks!
>
> --
> Posted via http://dbforums.com|||Are you saying that some of your jobs just Disappear ?
If yes then have a look at the job properties. On the Notifications
tab there is a "Automatically delete this job - When it
fails/Succeeds/completes"
Do you have that checked ?
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org|||There is no record kept of deleted jobs in SQL Server. If your msdb database
uses either the full or bulk-logged recovery model and you have backups of
the transaction logs, you can use LogExplorer from www.lumigent.com to do
research.
If a job disappears on a regular basis, make sure that you don't have the
'automatically delete job' property set. You can find it on the
Notifications tab of the job properties in Enterprise Manager.
--
Jacco Schalkwijk MCDBA, MCSD, MCSE
Database Administrator
Eurostop Ltd.
"MrSanity" <member40366@.dbforums.com> wrote in message
news:3390116.1063975524@.dbforums.com...
> Does anyone know if there is a record kept of a deleted SQL Agent Job? I
> need to track down why a job is going away but I haven't been able to
> figure out how to do it.
>
> Thanks!
>
> --
> Posted via http://dbforums.comsql

History Logging

How does the historyverboselevel and transactionsperhistory correlate ? If i
change the historyverbose level to 3 for the distribution agent profile, do
i also need to increase the transactionsperhistory ? I dont follow what the
transactionperhistory is.
Also the agents can log to output file based upon
http://support.microsoft.com/default...;en-us;312292. Is this
similar to changing the historyverboselevel to 3 or are the outputs totally
different between what is captured in the output file and setting it to 3
I am trying to gather some info about certain latency issues that we are
seeing between the time the record is inserted on the publisher and the time
it shows up on the subscriber and wanted to capture some logs.
Is this the right way ?
HistoryVerboseLevel refers to how much history is logged, 0 means none,
1 means only the current history or status is logged, overwriting any
past history, 2 is verbose, 3 is even more verbose and is used for
debugging.
TransactionsPerHistory controls how often the history is logged. So if
you have a value of 100 for TransactionsPerHistory you will not get any
history logged until your distribution agent stops or your distribution
agent distributes 100 transactions.
Hassan wrote:
> How does the historyverboselevel and transactionsperhistory correlate ? If i
> change the historyverbose level to 3 for the distribution agent profile, do
> i also need to increase the transactionsperhistory ? I dont follow what the
> transactionperhistory is.
> Also the agents can log to output file based upon
> http://support.microsoft.com/default...;en-us;312292. Is this
> similar to changing the historyverboselevel to 3 or are the outputs totally
> different between what is captured in the output file and setting it to 3
> I am trying to gather some info about certain latency issues that we are
> seeing between the time the record is inserted on the publisher and the time
> it shows up on the subscriber and wanted to capture some logs.
> Is this the right way ?
>
>
|||What about the output file ? Is that a different kinda logging of history ?
Do i need to set the verbose to 2 or 3 and also specify the output file ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:u%23hHynKPFHA.3388@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> HistoryVerboseLevel refers to how much history is logged, 0 means none,
> 1 means only the current history or status is logged, overwriting any
> past history, 2 is verbose, 3 is even more verbose and is used for
> debugging.
> TransactionsPerHistory controls how often the history is logged. So if
> you have a value of 100 for TransactionsPerHistory you will not get any
> history logged until your distribution agent stops or your distribution
> agent distributes 100 transactions.
> Hassan wrote:
If i[vbcol=seagreen]
do[vbcol=seagreen]
the[vbcol=seagreen]
totally[vbcol=seagreen]
3[vbcol=seagreen]
time[vbcol=seagreen]
|||the history is the history of your run, ie 10 transactions, and 20
commands. The output is far more detail. You can see the history in your
agent details. Output can only be read when it is piped to an output
file. You need to set OutputVerboseLevel to read these output statements.
Hassan wrote:
> What about the output file ? Is that a different kinda logging of history ?
> Do i need to set the verbose to 2 or 3 and also specify the output file ?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:u%23hHynKPFHA.3388@.TK2MSFTNGP10.phx.gbl...
>
> If i
>
> do
>
> the
>
> totally
>
> 3
>
> time
>
>

high latency with Dist agent

Any ideas on how I can decrease this?
--Thanks,
Kristy
you might also want to look at replicating the execution of stored
procedures.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kristy" <pleasereplyby@.posting.com> wrote in message
news:ug1ntMqHFHA.2740@.TK2MSFTNGP12.phx.gbl...
> Any ideas on how I can decrease this?
> --Thanks,
> Kristy
>
|||Can you give me an example?
--K
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23hFAwk%23HFHA.2456@.TK2MSFTNGP09.phx.gbl...
> you might also want to look at replicating the execution of stored
> procedures.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Kristy" <pleasereplyby@.posting.com> wrote in message
> news:ug1ntMqHFHA.2740@.TK2MSFTNGP12.phx.gbl...
>
sql