Duplicate column name resolution - Error on execution

Question

Duplicate column name resolution - Error on execution

Saurabh Mathur

SSC-Addicted

Points: 481
More actions
September 21, 2005 at 11:27 pm

#76425

I am new to DTS, and was using it to import data from one database (3 tables) to another database (1 table).
I just used the standard Transform Data Task initially, and mapped the columns and got the following error:
"Duplicate column name resolution could not be done because the ordinal specified a column of a different name"
I thought this would be because I had in the source, 2 columns(from diff tables) with the same name. So, later on in the select query for the source, i made sure that the one table didnt include that column.
But i still get this error. Would anyone know how to deal with this error, and whether I have understood it fully?
Thanks

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 245813 More actions · Answer 1

Suggest you modify your queries to remove any likelihood of ambiguity between column names. Do this by prefixing the column name with the table name:

select tablename.columnname from tablename

If the table names are long, think about using aliases for clarity and speed of typing:

select t1.columnname from tablename t1

Regards

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Saurabh Mathur SSC-Addicted Points: 481 More actions · Answer 2

I managed to get the source columns all unique. Still get the error.

Got no clue what else could be the matter..!!!!

Any clue as to what else could cause this ?

Phil Parkin SSC Guru Points: 245813 More actions · Answer 3

I've never seen this message before - you've got something strange happening there! All I can suggest is that you remove transformations one at a time and keep trying ... eventually you will remove the one that's causing the problems and that should allow you to work out why the error is appearing.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.