Working on upgrade to V7

[slimdave]

Hi folks,

We have about a dozen projects in Mstr v6, and are upgrading to v7.

Aside from the simple technical stuff, how much scope would you say there is for improving the projects by taking advantage of new features etc. Now I realise that this is a rather open-ended question, but I'm wondering whether a simple upgrade of the software might leave us with a system that is missing out on a huge range of new features.

Are there any particular areas you would target for work?

 

[nlim]

just a few areas to think about:

Performance and scalability
---------------------------
- object caching should be turned on
- scheduling reports!
- some vldb switches for specific databases (eg. derived tables.....)
- some things you do thru views today might work without views....like heterogenous columns for ids...expression based def (eg. age = sysdate-cust_DOB)

Analytics
---------
lots of new analytics to consider using
- stats, running sums and averages, financial calculations.
v7 custom groups = v6consolidations.
v7 consolidations is brand new
new subtotaling
multi-level transformation

Security
--------
- limit users to specific slices of data using security filters
- privilege control. decide which user gets to save reports, create metrics and other privileges...

Reporting functionality
-----------------------
- numerical prompts lets you do so "what-if" type analysis
- object prompts let you create "subject area" reports.
- drill on custom groups enabled
- drill to another report altogether. This facilitates guide train of thought analysis.

have fun!