Currently sorting out a resource to create training material for new users.

A lot of the clients users are unfamiliar with both Excel and the EDW Content, not to mention SAS.

So we are aiming for a simple user guide that shows users how to access Information Maps via Excel Pivots and another on how to access OLAP Cubes via Excel Pivot tables.

Then lastly a little more in-depth training material on how to use Excel Pivot tables with any sort of data.

Moving the SAS 9.2 environment from the old SAN based server to a new server with a dedicated disk array, to resolve some I/O issues under high load.  Will be using shadow copy to automate the move across machines as it manages the swap out of drivers etc for the new hardware.

Currently working on a developing a BI/DW technical architecture to define how we will manage an environment with multiple ETL and Reporting tools.

Will feed into the Enterprise Information Management and Reporting Strategy we are working on.

Had some issues with users using the SAS Addin for Microsoft Office against Info Maps where the size of the Excel file gets massive when you save it.

It seems Excel must be caching the data somewhere.

We are working on configuring SAS OLAP cubes in ROLAP mode as this removes the size issues with Excel.

We are re-branding the project after the successful completion of decommissioning the old Data Warehouse environment at the end of the month. So we are currently changing the SAS Portal theme to match the new brand.

Just found out Windows 2008 R2 is not currently supported for SAS 9.2, but it seems to work on the test install I did.

We are using a combination of SAS Web Report Studio, for report creation/rendering and an Oracle database for data storage.

When users run reports, they effectively invoke this process:

1. Connect to metadata and obtain authorisation
2. Access info map and generate query
3. Pass query to Oracle
4. Oracle passes data to WRS
5. WRS renders report

To make this faster we have been looking at configuring report scheduling to see if we can pre-cache the reports

Starting work on a business case for an Enterprise Information Management and Reporting Strategy.

Similiar to a BI Strategy but needs to include unstructured data management as well as lot more focus on people and process than BI reporting tools.

Setting up channels so that we can publish content to users without the need to store it on the filesystem.

Using Webdav as the storage mechanism.

Using custom DI code node to create content and publish as part of our standard ETL process flows.

Doing a test install of SAS 9.2 on Windows 2008 R2, with Weblogic 10.3.

We have decided to do the install without the STM Solutions layer to make the install easier as we only want to test migration of BI and DI content.