I have successfully migrated a SQL Server 2000 AS database to SQL
Server 2005 but am unable to process any of the cubes; each time I try
one I get OLE DB errors such as:

OLE DB error: OLE DB or ODBC error: [Native Error code: 103]
[DataDirect ADO Sybase Provider] The identifier that starts with
'[dbo_DimReportingROEYearOfAcc' is too long. Maximum length is 28.
; 42000; [Native Error code: 103]
[DataDirect ADO Sybase Provider] The identifier that starts with
'[dbo_DimReportingROEROEType0_' is too long. Maximum length is 28.
; 42000; [Native Error code: 11751]
[DataDirect ADO Sybase Provider] The column 'GBPROE' in the outer query
is not present in the derived table expression.
; HY000.

These cubes are based on Sybase tables and it appears that somewhere
the datasource is concatenating the table name with the column name.

We are using Sybase 12.5 client

Has anyone else experienced similar problems, please?
Thank you

Hi Rachel,

I have the same issue. How did you resolve this. One alternative someone
advised me is to create a linked server in sql 2005 for the sysbase server
and use it that way. But I can't really do it due to limitations.
Pls let me know if you had breakthrough on this.

Thanks
lakshman.

"rachel" wrote:

A couple of possible workaround should be to create VIEWS with short names
or name the tables in the DSV with shorter names.

Alternatively, you could modify the cartridge that you are using for the
Sybase provider (perhaps it is defaulting to the sql2000.xsl cartridge) to
set this property:
<mssqlcrt:limit-table-identifier-length>xx</mssqlcrt:limit-table-identifier-length>
to a smaller number like 28. But this is not a supported method and in fact
the Sybase data source is not supported by AS 2005.

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Lakshman" <Lakshman (AT) discussions (DOT) microsoft.com> wrote

Lakshman

I used the Migration Wizard - did you?
I have since been advised that this is what has caused the problem and
that it is better to recreate the cubes from scratch- a pain in the
neck but I think I shall treat it as a learning experience!
If I knew where to look i could probably fix the problem manually but
that would be a lot of work as well and frankly I haven't a clue where
to start!
Rachel


Akshai Mirchandani [MS] wrote: