dbTalk Databases Forums  

SSIS Transfer Database Task fails between 2000 and 2005

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss SSIS Transfer Database Task fails between 2000 and 2005 in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
larchevv
 
Posts: n/a

Default SSIS Transfer Database Task fails between 2000 and 2005 - 07-21-2006 , 11:43 AM






Hi,

I am trying to copy a database using the Database Transfer Task in
SSIS. My package always fails with the following error 0x80131500 (
-1073548784 ) saying that the login XXX already exists in the database.



When I change my package to run between two SQL 2000 instances,
everything works.


Microsoft documentation says that it should work between 200 and 2005.


Any idea?


Thanks,


Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SSIS Transfer Database Task fails between 2000 and 2005 - 07-24-2006 , 01:14 PM






Hello larchevv,

Have a look through profiler at the code being generated by the task. If
that still fails then is using BACKUP and RESTORE an option?


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Quote:
Hi,

I am trying to copy a database using the Database Transfer Task in
SSIS. My package always fails with the following error 0x80131500 (
-1073548784 ) saying that the login XXX already exists in the
database.

When I change my package to run between two SQL 2000 instances,
everything works.

Microsoft documentation says that it should work between 200 and 2005.

Any idea?

Thanks,




Reply With Quote
  #3  
Old   
larchevv
 
Posts: n/a

Default Re: SSIS Transfer Database Task fails between 2000 and 2005 - 07-25-2006 , 01:07 AM



I can always use BACKUP AND RESTORE. It is very annoying that Microsoft
always creates those "helpers" that always ends up causing more
problems that help.



Allan Mitchell wrote:
Quote:
Hello larchevv,

Have a look through profiler at the code being generated by the task. If
that still fails then is using BACKUP and RESTORE an option?


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Hi,

I am trying to copy a database using the Database Transfer Task in
SSIS. My package always fails with the following error 0x80131500 (
-1073548784 ) saying that the login XXX already exists in the
database.

When I change my package to run between two SQL 2000 instances,
everything works.

Microsoft documentation says that it should work between 200 and 2005.

Any idea?

Thanks,



Reply With Quote
  #4  
Old   
larchevv
 
Posts: n/a

Default Re: SSIS Transfer Database Task fails between 2000 and 2005 - 07-25-2006 , 01:10 AM



The main reason why I wanted to use the Transfer DB task is that it is
SUPPOSE to take care of the logins and users transfer as well.

larchevv wrote:
Quote:
I can always use BACKUP AND RESTORE. It is very annoying that Microsoft
always creates those "helpers" that always ends up causing more
problems that help.



Allan Mitchell wrote:
Hello larchevv,

Have a look through profiler at the code being generated by the task. If
that still fails then is using BACKUP and RESTORE an option?


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Hi,

I am trying to copy a database using the Database Transfer Task in
SSIS. My package always fails with the following error 0x80131500 (
-1073548784 ) saying that the login XXX already exists in the
database.

When I change my package to run between two SQL 2000 instances,
everything works.

Microsoft documentation says that it should work between 200 and 2005.

Any idea?

Thanks,



Reply With Quote
  #5  
Old   
Clutch
 
Posts: n/a

Default Re: SSIS Transfer Database Task fails between 2000 and 2005 - 07-26-2006 , 08:46 AM



I'm having the same problem, although, instead of it being the login
that already exists it's a role for me. Have you figured out a way
around this? It really is frustrating because you don't have control
on the actual script that's being used to transfer the database.

Thanks in advance.


larchevv wrote:
Quote:
The main reason why I wanted to use the Transfer DB task is that it is
SUPPOSE to take care of the logins and users transfer as well.

larchevv wrote:
I can always use BACKUP AND RESTORE. It is very annoying that Microsoft
always creates those "helpers" that always ends up causing more
problems that help.



Allan Mitchell wrote:
Hello larchevv,

Have a look through profiler at the code being generated by the task. If
that still fails then is using BACKUP and RESTORE an option?


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Hi,

I am trying to copy a database using the Database Transfer Task in
SSIS. My package always fails with the following error 0x80131500 (
-1073548784 ) saying that the login XXX already exists in the
database.

When I change my package to run between two SQL 2000 instances,
everything works.

Microsoft documentation says that it should work between 200 and 2005.

Any idea?

Thanks,



Reply With Quote
  #6  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SSIS Transfer Database Task fails between 2000 and 2005 - 07-26-2006 , 01:36 PM



In the Transfer Database task I can see no way for the task to take care of
logins. Users yes as they are in the DB being transferred.

--


Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com


Quote:
larchevv wrote:
The main reason why I wanted to use the Transfer DB task is that it is
SUPPOSE to take care of the logins and users transfer as well.

larchevv wrote:
I can always use BACKUP AND RESTORE. It is very annoying that Microsoft
always creates those "helpers" that always ends up causing more
problems that help.



Allan Mitchell wrote:
Hello larchevv,

Have a look through profiler at the code being generated by the task.
If
that still fails then is using BACKUP and RESTORE an option?


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Hi,

I am trying to copy a database using the Database Transfer Task in
SSIS. My package always fails with the following error 0x80131500 (
-1073548784 ) saying that the login XXX already exists in the
database.

When I change my package to run between two SQL 2000 instances,
everything works.

Microsoft documentation says that it should work between 200 and
2005.

Any idea?

Thanks,





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.