Re: Migrating DTS Packages on SQL 2000 to SSIS on 2005

Hi Karen,

You can install a named instance of SQL Server 2005 on the same box as SQL
Server 2000, if SQL Server 2000 is already the default instance. For now, you
can develop your packages and perform your migrations on that system.
However, when you come to deploying the packages, deploy to a different
server as SSIS does not support named instances.

Hope this helps.

Charles Kangai, MCT, MCDBA
Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
Services" http://www.learningtree.com/courses/134.htm
Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
http://www.learningtree.com/courses/523.htm
email alias: charles
email domain: kangai.demon.co.uk


"KarenM" wrote:

Charles,

Many thanks for your advice. Can I install the SQL 2005 instance on the
same server running SQL 2000.

Thanks
Karen
Charles Kangai wrote:
Karen,

Use the DTS Migration wizard. You can start the wizard either from SQL
Server Management Studio (SSMS) or from SQL Server Business Intelligence
Development Studio (BIDS). If you start it from SSMS, expand the Management
folder, then expand Legacy. Right-click on Data Transformation Services and
choose Migration Wizard. If you start it in BIDS, you need to first create a
project of Integration Services type. Right-click on the SSIS Packages folder
in Solution Explorer and choose Migrate DTS 2000 Package.

Migration may not be perfect as some DTS features are not supported in SSIS.
With some packages, you are better off creating them from scratch in SSIS.

Hope this helps.

Charles Kangai, MCT, MCDBA
Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
Services" http://www.learningtree.com/courses/134.htm
Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
http://www.learningtree.com/courses/523.htm
email alias: charles
email domain: kangai.demon.co.uk




"KarenM" wrote:

I have some DTS packages that load a flat file to the SQL 2000 database
and then to a AS 2000 cube. I want to migrate this to SSIS on SQL 2005
and AS 2005 kindly explain the procedure for the migration.

Thanks
Karen




.

Relevant Pages

  • Re: SSIS as part of scheduled job fails
    ... SSIS as part of scheduled job fails ... An SSIS package does not run when you call the SSIS package from a SQL ... Microsoft SQL Server Management Studio ...
    (microsoft.public.sqlserver.dts)
  • Re: SSIS as part of scheduled job fails
    ... any more detailed instruction on how to configure the logging for the SSIS ... SSIS as part of scheduled job fails ... An SSIS package does not run when you call the SSIS package from a SQL ... Microsoft SQL Server Management Studio ...
    (microsoft.public.sqlserver.dts)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... I understand that you can connect to SQL 2000 named instance on the local ... to an instance of SQL Server 2000 or of SQL Server 7.0 that was installed ... Select TCPIP, and click Properties, and set the port of the instance to ...
    (microsoft.public.sqlserver.setup)