J
JM
This functionality is in Excel but I'm not sure if this is the appropriate
group to ask the question. Please redirect me to a better group if
appropriate.
I've used the functionality contained with Excel to create an OLAP Cube for
analysis in pivot tables and charts. {Data | Get External Data etc. } This
creates a file with the "cub" extension. Suppose I send this cube to another
person. How do they open it in Excel, without re-running the query? Do they
need the original Excel file?
Comparing this functionality with alternate tools like say Cognos. I notice
that Cognos can accept the "transaction" data in a separate file/query from
the hierarchies or metadata. This makes for a much more efficient cube
build, because each hierachies invariably holds many levels of text strings
indicating parent child relations, which can be joined to the transactional
data on a one-many relation on a short "key" field. Creating a cube with
Excel seems to require the data be joined into a single query view, which
makes the query result set huge and time consuming to run. Am I missing
something? Is there a way to create a cube in Excel, without joining the
hierarchy to the transaction data (ie the "join" is postponed to the last)
group to ask the question. Please redirect me to a better group if
appropriate.
I've used the functionality contained with Excel to create an OLAP Cube for
analysis in pivot tables and charts. {Data | Get External Data etc. } This
creates a file with the "cub" extension. Suppose I send this cube to another
person. How do they open it in Excel, without re-running the query? Do they
need the original Excel file?
Comparing this functionality with alternate tools like say Cognos. I notice
that Cognos can accept the "transaction" data in a separate file/query from
the hierarchies or metadata. This makes for a much more efficient cube
build, because each hierachies invariably holds many levels of text strings
indicating parent child relations, which can be joined to the transactional
data on a one-many relation on a short "key" field. Creating a cube with
Excel seems to require the data be joined into a single query view, which
makes the query result set huge and time consuming to run. Am I missing
something? Is there a way to create a cube in Excel, without joining the
hierarchy to the transaction data (ie the "join" is postponed to the last)