Migration of SSIS package to SQL Server 2000
-
Hi ,
I need to schedule a SSIS package developed in SQL Server 2005, in sql server 2000. Is there any way that i can deploy SSIS package into Sql 2000
-
Installing an instance of SSIS 2005 on the server where you are running SQL 2000. That means you need a license.
-
SQL 2000 does not run SSIS. SSIS is for 2005 & 2008.
Could you be more clear about what you want to do ?
-
SQL 2000 has DTS. Which provide some functionality. So what do you want to do?
-
k in simple words, what i required is :-
i need to deploy SSIS package of 2005 in sql server 2000. As far as i know, MS don't provide backward compatibility. Does anybody have any idea
-
Could you please be more specific. What do you want the package to do?
-
This was removed by the editor as SPAM
-
A few alternatives:
1. Rebuild SSIS jobs as DTS jobs.
2. Add the SQL Server 2000 server as a linked server on a SQL Server 2005 or later server. Then amend the SSIS packages on this server to point to the linked server. So SSIS is still being executed by the later version but saving data etc on the 2000 machine.
3. Look at the SSIS jobs to see how many could be converted to stored procedures. Then set up jobs to simply execute the procedures. - This would be my preferred option. This way the jobs are totally portable when you need to upgrade, and often procedures are much faster than SSIS or DTS.
Options 1 and 3 give you a chance for some spring cleaning.
By the way why are you using SQL Server 2000 rather than later version?
-
Never mind new installations as long as you have a sql 2005 instance somewhere. The package can sit on any 2005 server, the sql agent job on any 2005 server and the database and files on any 2000 server. And all run fine.
I have a sql agent job on a sql 2005 cluster in domain D running a ssis package stored in msdb on sql server 2005 in domain A and updating 3 sql 2000 servers and 1 sql 2005 server in domain A and 2 in domain D.
Develop your package anywhere, but in the package, set datasources to refer to your sql2000 server. If you need to refer to other files on your sql2000 server use the \\servername\share\filename format.
If you developed in Visual Studio on your local machine do a File, save copy of ... as to deploy your package to the chosen sql 2005 server and set "Rely on server ..." for security.
Then on your 2005 server set up a sql agent job to execute the package at the required time.
Ensure your job is run by a suitably privileged account to access everything across the servers.
-
That is why I was asking him what he wanted to do, but still no reply.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply