Im trying to rename output columns in DataReader Source to be more readable.
For example: in the source table is column named GLMPUJ. After connecting
DataReader Source (SELECT GLMPUJ FROM tblSourceTable), there is External
Column named GLMPUJ and Output Column named GLMPUJ.
I renamed Output Column GLMPUJ to name DocumentNumber.

When Im using this DocumentNumber in data flows in design mode, it working
well. But when Im running package, the DataReader Source fails and says that
tblSourceTable does not contains column DocumentNumber.

Columns are connected well, the relation is created. I thought, that I can
rename output columns with no problem.

What is wrong???

Thanks for answer

Mike

I did it by AS keyword... SELECT GLMPUJ AS DocumentNumber FROM
tblSourceTable


"Mirek Endys" <MikeEndy (AT) nospam (DOT) nospam> wrote

I did it by AS keyword... SELECT GLMPUJ AS DocumentNumber FROM
tblSourceTable


"Mirek Endys" <MikeEndy (AT) nospam (DOT) nospam> wrote

I did it by AS keyword... SELECT GLMPUJ AS DocumentNumber FROM
tblSourceTable


"Mirek Endys" <MikeEndy (AT) nospam (DOT) nospam> wrote

I did it by AS keyword... SELECT GLMPUJ AS DocumentNumber FROM
tblSourceTable


"Mirek Endys" <MikeEndy (AT) nospam (DOT) nospam> wrote

I did it by AS keyword... SELECT GLMPUJ AS DocumentNumber FROM
tblSourceTable


"Mirek Endys" <MikeEndy (AT) nospam (DOT) nospam> wrote

I did it by AS keyword... SELECT GLMPUJ AS DocumentNumber FROM
tblSourceTable


"Mirek Endys" <MikeEndy (AT) nospam (DOT) nospam> wrote

I did it by AS keyword... SELECT GLMPUJ AS DocumentNumber FROM
tblSourceTable


"Mirek Endys" <MikeEndy (AT) nospam (DOT) nospam> wrote

I did it by AS keyword... SELECT GLMPUJ AS DocumentNumber FROM
tblSourceTable


"Mirek Endys" <MikeEndy (AT) nospam (DOT) nospam> wrote

On Wed, 24 Sep 2008 11:02:28 +0200, "Mike Endys"
<MikeEndy (AT) nospam (DOT) nospam> wrote:

That is one of three ways to assign an alias to an output column.

SELECT GLMPUJ AS DocumentNumber

SELECT GLMPUJ DocumentNumber

SELECT AS DocumentNumber = GLMPUJ

As you see in the second example AS is optional. Of the three that is
the one I do not use. That format also provides the annoying behavior
that a comma between two column in a SELECT list results in the former
column receiving the later column's name as an alias. That can be
very confusing.

I think that I have heard that the third format using = is not
standard SQL, but I am not certain. It can be the cleanest to read if
you format your SELECT neatly, as it is always right there up front
even when the expression is long and complicated.

Roy Harvey
Beacon Falls, CT