Seggregating SQL tables/views for SCCM Application and for Admins
1286 tables and 7153 views, makes it an extensive and difficult job for SCCM Admins to create custom reports, as herculean task for finding where needed info exits, sometime data is available in multiple table/views, makes it tough to decide. Do you think it helps to re/design table or views naming structure in such a way that, set of them are meant for SCCM application for internal purposes which we don’t user for reporting purposes, and a second set of them are meant for SCCM Admin for creating report purposes, making the naming convention and data available in later section more intuitive and easy for admins. You may even keep current tables intact and create few views for admins, from those tables by following different naming convention for these views. Probably this could even reduce the direct load/impact on DB
FYI the supported SQL views have now be documented. And are being updated as needed.
may be good idea, but that make it non-compatible with old reports, all of the reports to be rebuild, lot of work for existing SCCM admins to relearn what they had learned for many years. Nevertheless it's good thinking....