December 29, 2008 at 7:25 pm
Hello everybody,
i was doing a migration..we migrated the dbs and packages...but not the jobs...today all of a sudden all the jobs are also...i asked if anyone copied the job..they said no one did..then i wasnt able to see sql server logs..i had to restart the machine..then i cld see the logs...hte jobs were migrated at 12:24 pm..when i check in the logs..i do not see any entry for that time...is there anyway anyone could suggest me how this happened or if there is a way i can find out who copied the jobs from source server...we all are confused..hope someone here helps me...thanks,,
December 29, 2008 at 8:27 pm
How did you do your migration? Someone had to have done something whether they realize it or not since Jobs don't just mysteriously decide to migrate themselves. Unfortunately you can't tell who moved them, just when it was done in msdb.dbo.sysjobs. You can try looking at the job owners, but if they moved the owner as a part of job which is highly likely, then that won't help either.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
December 29, 2008 at 8:36 pm
hello thanks..i did check in the jobs owner..it is the same as the source...and all the jobs are transfered..how could someone unknowingly transfer all the jobs???..thanks again for ur answer...
December 29, 2008 at 8:38 pm
How did you do the migration?
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
December 29, 2008 at 8:45 pm
for dbs backup & restore..and for DTS packages..i think the other guy did use BI studio...
December 29, 2008 at 9:22 pm
Check the package that they used to move the Packages between instances, that would be the most likely suspect. If it was a transfer objects task in BIDS then it is possible that they left Agent Jobs selected as a object to move. Did you restore MSDB as a part of the databases? I wouldn't think so since that would have preserved the old job modification dates. I am not trying to be funny with my answers, but someone did something to cause the jobs to be moved/generated on the new server. If it is SQL 2005, try querying the Default Trace and see if it has the information for who did it.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
December 30, 2008 at 12:08 am
Hi,
Seems like the msdb database was also migrated and hence all the system tables were overwritten. In this case the sysjobs table was overwritten by the source server and hence you are able to see all the jobs. Hence the "originated_server_id" is showing to be the current one.
In SQL Server 2000, if by any chance the msdb database got restored from some other server, then we can find out that from the "Originating_server" column from sysjobs, which then needs to be manually cahnged to the current server, However this is not applicable to 2005.
All I can say is that the msdb database must have also got migrated resulting in the sysjobs table getting modified.
-Rajini
December 30, 2008 at 1:25 pm
thanks everyone for all your answers..
Rajni..i see the jobs...i do not think msdb is migrated bcoz in the porp it still shows the old date.
Jonathan..the packages were migrated long back..we just saw these jobs yesterday...im sure there should be some reason...i think im missign something.
thanks again for spending time and replying me..any ideas keep posting..thz..
December 30, 2008 at 11:17 pm
iqtedar (12/30/2008)
thanks everyone for all your answers..Rajni..i see the jobs...i do not think msdb is migrated bcoz in the porp it still shows the old date.
Jonathan..the packages were migrated long back..we just saw these jobs yesterday...im sure there should be some reason...i think im missign something.
thanks again for spending time and replying me..any ideas keep posting..thz..
Ye, the date old u seen, but when the job ismigrated then it will aslo shown old data wheen it was created in orignal server.
December 31, 2008 at 12:31 pm
i couldnt get what you are trying to say...the packages were migrated month back...i just see the jobs for the first time two days ago...the jobs were not there until two days back..thanks...
December 31, 2008 at 7:39 pm
just an update...as i was mentioning before that all the jobs were copied from the source onto new server..but today i found that some jobs were not copied...i realize that all the jobs except couple had DTS packages ...so i am assuming the jobs were copied along with the packages..is my assumption true..i tried looking at the trace but cldnt get any helpful information..if someone can shed light on it that wodul also be nice..thnx again..happy new year..
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply