DTS and Jobs Import/Export SQL2000

Discussion:

(too old to reply)

ago via SQLMonster.com

2008-07-23 17:39:57 UTC

Hi,

I imported DTS and Jobs (SQL2000) from SQLServer1 to SQLServer2 and all the
jobs failed. I tested with dtsEmployee and it failed, then I created a job on
SQLServer2 itself for dtsEmployee and it worked. So it could be the import of
jobs. I opened the one that failed (I imported from SQLServer1) and compared
the DTS command and they are different. After copying the command DTS /...
from the jobs I created in SQLServer2 into the one I imported then it worked.
My biggest dilemma right now is I have 300+ jobs running from SQLServer1 that
I imported into SQLServer2. Is there a way to export/import jobs from one
server to another and avoiding this issues, may be I am doing it wrong...?

Any help is appreciated.

ago

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-data-mining/200807/1

Russell Fields

2008-07-28 14:37:11 UTC

Permalink

ago,

You did not mention how you imported the jobs. Did you script them out of
one server and into the new server? Did you copy the rows directly from
sysjobs, sysjobsteps, etc? Did you restore a copy of msdb on the new
server?

When the jobs fail, what errors do they report?

One thing to check is whether the originating_server column in sysjobs
matches the name of your current server.

SELECT name, originating_server, @@SERVERNAME from msdb.dbo.sysjobs
WHERE originating_server <> @@SERVERNAME

If your jobs are still referring to the original server, then you will need
to update the originating_server column in your new msdb. You can do it
like this:

1. Stop SQL Server Agent
2. UPDATE msdb.dbo.sysjobs SET originating_server = @@SERVERNAME
3. Start SQL Server Agent

RLF

Post by ago via SQLMonster.com
Hi,
I imported DTS and Jobs (SQL2000) from SQLServer1 to SQLServer2 and all the
jobs failed. I tested with dtsEmployee and it failed, then I created a job on
SQLServer2 itself for dtsEmployee and it worked. So it could be the import of
jobs. I opened the one that failed (I imported from SQLServer1) and compared
the DTS command and they are different. After copying the command DTS /...
from the jobs I created in SQLServer2 into the one I imported then it worked.
My biggest dilemma right now is I have 300+ jobs running from SQLServer1 that
I imported into SQLServer2. Is there a way to export/import jobs from one
server to another and avoiding this issues, may be I am doing it wrong...?
Any help is appreciated.
ago
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-data-mining/200807/1

Russell Fields

2008-07-28 14:46:32 UTC

Permalink

Of course, it some of your jobs have target servers, then you should change
the update to:

UPDATE msdb.dbo.sysjobs SET originating_server = @@SERVERNAME
WHERE originating_server = 'Old server name'

RLF

Post by Russell Fields
ago,
You did not mention how you imported the jobs. Did you script them out of
one server and into the new server? Did you copy the rows directly from
sysjobs, sysjobsteps, etc? Did you restore a copy of msdb on the new
server?
When the jobs fail, what errors do they report?
One thing to check is whether the originating_server column in sysjobs
matches the name of your current server.
If your jobs are still referring to the original server, then you will
need to update the originating_server column in your new msdb. You can do
1. Stop SQL Server Agent
3. Start SQL Server Agent
RLF