Error copying data to a remote sql server 2005 database.

When copying data to a remote SQL2K5 destination from a SQL2K5 source database, both using mixed sql server security mode, my job generates the following error:

[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".

This occurs after the destination database tables have been truncated and replacement data from the source would begin to copy.

The same process can be successfully completed from the Management studio with a simple data export process. However, when I run the saved package again from the BI interface, I get this error.

My search engine searches have yielded numerous hits of others having the same problem with one microsoft rep indicating it was a bug and would be resolved in sp1. I am working with sp1. Oddly, there is only mention of this in the forums. No KB article from MS addresses the problem and I do not see it addressed elsewhere at sqlservercentral.

It appears that others have switched to Integrated Security and resolved the problem. However, I do not have that option with a remotely hosted database.

Does anyone have any information concerning this problem?

bug reports may be submitted here: SQL Server Feedback.

i suggest that you first check for the status of any existing bug report to avoid duplication.

error column

Hi,

There is an error output from one oledb destination which causes error to another which populated a table called tblFailedRows.

I have mapped the errorcolumn to the errorcolumn in tblFailedRows.

When looking at the errorcolumn in tblFailedRows I see just numbers not the column name.

How do I get the column name that causes the error?

Thanks

Here's a thread with information on this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1509836&SiteID=1

error column

Hi,

Using SSIS, while importing (source i.e. .csv into destination i.e. sql server table), how is it possible to log the source COLUMN which causes the error in the row?

Thanks

Hello Arkiboys,

Many data flow components, including most sources and destinations, support an "Error Ouput" concept whereby you can work with the individual rows of data that could not be successfully processed by a component. This error output includes an ErrorCode and ErrorColumn that you can use in many cases to determine the column that is causing the error.

For more information, I'd suggest taking a look at this:

http://msdn2.microsoft.com/en-us/library/ms141679.aspx

-David

|||

Hi,

I followed the lonk.
Not sure why I do not get the error columns expanded as it says in the link.

Still do not know how to pull the column out i.e. I have a stored procedure which I would like to record the error columns. How do I get these error columns name and rows?

Thanks

Error at Transfer Objects Task: The source server can not be the same as the destination server.

SQL Server 2005 - June CTP

Error at Transfer Objects Task [Transfer Objects Task]: The source server can not be the same as the destination server.

Why not? I'm trying to transfer a set of tables from one database to another. Both databases happen to be on the same server. I understand that the source *database* cannot be the same as the destination *database*. But why can't I use the Transfer Objects task to transfer objects from one database to another on the same server?

Thanks for your help!

I can easily reproduce this. I would agree with Joseph, moving between databases on the same server is a legitamate requirement.

-Jamie|||I bumped into this problem several weeks ago and was only told "there are known problems with the transfer objects task"

My work around is to use an execute sql task that uses a fully qualified Insert statement to insert records into database 2 from database 1

Insert database2.dbo.tableA select * from database1.dbo.tableA

While it is a royal pain to have to have a line per table (250+ tables..changing on a regular basis) it does work and I get my records from the staging DB to the production

Paul Pisarek|||Paul,

Sorry about the curt response. Please reactivate the bug and follow through until you're satisfied with either the explaination or the resolution.

thanks,
ash|||

Dear Sharma,

Could you please update everyone whether the bug is resolved or yet to be resolved as we are facing a lot of issues in this task even after installing Service Pack Sp1.

Thanks,

Pradeep

+91 99451 20960

Pradeep.au@.gmail.com

|||

As far as I can see, with the production release of VS 2005, the original bug which I reported 'the source server cannot be the same as the destination server' has been corrected. I just used the Transfer SQL Server Objects task to transfer all objects (i.e. Tables, Views, Data, Indexes, etc.) from one database to another on the same server.

What 'issues' specifically are you encountering?

- Joe Geretz -

Error at Transfer Objects Task: The source server can not be the same as the destination ser

SQL Server 2005 - June CTP

Error at Transfer Objects Task [Transfer Objects Task]: The source server can not be the same as the destination server.

Why not? I'm trying to transfer a set of tables from one database to another. Both databases happen to be on the same server. I understand that the source *database* cannot be the same as the destination *database*. But why can't I use the Transfer Objects task to transfer objects from one database to another on the same server?

Thanks for your help!

I can easily reproduce this. I would agree with Joseph, moving between databases on the same server is a legitamate requirement.

-Jamie|||I bumped into this problem several weeks ago and was only told "there are known problems with the transfer objects task"

My work around is to use an execute sql task that uses a fully qualified Insert statement to insert records into database 2 from database 1

Insert database2.dbo.tableA select * from database1.dbo.tableA

While it is a royal pain to have to have a line per table (250+ tables..changing on a regular basis) it does work and I get my records from the staging DB to the production

Paul Pisarek|||Paul,

Sorry about the curt response. Please reactivate the bug and follow through until you're satisfied with either the explaination or the resolution.

thanks,
ash|||

Dear Sharma,

Could you please update everyone whether the bug is resolved or yet to be resolved as we are facing a lot of issues in this task even after installing Service Pack Sp1.

Thanks,

Pradeep

+91 99451 20960

Pradeep.au@.gmail.com

|||

As far as I can see, with the production release of VS 2005, the original bug which I reported 'the source server cannot be the same as the destination server' has been corrected. I just used the Transfer SQL Server Objects task to transfer all objects (i.e. Tables, Views, Data, Indexes, etc.) from one database to another on the same server.

What 'issues' specifically are you encountering?

- Joe Geretz -