Hello,
I've built a cube using AS 2005 from a DB2 version 7 dimensional data
source. Processing it directly from DB2 fails because AS 2005 is
attempting to issue SQL statements against DB2 with table alias names
that exceed the maximum limits - which is 18 characters for DB2 version
7. For example, this is the kind of statement that is auto-generated:

SELECT
DISTINCT "MIS_ACTIVITY_STATISTIC"."ACTIVITY_START_DT" AS
"MIS_ACTIVITY_STATISTIC0_0"
FROM
"MIS"."ACTIVITY_STATISTIC" AS "MIS_ACTIVITY_STATISTIC"

Is there a way to force AS 2005 to generate shorter names, suitable for
DB2 v7?

I came across a post refering to a similar problem when using a Sybase
data source. The suggested solution was to replace a "cartridge" xsl
file with one corresponding to the correct Sybase version. Indeed, the
analogous file installed on my machine is "db2v0801.xsl" which
presumably targets DB2 version 8 (and v8 supports larger names). If
that's the solution, where can I get the appropriate file for DB2 v7?
Alternatively, can db2v0801.xsl be modified to produce the correct
output?

Cheers,
David.

The simplest workaround would be to change 'db2v0801.xsl' but none of these
are officially supported techniques and DB2 v7 isn't a supported AS data
source.

Thanks,
Akshai
--
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.

"Dave" <david.antelmi (AT) gmail (DOT) com> wrote

Akshai,

Thanks for your response. Do you know of any public resources or
documentation on the way the xsl works?

David.

I'm still having problems with this as well. I've got a Sybase cartridge but
it still seems to use the SQL Server one - same problem with long identifiers
- I can't see how to force AS2005 to use a different cartridge, and no
documentation in BOL (I think). MS just say - it's not supported. See my post
on 16.12.2005.

"Dave" wrote:

Sorry, as of now the .xsls aren't documented. This might change in the
future, but they're complex enough to make it quite a difficult task (and
supporting custom cartridges could become a problem)...

Steve, the server will use the OLE DB properties DBMSName and DBMSVersion to
find a cartridge that matches -- if it isn't finding the one you have
created, then probably those two properties aren't matching the cartridge.
Try to query those two properties in rowsetviewer or a small ADO sample
application and update the cartridge to use the correct values...

HTH,
Akshai
--
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.

"Steve G" <SteveG (AT) discussions (DOT) microsoft.com> wrote