Showing posts with label component. Show all posts
Showing posts with label component. Show all posts

Thursday, March 22, 2012

DTS Packages Unspecified Error

WE have dts packages created with ftp component in Sql 2000 dts designer. At the same time client where we are developing the package has sql 2005 components. When we move this package to sql 2000 production server - we can execute nor we can open the package it will give unspecified error.

if we recreate the package on client which does not have sql 2005 component than only it works. So for any mistake the packge once opened in sql 2000 designer also with client having sql 2005 components it does not work. Only criteria this error happens when you have ftp component used in dts package.

Did anyone has seen this problem ? Any fixes or patches available to be applied ?

Thanks for the help.

Manoj

Hi

Microsoft already know this problem but dont release the hotfix, you need to contact them.

http://support.microsoft.com/kb/890841

I have the same problem and to fixe it, I recovered an old version of DTS through the server and made the modifications.

If you found a better way please contact me.

Thanks

|||

Thanks

Looks like this hotfix should resolve the issue, I will touchbase with microsoft and will try to install the hotfix.

Let you know.

Manoj

|||

I tried after applying the hotfix - it did not work.

Manoj

|||I'm having the same problem. Did you every get this fixed?|||DTS is provided for the backward compatibility in SQL 2005, you might need to rewrite the same in SSIS to provide the functionality.sqlsql

DTS Packages Unspecified Error

WE have dts packages created with ftp component in Sql 2000 dts designer. At the same time client where we are developing the package has sql 2005 components. When we move this package to sql 2000 production server - we can execute nor we can open the package it will give unspecified error.

if we recreate the package on client which does not have sql 2005 component than only it works. So for any mistake the packge once opened in sql 2000 designer also with client having sql 2005 components it does not work. Only criteria this error happens when you have ftp component used in dts package.

Did anyone has seen this problem ? Any fixes or patches available to be applied ?

Thanks for the help.

Manoj

Hi

Microsoft already know this problem but dont release the hotfix, you need to contact them.

http://support.microsoft.com/kb/890841

I have the same problem and to fixe it, I recovered an old version of DTS through the server and made the modifications.

If you found a better way please contact me.

Thanks

|||

Thanks

Looks like this hotfix should resolve the issue, I will touchbase with microsoft and will try to install the hotfix.

Let you know.

Manoj

|||

I tried after applying the hotfix - it did not work.

Manoj

|||I'm having the same problem. Did you every get this fixed?|||DTS is provided for the backward compatibility in SQL 2005, you might need to rewrite the same in SSIS to provide the functionality.

DTS Packages Unspecified Error

WE have dts packages created with ftp component in Sql 2000 dts designer. At the same time client where we are developing the package has sql 2005 components. When we move this package to sql 2000 production server - we can execute nor we can open the package it will give unspecified error.

if we recreate the package on client which does not have sql 2005 component than only it works. So for any mistake the packge once opened in sql 2000 designer also with client having sql 2005 components it does not work. Only criteria this error happens when you have ftp component used in dts package.

Did anyone has seen this problem ? Any fixes or patches available to be applied ?

Thanks for the help.

Manoj

Hi

Microsoft already know this problem but dont release the hotfix, you need to contact them.

http://support.microsoft.com/kb/890841

I have the same problem and to fixe it, I recovered an old version of DTS through the server and made the modifications.

If you found a better way please contact me.

Thanks

|||

Thanks

Looks like this hotfix should resolve the issue, I will touchbase with microsoft and will try to install the hotfix.

Let you know.

Manoj

|||

I tried after applying the hotfix - it did not work.

Manoj

|||I'm having the same problem. Did you every get this fixed?|||DTS is provided for the backward compatibility in SQL 2005, you might need to rewrite the same in SSIS to provide the functionality.

DTS Packages in SQL 2005 - what are they now, etc

OK - so it looks like DTS Packages are "legacy". I installed the component to be able to edit and run them from SQL 2005 Management console and that seems to work fine. (I haven't acually run my packages yet, but at least I can open and edit the dang things). And I also migrated the existing ones from the networked server on which they lived (which is still running SQL 2000) to my local server (which is the one on 2005).

So assuming I want to do the new methodology - what IS the new methodology?

Where are the migrated packages? I looked at all of the links in the SQL Management Console for anything that references these newly migrate packages, and I don't see them - or anything that looks like them - anywhere.

What do I run them in - from what, how, etc? This really isn't clear at all.OK - so I think I have this figured out. You have to connect to Integration Services for a specific server. If you do that, they are then in the Stored Packages. So I'll post back if I have any problems when I actually get up the courage to try and run these puppies...|||That's correct. If you used the destination as a server, you have to connect to Integration Services and then see the packages under MSDB in stored packages. Alternatively, you can choose "DTSX File" as the destination for your migrated packages, and then save your packages as .dtsx files in your chosen folder. You can then add these packages to an SSIS Project and view/edit them in BI Studio.|||Hi.
Yeah, they are unregular XML-files, I guess. Not to be edited.

Try to enable and start the "DTS Server" service, then run
cmd
dtexec.exe /?

They can also be scheduled from within managment studio and run from bi studio.

Sunday, February 19, 2012

DTS in SQL 2005

SQL 2000 had a component called DTS. Has it channged name in SQL 2005?Zack wrote:
> SQL 2000 had a component called DTS. Has it channged name in SQL 2005?
>
It's now called SQL Server Integration Services, or SSIS.
http://www.microsoft.com/sql/techinfo/whitepapers/whats-new-in-ssis.mspx
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes. It is called SQL Server Integration Services (SSIS)\
http://msdn2.microsoft.com/en-us/library/ms141026.aspx
"Zack" wrote:
> SQL 2000 had a component called DTS. Has it channged name in SQL 2005?
>
>

DTS in SQL 2005

SQL 2000 had a component called DTS. Has it channged name in SQL 2005?
Zack wrote:
> SQL 2000 had a component called DTS. Has it channged name in SQL 2005?
>
It's now called SQL Server Integration Services, or SSIS.
http://www.microsoft.com/sql/techinfo/whitepapers/whats-new-in-ssis.mspx
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Yes. It is called SQL Server Integration Services (SSIS)\
http://msdn2.microsoft.com/en-us/library/ms141026.aspx
"Zack" wrote:

> SQL 2000 had a component called DTS. Has it channged name in SQL 2005?
>
>

DTS in SQL 2005

SQL 2000 had a component called DTS. Has it channged name in SQL 2005?Zack wrote:
> SQL 2000 had a component called DTS. Has it channged name in SQL 2005?
>
It's now called SQL Server Integration Services, or SSIS.
http://www.microsoft.com/sql/techin...ew-in-ssis.mspx
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes. It is called SQL Server Integration Services (SSIS)\
http://msdn2.microsoft.com/en-us/library/ms141026.aspx
"Zack" wrote:

> SQL 2000 had a component called DTS. Has it channged name in SQL 2005?
>
>