Vidas Matelis had put out a very good post with a great SSAS Whitepaper list. I strongly recommend you check it out as it summarizes some very important info about Management and Maintenance of SSAS.
If you’re intrigued about what SSAS Maestro is, it's a program incorporated from lessons learned at SQLCAT and given by Solid Quality Mentors. The description sounds fascinating! I admit I’m slightly jealous at anyone going, but I believe the information will be gradually available to more and more people.
In the meanwhile, go brush up on SSAS management and maintenance through the whitepapers.
So, as you may have gathered from the previous post, we installed SQL Server 2008 R2 in the municipality not too long ago. And yes, that led to all sort of problems...
One of the main problems that all of us encountered, was that we couldn't update our report models. Yes, we could start a new Report Builder 1.0 Project. We could define a DSV and autogenerate a Report Model. But then, if we added a table to the DSV or new columns were added to an existing table, and then we would run an Autogenerate on the Report Model again, then... well it would fail. We would get an error message saying the COM Object could not be recognized and either get a new entity in the Report Model without any attributes in it, or we would get blank new attributes in existing entities. We would end up adding new attributes manually to the model, binding them to the relevant field and giving them the proper name. needless to say, that was pretty frustrating.
We searched the internet for the error message or something about problems updating Report Builder 1.0 in SQL Server 2008 R2, but nothing came up. After a few mails with Microsoft support Israel, the answer was found...
So what's the solution? Cumulative Update 5 for SQL Server 2008 R2!
SQL Server 2008 R2 CU 5 includes a lot of fixes, and not just on the client side, but also on the server side.
I would like to thank Idit Izak from Microsoft support Israel that helped us reach a quick solution.
Please give Cumulative Update 5 a look and consider installing it on your PC and server.
We installed SQL Server 2008 R2 about 2 months ago, and I recently tried to use a new feature in Reporting Services 2008 R2. I used the Business Intelligence Development Studio (BIDS) to open a new Report Server Project. After creating a data source I also defined a shared dataset (a new feature to SSRS 2008 R2). I put some of the fields into a table and tried to run the report (still inside the BIDS). But I failed with an error:
The report preview failed because the report could not be built. Read the errors, warnings and messages in the Error List window for specific build features.
The data set, DataSet1, is a shared dataset. SQL Server 2008 Reporting Services does not support shared data sets.
I couldn't get it. I'm using BIDS from SQL Server 2008 R2 - what do you mean it's not supported? :S
Help was on the way quite quickly from Microsoft support Israel. Apparently, though I am using the BIDS from SQL Server 2008 R2, I still need to define my Target Server Version to SQL Server 2008 R2. The default setting is (for some reason) set to SQL Server 2008 (hence the error message).
Guess that just goes to show me, it's all about the little things (as always ;)).