By Jeffrey McDaniel on Dec 04, 2013
If you are working in the P6 Reporting Database or P6 Analytics and you notice that either your spread range or resource utilization and limit ranges haven't adjusted more than likely it has to do with your P6 Extended Schema.
First check in your STAR schema:
select min(day_dt),max(day_dt) from w_day_d;
In the P6 Extended schema an initial date range is set when the project services and global services are run the 1st time. Generally the range is not changed after that point. The date range creates a rolling window of time. You set your start date and then your finish range to be plus a certain amount of months or years in the future. An example is setting your start date to be:
Jan-1-2012 and a rolling 3 year window (today's date + 3 years).
Looking at the ReportDate table you want to see if this matches your expected date range:
select min(daydate),max(daydate) from reportdate;
If all global services were run today and project services this should be updated and max should reflect today's date. If for some reason it does not make sure the Enterprise Data service has been run. Make sure you are still publishing projects. And if all seems functional, a last case scenario you could truncate the reportdate table then rerun the Enterprise Data service. This will force a new recalculation of the date range for this table.
After this is completed you can run the StarETL and you should see w_day_d updated with this date range. If for any reason you are still seeing an issue then the w_day_d can be truncated and repopulated on the next ETL run. Again truncating of these tables should not be necessary and is only in extreme cases. In a majority of cases having the Enterprise Data service and ETL run will make sure all date ranges in the P6 Reporting Database and P6 Analytics are up to date.