Jim Lawrence
accessd at shaw.ca
Thu Jul 13 15:52:29 CDT 2006
Hi Jim: Thank you very much. That is a definitely a thorough explanation for a definitely not obvious solution. Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Moss Sent: Thursday, July 13, 2006 9:12 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Exporting from SQL 2000 to SQL 2003 Jim. >From BOL: The Execute DTS 2000 Package task runs packages that were developed by using the SQL Server 2000 tools. By using this task, you can include SQL Server 2000 DTS packages in SQL Server 2005 data transformation solutions. A package can include both Execute Package tasks and Execute DTS 2000 Package tasks, because each type of task uses a different version of the run-time engine. The Execute DTS 2000 Package task runs SQL Server 2000 packages, but otherwise its features are similar to those of the Execute Package task. You can use the Execute DTS 2000 Package task for the following purposes: Breaking down complex package workflow. This task lets you break down workflow into multiple packages, which are easier to read and maintain. For example, if you are loading data into a star schema, you can build a separate package to populate each dimension and the fact table. Reusing parts of packages. Other packages can reuse parts of a package workflow. For example, you can build a data extraction module that can be called from different packages. Each package that calls the extraction module can perform different data scrubbing, filtering, or aggregation operations. Grouping work units. Units of work can be encapsulated into separate packages and joined as transactional components to the workflow of a parent package. For example, the parent package runs the accessory packages, and based on the success or failure of the accessory packages, the parent package either commits or rolls back the transaction. Controlling package security. Package authors require access to only a part of a multipackage solution. By separating a package into multiple packages, you can provide a higher level of security, because you can grant an author access only to relevant packages. Note: The DTS 2000 run-time engine must be installed on the computer to run DTS 2000 packages. For more information, see Installing SQL Server Integration Services. A package that executes other packages, such as the Execute DTS 2000 Package task, is typically referred to as the parent package, and the packages that a parent workflow runs are called child packages. Jim > Hi All: > > Here is a simple question? I have recently exported a database from a SQL > 2000 server to a SQL 2003 server and everything went through with minimal > problems with exception to DTS packages. They just did not import. > > I was wondering if DTS packages have to be re-created, there is a simple > solution or there is some trick to importing them. > > MTIA > Jim > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com