Request for TrueSight Capacity Optimization (TSCO) Database Internal Schema |
The recommended interface for accessing data from the TrueSight Capacity Optimization (TSCO) database are the Public Views. The Public View (PV) views are the only officially supported 'tables' available in the TSCO database. This means that the only information we can provide from Technical Support will be related to the Public Views or related to queries documented in published solution documents. Beyond the Public Views currently there is no public available documentation about the internal schema for the TSCO data warehouse. Accessing internal data warehouse tables is not recommended and might be affected by upgrade since there is a chance the data warehouse structure may be changed between releases. Q: Can the Public View tables be joined against other tables in the TSCO data warehouse?In general, since PVs are just views into the data tables you should always be able to join PV tables to the other tables within CO, but Technical Support is not able to provide any information on how to do that. Database access outside of the PVs is outside of the scope of TSCO Technical Support. So, the general policy would be that information on how to join with tables outside of the PVs is outside of the scope of Technical Support. Q: Is there a direct correlation between the naming conventions of the Public Views and the private BCO database tables? For example, is PV_SYS_DATA_D the same as SYS_DATA_D?There isn't a direct correlation rule between Private View names and TSCO internal table names, but there is frequently a correlation. So, PV_SYS_DATA_D is the Public View into the SYS_DATA_D table (raw/detail data) and PV_SYS_DATA_DAY is the public view into the SYS_DATA_DH table (hourly summary data). Q: Will the PVs work with the SQL View Template and be fully compliant with custom dashboards? I thought the PVs were mainly for BIRT reports?Yes, the PVs are fully supported views and SQL can be written against them from any component of the product (TSCO Console or TSCO Views). Q: When a new version of CO is released will the Release Notes document which tables were modified to allow us to review any queries we've written against the internal BO tables because an equivalent Public View didn't exist?No, that is one of the purposes restricting access to only the Public View tables. We consider the Public View tables to be the only public interface into the TSCO database. Thus, we will document any changes in the Public View tables that would impact an existing query but we would not document changes related to the internal TSCO tables from release to release. Q: What should be done if I require access to data that exists in the TSCO database but is not available via a Public View?If you are trying to create a specific type of view in the TSCO Dashboard we can take a Request for Enhancement to make a PV available in TSCO that would make that data available. Q: Is there a Public View available in TSCO to access data from the forecast models -- for example a PV_FORECAST view which would contain useful forecasting values for systems?There are two existing PV where Golden Model data is published:
Related Products:
|