Analysis Services really shines as a client-server solution. However, for remote locations, portability, and custom applications, local cubes may be what you want.
Creating a local cube is fairly simple so I won't go into it.
The syntax can be found here.
http://msdn2.microsoft.com/en-us/library/ms145581.aspx
After playing a bit with the parameters, I managed to create a global cube located in a .cub file on my laptop. Oddly enough, Excel 2003 does not associate .cub files, so you need to either associate it or open Excel and then open the .cub file. Opening the file brings up the standard pivot table interface against the local cube. A couple problems I encountered - dragging in dimension attributes appeared slower than hosting the cube on a server, and I encountered the 64,000 row limit pretty quickly.
I passed the cube on to someone else in our company, who received a No Visible Tables error message.
Nobody said client requirements for BI solutions were trivial.
Here they are.
Microsoft .NET Framework Version 2.0 Redistributable Package (x86)
MSXLM 6.0 Parser
Microsoft SQL Server 2000 PivotTable Services
Microsoft SQL Server 2005 Analysis Provider Services 9.0 OLEDB Provider
Of course, Analysis Services 2005 also has support for synchronizing databases, so if it is possible to keep multiple servers at remote locations, this would probably be the better route for things like SOX compliance and security purposes.
1 comment:
We've released a new tool to create local cubes from any relational database or text files.
The product is called Olapcube, the product website is: http://www.olapcube.com
You can contact us at olapcube@adersoft.com
Thank you.
Jean-Herve - Adersoft
Post a Comment