March 19, 2011 at 12:51 pm
I have a question about SSRS, and really really need help. please kindly help me. I have similar question on various forums but...
My company has a big cube covering several business processes and data mart supporting it. This is not exactly working very well hence, we have plans to decompose into several cubes supporting individual business processes et al. This is planned over several next months and will be carried in phases.. alongside there are plenty other database field changes.
This will mean if there will be major disturbance for reporting.. There will be many breaking stored procedures, many non working reports and lots of frustration. My line manager has asked me to look into the possibility to avoid/overcome this situation.
I was thinking of bringing another layer on top DW database for Reporting. It will be like "Interfaces" where any change we make in existing database, we still have same "interface" views for reporting services. It might mean more work for developers making breaking change but will at least ensure smooth Reporting.
Shall I propose this to management? I am not sure how it will work with Cubes? Do you have any suggession to save me, please??
We have SQL Server 2K8R2 and are thinking of Sharepoint Foundation 2010 as reporting interface for end/power users along with PoverPivot..
March 25, 2011 at 3:39 am
If you're using stored procedures, then it should be easy, just making sure they return the same data as before.
If you have a mix of stored procedures and something else, you could create and maintain views which mimic the current structure.
But if you're using Report Models, you'll have to throw them all out and create new ones, along with the reports which go with them 🙁
March 25, 2011 at 4:51 am
I wouldn't use an interface layer, you would have trouble getting this to work with a cube and you would end up developing everything twice.
My approach would be a non-technical one where you use an Agile approach to developing the cube and tackle each report one by one.. though how this would work in your organisation would depend on how you are setup.
I think any adding of layers would end up more work.
I wouldn't bother with report models as chances are they will be deprecated in future releases and taken over by the BISM..
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply