DTS packages migration from MSSQL 2K to MSSQL server 2005

Hello
I need to migrate all my dts packages from sql server 2000 to sql
server 2005 so I can access these packages under Legacy->DTS in
Microsft sql server 2005 Management studio.
How can I do this?
Regards,
Lena
Lena, privet
Under Legacy folder, there is Data Transformation Services folder, right
click on it then Import Package File ( I assumed you saved the dts package
as a file)
"Lena" <lenaglozman@.yahoo.com> wrote in message
news:e01c20ab-e0a9-4104-ad48-90f70fd91a5d@.47g2000hsb.googlegroups.com...
> Hello
> I need to migrate all my dts packages from sql server 2000 to sql
> server 2005 so I can access these packages under Legacy->DTS in
> Microsft sql server 2005 Management studio.
> How can I do this?
> Regards,
> Lena
|||I already did that.
Now when I try to open the package, I'm getting error:
"The package cannot be edited.
SQL Server 2000 DTS Designer Components are required to edit DTS
packages. Install the special Web download, "SQL server 2000 DTS
designer Com[ponents" to use this feature".
I can not find this download on Microsoft's site.
On Mar 6, 1:21Xam, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Lena, privet
> Under Legacy folder, there is XData Transformation Services folder, right
> click on it then Import Package File ( I assumed you saved the dts package
> as a file)
> "Lena" <lenagloz...@.yahoo.com> wrote in message
> news:e01c20ab-e0a9-4104-ad48-90f70fd91a5d@.47g2000hsb.googlegroups.com...
>
>
>
> - Show quoted text -

DTS packages migration from MSSQL 2K to MSSQL server 2005

Hello
I need to migrate all my dts packages from sql server 2000 to sql
server 2005 so I can access these packages under Legacy->DTS in
Microsft sql server 2005 Management studio.
How can I do this?
Regards,
LenaLena, privet
Under Legacy folder, there is Data Transformation Services folder, right
click on it then Import Package File ( I assumed you saved the dts package
as a file)
"Lena" <lenaglozman@.yahoo.com> wrote in message
news:e01c20ab-e0a9-4104-ad48-90f70fd91a5d@.47g2000hsb.googlegroups.com...
> Hello
> I need to migrate all my dts packages from sql server 2000 to sql
> server 2005 so I can access these packages under Legacy->DTS in
> Microsft sql server 2005 Management studio.
> How can I do this?
> Regards,
> Lena|||I already did that.
Now when I try to open the package, I'm getting error:
"The package cannot be edited.
SQL Server 2000 DTS Designer Components are required to edit DTS
packages. Install the special Web download, "SQL server 2000 DTS
designer Com[ponents" to use this feature".
I can not find this download on Microsoft's site.
On Mar 6, 1:21=A0am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Lena, privet
> Under Legacy folder, there is =A0Data Transformation Services folder, righ=t
> click on it then Import Package File ( I assumed you saved the dts package=
> as a file)
> "Lena" <lenagloz...@.yahoo.com> wrote in message
> news:e01c20ab-e0a9-4104-ad48-90f70fd91a5d@.47g2000hsb.googlegroups.com...
>
> > Hello
> > I need to migrate all my dts packages from sql server 2000 to sql
> > server 2005 so I can access these packages under Legacy->DTS in
> > Microsft sql server 2005 =A0Management studio.
> > How can I do this?
> > Regards,
> > Lena- Hide quoted text -
> - Show quoted text -

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
Johnthere is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one'
"Jéjé" wrote:

> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (
to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>
>

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
John
there is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>
|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one?
"Jéjé" wrote:

> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>
>

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
Johnthere is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one'
"Jéjé" wrote:
> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
> >I see them show up under a node called Legacy in Management Studio. What is
> >the plan for migration of DTS packages from 2000 to 2005? We have lots of
> >these that we'll need to migrate that are in use with various SQL jobs.
> >
> > Thanks,
> >
> > John
> >
>
>

DTS packages fail after server migration

Hi All
My DTS packages fail after i have migrated my sql server from a NT based
network to a windows 2003 based network and unattached the old domain, I
know that the users that was once on the server as %old domain%\user will no
longer have any rights on the sql server, But how can i change the ownership
of those DTS packages to %New Domain%\New AD User.?
some input would be great.
thanksHave you checked SQLDTS.com. I believe package ownership issues are covered
on that site.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Todd" <Todd_c_wright@.hotmail.com> wrote in message
news:uVew3tSDEHA.3348@.TK2MSFTNGP11.phx.gbl...
Hi All
My DTS packages fail after i have migrated my sql server from a NT based
network to a windows 2003 based network and unattached the old domain, I
know that the users that was once on the server as %old domain%\user will no
longer have any rights on the sql server, But how can i change the ownership
of those DTS packages to %New Domain%\New AD User.?
some input would be great.
thanks|||You can change the owner using the undocumented
sp_reassign_dtspackageowner but the package ownership
probably has nothing to do with the packages failing. You
can sometimes run into issues when someone who isn't the
owner and isn't a sysadmin attempts to modify and save
packages owned by someone else but that's about it.
You can find more info on this at the site Vyas referred you
to:
Package Ownership Issues
http://www.sqldts.com/default.aspx?212
Are these scheduled packages that are failing or do they
fail when run manually as well? What are the errors?
-Sue
On Fri, 19 Mar 2004 09:56:27 +1300, "Todd"
<Todd_c_wright@.hotmail.com> wrote:

>Hi All
>My DTS packages fail after i have migrated my sql server from a NT based
>network to a windows 2003 based network and unattached the old domain, I
>know that the users that was once on the server as %old domain%\user will n
o
>longer have any rights on the sql server, But how can i change the ownershi
p
>of those DTS packages to %New Domain%\New AD User.?
> some input would be great.
> thanks
>

DTS Package Migration Error

I've been migrating SQL 2000 DTS packages into SQL 2005 using the Migrate DTS 2000 Package wizard in Visual Studio 2005. All packages migrate fine except one which throws out the following error:

exception of type 'Microsoft.SQLServer.DTS.MigrationWizard.HelperUtility.DTSMWException was thrown

No other supporting information is given to help diagnose the problem. Has anyone else come across this error before? Looking at past threads, I've checked the DTS package for leading or trailing spaces which might cause an issue and there are none.

Thanks.

me too in the same position...|||

Hey i found the problem. if you are package is Incompleted take an example "doing the bulk insert from SQL Server Conn to Excel sheet but with out Defining which Table and column" package will thro error. Just check you package.

DTS Package Migration Error

I've been migrating SQL 2000 DTS packages into SQL 2005 using the Migrate DTS 2000 Package wizard in Visual Studio 2005. All packages migrate fine except one which throws out the following error:

exception of type 'Microsoft.SQLServer.DTS.MigrationWizard.HelperUtility.DTSMWException was thrown

No other supporting information is given to help diagnose the problem. Has anyone else come across this error before? Looking at past threads, I've checked the DTS package for leading or trailing spaces which might cause an issue and there are none.

Thanks.

me too in the same position...|||

Hey i found the problem. if you are package is Incompleted take an example "doing the bulk insert from SQL Server Conn to Excel sheet but with out Defining which Table and column" package will thro error. Just check you package.

DTS migration wizard, where does it put migrated version?

From SQL Server Management Studio I right click on Management/Legacy/DTS and select Migration Wizard and enter a SQL Server Source and Destination. A list of DTS packages from the source server is displayed and I select one of the DTS packages and give the destination a unique name. The wizard runs and says it's successful. I can't find the new SSIS version of the DTS package with the new name that I've given it, however. Where does it put the new migrated copy of the DTS package.

Thanks,

John

In Sql Management Studio, under the Object Explorer window in the Connect drop down choose Integration Services, and it will show you all stored packages on that instance.|||Thanks, this helps. Now I'd like to find out how to edit the migrated version. How to I get to it from BI Dev Studio?|||

All of the stored packages will usually be in ~\Program Files\Microsoft SQL Server\90\DTS\Packages

DTS migration wizard, how to edit MSDB packages?

Thanks to Sean for helping me find the migrated packages. I'd like to edit one of the connections on a bunch of packages that I migrated. I see in the Run Package there are configuration options that would allow me to mofify the connection string at that point in time, but I would like to modify the package so it has the new connection string. I was thinking I could access it in BI Dev studio, but I'm not sure how to get to it. I suppose I could migrate to a file and then edit the file prior to importing, but I'm curious if there's a way I can modify the packages that show up under Integration Services/Stored Packages/MSDB.

Thanks,

John

You'll have to export it to a file, and then edit it with BIDS. Afterwards import it back in. :)

DTS Migration Wizard question

Hi,
I've upgraded from 2000 to 2005, 2005 on a new server too.
I have moved a DTS package from the 2000 box to 2005 box & have performed th
DTS Migration Wizard.
Now I want to fiddle with the design of the package in Business Intelligence
Design Studio. Where the heck is it (the migrated package)? How do I open
the package in this wierd GUI?
cheersTry to connect to Integration Services and expand "Storage Packages", just t
o
see where you saved your package.
To edit the package, run Business Intelligence Development Studio, create a
new Project (using Integration Services Template) and in the new Solution ad
d
an existing package; following the dialog boxes you should navigate to the
path where your package is stored.
Gilberto Zampatti
"dc" wrote:

> Hi,
> I've upgraded from 2000 to 2005, 2005 on a new server too.
> I have moved a DTS package from the 2000 box to 2005 box & have performed
th
> DTS Migration Wizard.
> Now I want to fiddle with the design of the package in Business Intelligen
ce
> Design Studio. Where the heck is it (the migrated package)? How do I ope
n
> the package in this wierd GUI?
> cheers
>
>

DTS Migration Wizard question

Hi,
I've upgraded from 2000 to 2005, 2005 on a new server too.
I have moved a DTS package from the 2000 box to 2005 box & have performed th
DTS Migration Wizard.
Now I want to fiddle with the design of the package in Business Intelligence
Design Studio. Where the heck is it (the migrated package)? How do I open
the package in this wierd GUI?
cheersTry to connect to Integration Services and expand "Storage Packages", just to
see where you saved your package.
To edit the package, run Business Intelligence Development Studio, create a
new Project (using Integration Services Template) and in the new Solution add
an existing package; following the dialog boxes you should navigate to the
path where your package is stored.
Gilberto Zampatti
"dc" wrote:
> Hi,
> I've upgraded from 2000 to 2005, 2005 on a new server too.
> I have moved a DTS package from the 2000 box to 2005 box & have performed th
> DTS Migration Wizard.
> Now I want to fiddle with the design of the package in Business Intelligence
> Design Studio. Where the heck is it (the migrated package)? How do I open
> the package in this wierd GUI?
> cheers
>
>

DTS Migration Wizard error

I'm using SQL Server 2005 Enterprise x64 and when attempting to migrate a DTS from our SQL Server 2000 Standard x86 server I received the following error message:

DTS Migration Wizard Error

Could not load file or assembly 'Microsoft.SqlServer.Exec80PackageTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of it's dependencies. The system cannot find the file specified.

Click Abort to stop the migration of the current package.

Click Retry to retry the operation.

Click Skip to skip the migration of the current task and continue to the next task.

From the error message, it would appear something did not install or register correctly. Any idea on what is missing and how I can fix it?

Hi there,

Did you do a full SSIS install, or did you install the Migration Wizard by itself? I believe you also need choose "Legacy Components" from the setup if you choose to install the Migration Wizard without the rest of the workbench. That might be the cause of the error you're seeing.

Thanks,

~Matt

|||

I chose to install all (full) components, both server and tools, during my installation of SQL Server 2005 Evaluation Edition. I found it strange that the icon said MS Visual Studio Premier Edition -enu instead of SQL Server Business Intelligence Development Studio. I tried a repair on the MS Visual Studio Premier Edition from Add / Remove Programs but it didn't help. I then removed it using Add / Remove Programs. However, when I fire up the SQL Server 2005 Evaluation Edition setup and attempted to reinstall the tools, it said they were already installed and would not let me go any further. Is a reboot of the production server necessary for Windows 2003 Enterprise to realize I uninstalled MS Visual Studio?

Thanks for your response Matt!

|||

The Visual Studio icon will only be labeled "SQL Server Business Intelligence Development Studio" under the SQL Server folder in the start menu. Your old visual studio icons won't change (they all point to the same thing).

You shouldn't have to reboot after installing SQL Server, but if you've done a repair, I'm not sure what state that puts you in. You might want to uninstall it all and start over again.

The Migration Wizard will be looking for the Microsoft.SqlServer.Exec80PackageTask assembly in the GAC - you might want to make sure it's there. This task gets installed when you select "Legacy Components" or the workbench, so doing a full install should give you all the bits you need.

|||That is the strange part. MS Visual Studio 2005 was not previously installed on this machine; it came across when I chose to install every component of the SQL Server 2005 Eval Edition installation. And the icon in the SQL Server folder didn't say BIDS, instead it was labeled MS Visual Studio 2005. Either way, I have now uninstalled MS Visual Studio 2005 and it looks like I will need to reboot my server before it recognizes the change as it will not allow me to re-install them at this point.|||I ended up uninstalling and reinstalling all of SQL Server 2005 and components. Then to address the missing Business Intellligence projects; I finallly found the answer, In MS Visual Studio (BIDS) click on Tools - Import and Export Settings - Import Selected Environment Settings - Yes, Save my current settings and then highlight "Business Intelligence Settings" and click on finish. This will add the Business Intelligence projects to BIDS.

DTS Migration Wizard error

I'm using SQL Server 2005 Enterprise x64 and when attempting to migrate a DTS from our SQL Server 2000 Standard x86 server I received the following error message:

DTS Migration Wizard Error

Could not load file or assembly 'Microsoft.SqlServer.Exec80PackageTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of it's dependencies. The system cannot find the file specified.

Click Abort to stop the migration of the current package.

Click Retry to retry the operation.

Click Skip to skip the migration of the current task and continue to the next task.

From the error message, it would appear something did not install or register correctly. Any idea on what is missing and how I can fix it?

Hi there,

Did you do a full SSIS install, or did you install the Migration Wizard by itself? I believe you also need choose "Legacy Components" from the setup if you choose to install the Migration Wizard without the rest of the workbench. That might be the cause of the error you're seeing.

Thanks,

~Matt

|||

I chose to install all (full) components, both server and tools, during my installation of SQL Server 2005 Evaluation Edition. I found it strange that the icon said MS Visual Studio Premier Edition -enu instead of SQL Server Business Intelligence Development Studio. I tried a repair on the MS Visual Studio Premier Edition from Add / Remove Programs but it didn't help. I then removed it using Add / Remove Programs. However, when I fire up the SQL Server 2005 Evaluation Edition setup and attempted to reinstall the tools, it said they were already installed and would not let me go any further. Is a reboot of the production server necessary for Windows 2003 Enterprise to realize I uninstalled MS Visual Studio?

Thanks for your response Matt!

|||

The Visual Studio icon will only be labeled "SQL Server Business Intelligence Development Studio" under the SQL Server folder in the start menu. Your old visual studio icons won't change (they all point to the same thing).

You shouldn't have to reboot after installing SQL Server, but if you've done a repair, I'm not sure what state that puts you in. You might want to uninstall it all and start over again.

The Migration Wizard will be looking for the Microsoft.SqlServer.Exec80PackageTask assembly in the GAC - you might want to make sure it's there. This task gets installed when you select "Legacy Components" or the workbench, so doing a full install should give you all the bits you need.

|||That is the strange part. MS Visual Studio 2005 was not previously installed on this machine; it came across when I chose to install every component of the SQL Server 2005 Eval Edition installation. And the icon in the SQL Server folder didn't say BIDS, instead it was labeled MS Visual Studio 2005. Either way, I have now uninstalled MS Visual Studio 2005 and it looks like I will need to reboot my server before it recognizes the change as it will not allow me to re-install them at this point.|||I ended up uninstalling and reinstalling all of SQL Server 2005 and components. Then to address the missing Business Intellligence projects; I finallly found the answer, In MS Visual Studio (BIDS) click on Tools - Import and Export Settings - Import Selected Environment Settings - Yes, Save my current settings and then highlight "Business Intelligence Settings" and click on finish. This will add the Business Intelligence projects to BIDS.

DTS Migration wizard - solved

i am trying to use the DTS migration wizard in sql server 2005 to migrate some of the DTS packages that i have on sql server 2000.

After entering the source and destination server i get the following error:

Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index (mscorlib)

Does anyone know the reson behind this?

Thanks for any help.

I've just installed Server 2005 and am getting the same message. The earlier threads refer to special characters and leading or trailing spaces. I've tried the wizard on a few packages that have nothing but letters in the name, and I get the above message. I tried repairing .NET 2.0 as well (didn't work).

What else should I/we try?

Thanks,

K

|||

Found a forum where a user clarified that NONE of the DTS packages can have a leading/trailing space. Well, one out of a hundred or so packages had a space; after I fixed that one, the wizard worked.

Find the spaces (thanks to Joseph Sack's SQL Server blog):

SELECT DISTINCT name
FROM msdb.dbo.sysdtspackages
WHERE name LIKE '% '

and I'd suggest: or name LIKE ' %'

|||

Thanks a lot.

I had one package that had a space. After i deleted the space i was able to get a little further. but when i hit finish, All the packages display "Stopped" and none gets transferred.

Thanks

DTS Migration wizard - same here

i am trying to use the DTS migration wizard in sql server 2005 to migrate some of the DTS packages that i have on sql server 2000.

After entering the source and destination server i get the following error:

Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index (mscorlib)

Does anyone know the reson behind this?

Thanks for any help.

I've just installed Server 2005 and am getting the same message. The earlier threads refer to special characters and leading or trailing spaces. I've tried the wizard on a few packages that have nothing but letters in the name, and I get the above message. I tried repairing .NET 2.0 as well (didn't work).

What else should I/we try?

Thanks,

K

|||

Found a forum where a user clarified that NONE of the DTS packages can have a leading/trailing space. Well, one out of a hundred or so packages had a space; after I fixed that one, the wizard worked.

Find the spaces (thanks to Joseph Sack's SQL Server blog):

SELECT DISTINCT name
FROM msdb.dbo.sysdtspackages
WHERE name LIKE '% '

and I'd suggest: or name LIKE ' %'

|||

Thanks a lot.

I had one package that had a space. After i deleted the space i was able to get a little further. but when i hit finish, All the packages display "Stopped" and none gets transferred.

Thanks

DTS Migration to SSIS

Good Day,

I am currently in the process of migrating my DTS packages to SSISone at a timeand have come accross the following error during the excecution of a "Copy SQL Server Objects Task". The exact error is:

[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Version80 database compatibility level is not supported.".

What I am doing with this particular task is to copy a table(s) from another SQL Server, to the current SQL Server. The original location is a SQL2000 DB table. In the near future the source server for this table will be a SQL 2005 server but not until the current migration has been completed.

I have looked at all of the properties, but can not find anything relating to the db compatibilty level. Is there an easier way? Or a setting that I can change to accomplish what I am trying?

Thanks for any help/suggestions.

I have the same error . I'm copying from SQL 2005 to SQL 2005, and selecting all tables. Also having it copy all indexes, triggers, etc. Sometimes I can actually get it to execute successfully, however; there are no tables that have been copied when this happens. I'm betting this is another bug.

Really need this problem resolved since there already is a bug that have been recently report using the Transfer Database Object. Especially if we need to move a SQL 2005 database back to 2000, which my the situation in a case for me the other day. The only way was to export all the tables and then go back into the 2000 db and re-create the indexes, and relationships - not good.

We need the SSIS tools working correctly - DBA's rely on them!.

Hoping for quick resolutions.

Update: There is a solution. Check the Properties\Options of the database and look at the compatibility level. Most likely it is set to 8.0 as was mine. Change to 9.0 and it should now run. - Unfortunately when I ran mine, it led me to believe that everthing ran fine, but when I looked at the database, no user tables, etc. were there.

|||Try changing the provider to Microsoft OLE DB Provider for SQL server. The default provider probably does not work for SQL server 2000.

DTS Migration to SSIS

Good Day,

I am currently in the process of migrating my DTS packages to SSISone at a timeand have come accross the following error during the excecution of a "Copy SQL Server Objects Task". The exact error is:

[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Version80 database compatibility level is not supported.".

What I am doing with this particular task is to copy a table(s) from another SQL Server, to the current SQL Server. The original location is a SQL2000 DB table. In the near future the source server for this table will be a SQL 2005 server but not until the current migration has been completed.

I have looked at all of the properties, but can not find anything relating to the db compatibilty level. Is there an easier way? Or a setting that I can change to accomplish what I am trying?

Thanks for any help/suggestions.

I have the same error . I'm copying from SQL 2005 to SQL 2005, and selecting all tables. Also having it copy all indexes, triggers, etc. Sometimes I can actually get it to execute successfully, however; there are no tables that have been copied when this happens. I'm betting this is another bug.

Really need this problem resolved since there already is a bug that have been recently report using the Transfer Database Object. Especially if we need to move a SQL 2005 database back to 2000, which my the situation in a case for me the other day. The only way was to export all the tables and then go back into the 2000 db and re-create the indexes, and relationships - not good.

We need the SSIS tools working correctly - DBA's rely on them!.

Hoping for quick resolutions.

Update: There is a solution. Check the Properties\Options of the database and look at the compatibility level. Most likely it is set to 8.0 as was mine. Change to 9.0 and it should now run. - Unfortunately when I ran mine, it led me to believe that everthing ran fine, but when I looked at the database, no user tables, etc. were there.

|||Try changing the provider to Microsoft OLE DB Provider for SQL server. The default provider probably does not work for SQL server 2000.

DTS Migration to SSIS

Good Day,

I am currently in the process of migrating my DTS packages to SSISone at a timeand have come accross the following error during the excecution of a "Copy SQL Server Objects Task". The exact error is:

[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Version80 database compatibility level is not supported.".

What I am doing with this particular task is to copy a table(s) from another SQL Server, to the current SQL Server. The original location is a SQL2000 DB table. In the near future the source server for this table will be a SQL 2005 server but not until the current migration has been completed.

I have looked at all of the properties, but can not find anything relating to the db compatibilty level. Is there an easier way? Or a setting that I can change to accomplish what I am trying?

Thanks for any help/suggestions.

I have the same error . I'm copying from SQL 2005 to SQL 2005, and selecting all tables. Also having it copy all indexes, triggers, etc. Sometimes I can actually get it to execute successfully, however; there are no tables that have been copied when this happens. I'm betting this is another bug.

Really need this problem resolved since there already is a bug that have been recently report using the Transfer Database Object. Especially if we need to move a SQL 2005 database back to 2000, which my the situation in a case for me the other day. The only way was to export all the tables and then go back into the 2000 db and re-create the indexes, and relationships - not good.

We need the SSIS tools working correctly - DBA's rely on them!.

Hoping for quick resolutions.

Update: There is a solution. Check the Properties\Options of the database and look at the compatibility level. Most likely it is set to 8.0 as was mine. Change to 9.0 and it should now run. - Unfortunately when I ran mine, it led me to believe that everthing ran fine, but when I looked at the database, no user tables, etc. were there.

|||Try changing the provider to Microsoft OLE DB Provider for SQL server. The default provider probably does not work for SQL server 2000.

DTS migration to Oracle

Hi!
Do you know any tool ou method to help the migration of an entire DW
repository in SQL Server 2000 to Oracle? And I mean the Dtata Transformation
Services too... I think it is veru difficult to migrate DTS to DML in
Oracle, but who knows there is some tool that transforms DTSs into PL/SQL (I
doubt it, but...).
thanks.
FPG
Hi Filipe,
you are out of luck as far as I am aware....there are few tools to
convert etl from one thing to another....I always recommend to my
clients to use ETL tools that can move from one database to another
with zero changes...and I liked the idea so much I wrote one for
myself...LOL!
At least if you can move your entire ETL/BI subsystem from one OS/RDBMS
platform to another you can push the vendor for a better deal on
maintenance...if you are lucky...
Best Regards
Peter Nolan
www.peternolan.com