Dave,
I have a follow-on question from this thread. One reader posted that as
a workaround we can create a named query around the table to cast the
tinyint field to an int. What is the impact of converting the physical
table to named query tables in the data source view, assuming that it
was just a <select * from some_table> without any joins to other
tables? Finally, I'm using Oracel for my data mart and some pl-sql
conversion functions will not work, such as the CAST ot CONVERT
function, so I'm SOL when it comes to converting unless I use TO_NUMBER
but it becomes system.decimal rather than system.int64 which is what I
want. Would like your input on this. Thanks.
Julius

Using named query should slow down the process depending on how complicate
your query. Just <select * from table> should have less impact.

BTW, named query is one of the ways to make tinyint to int. Another way is
to open the DSV in XML mode and modify the column data type to int (You can
copy the format from other int columns). However, it will be changed when
you refresh DSV next time. If you never refresh DSV, it may be convinent to
you.

There are 2 query builders when you open query builder dialog. By default,
it is VDT query builder which provides you more graphical table layout but
it has problem on parsing query. You can switch to generic query builder by
hitting the first toolbar button. This generic query builder does not parse
your query and hopefully this one will help.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

Ken Kwok
SQL Server Analysis Services

<jconcepcion (AT) gmail (DOT) com> wrote