Recreating a Report Model

October 31, 2007

Remember how I taught you to recreate your Analysis Project? Well, let's say this time you have a model you deployed to the Reporting Services Server, but you have changed it since then and want the old version back. So how would you recreate the model you have on the server?  First of all, create a new Data Source View in your Analysis Project. It doesn't have to include all the relevant tables, as you'll only use it as a shell to build upon. After you've finished defining the DSV, save the project. Then, right click the new DSV...

A Shift in the Market

October 26, 2007

This week, a couple of things happened. The first big news was that SAP had purchased Business Objects. The move is considered a response to Oracle buying Hyperion earlier this year. Microsoft has acquired ProClarity earlier in 2006. There also remains Cognos, SAS and Panorama as individual players. Still, Panorama has its own sort of news for this week, after it fired 20 of its workers in Israel (the article is in Hebrew). The workers are said to be from the development department and make for a fifth of the entire Israeli office of Panorama (which has 250 workers...
tags: ,

Cumulative update package 4 for SQL Server 2005 Service Pack 2

October 16, 2007

CU 4 was released yesterday, and as in previous versions, contains the hotfixes that have been developed since the release of SP2. Like with cumulative update 3, this one is also multilanguage and is available through writing a request to Microsoft Online Customer Services at To install cumulative update package 4 for SQL Server 2005 Service Pack 2, you need to enable the SMO and the SQL-DMO stored procedures. The cumulative update is also known as build 3200. For further detail, please see the knowledge base article.

The Parent – Child Dimension

October 9, 2007

A Parent - Child Dimension is a special sort of dimension, to be used in case:  You have data even for non – leaf members. For instance, you may have set – up costs allocated for the Category level (the higher level), but profit data for your Product level (the lower level). You have an unbalanced hierarchy. The classic example for this might be the Geographical Hierarchy which at times might look like: Country > State > City, and at other times like Country > City. For an international company trying to track its worldwide business, the hierarchy in the US...