RE: Anyone know how to transfer SQL 2000 jobs to SQL 2005 ?

RE: Anyone know how to transfer SQL 2000 jobs to SQL 2005 ?

 

  

Michael,
Use the activeX script run as a DTS
You have change server name and path to script
Run it on 05 probably this should work

'**********************************************************************
' Visual Basic ActiveX Script
'***********************************************************************
*

Function Main()
Const srtSQLServer="ServerName here.............."
Dim conServer
Dim fso
Dim iFile
Dim oJB
Dim strJob
Dim strFilename
Const ioModeAppend = 8
Dim dtDateOfTransfer
Dim dtDay, dtMonth, dtYear, dtTime




dtDateOfTransfer = now()
dtDay = Day(dtDateOfTransfer)
dtMonth = Month(dtDateOfTransfer)
dtYear = Year(dtDateOfTransfer)

dtDateOfTransfer = dtYear & "_" & dtMonth & "_" & dtDay

strFilename="Script Location......................." &
dtDateOfTransfer & ".txt"


Set conServer = CreateObject("SQLDMO.SQLServer")
conServer.LoginSecure = True

conServer.Connect (Local)

'strJob = "/*Scripts for all JOBS located on SQL Server: " &
srtSQLServer & " as of " & NOW() & "*/" & vbCrLf & vbCrLf

strJob = strJob & "/*" & vbCrLf
strJob = strJob & "Description: : Scripts for all SQL Server
JOBS" & vbCrLf
strJob = strJob & "SQL Server : " & srtSQLServer & vbCrLf
strJob = strJob & "Script Date : " & NOW() & vbCrLf
strJob = strJob & "*/" & vbCrLf & vbCrLf & vbCrLf

For Each oJB In conServer.JobServer.Jobs
strJob = strJob & "/*SCRIPTING JOB: " & oJB.Name & "*/"
& vbCrLf
strJob = strJob & oJB.Script() & vbCrLf
Next

Set conServer = Nothing

Set fso = CreateObject("Scripting.FileSystemObject")
Set iFile = fso.CreateTextFile(strFilename, True)

iFile.Write (strJob)
iFile.Close

Set fso = Nothing

Main = DTSTaskExecResult_Success

End Function





Uday



-----Original Message-----
From: Michael_Beadles
[mailto:mssqldba-ezmlmshield-x87278384.[Email address protected]
Sent: Friday, June 30, 2006 3:37 PM
To: LazyDBA Discussion
Subject: Anyone know how to transfer SQL 2000 jobs to SQL 2005 ?


On a 2005 Server not set up by me ... trying to pull in jobs from a 2000
box so I can later put certain jobs back onto it when it is upgraded.

(Upgrade will be to backup everything, detach 2000 user db's, blow away
the
2000 install completely, install 2005, attach the user db's)

I am at a stand still:

In ISSI:

Source and Dest. connections defined ok - they test ok.

In Control Flow, have the Transfer Jobs Task defined. Have set all
properties so allow the jobs to transfer.

Job List Property says "(Collection)" and trying to inspect it by
clicking
on it brings up a blank Collection Members List.

Trying to add a job gives me the message "Constructor on Type
System.String
not found"



======================================================================
Confidentiality Notice: The information contained in and transmitted
with this communication is strictly confidential, is intended only for
the use of the intended recipient, and is the property of Countrywide
Financial Corporation or its affiliates and subsidiaries. If you are
not the intended recipient, you are hereby notified that any use of the
information contained in or transmitted with the communication or
dissemination, distribution, or copying of this communication is
strictly prohibited by law. If you have received this communication in
error, please immediately return this communication to the sender and
delete the original message and any copy of it in your possession.
======================================================================



---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html

Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged.
If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of all or any portion of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system.

MS Sql Server LazyDBA home page