Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Services / Analysis (Data Mining) / July 2008

Tip: Looking for answers? Try searching our database.

DTS and Jobs Import/Export SQL2000

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ago - 23 Jul 2008 18:39 GMT
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
Russell Fields - 28 Jul 2008 15:37 GMT
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

> Hi,
>
[quoted text clipped - 17 lines]
>
> ago
Russell Fields - 28 Jul 2008 15:46 GMT
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

> ago,
>
[quoted text clipped - 44 lines]
>>
>> ago
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.