Return to Answer

There is a wrapper specifically for sysschobjs in the OrcaMDF project, you can see the use of that here. Apparently, for SQL Server 2008 the MDF exploration needed no other Illuminati Views than sysschobjs, or perhaps the others on this list were not yet available.

The first thing that must be cleared up is everything is an object, including Illuminati Views and they all live in a sysschobjs table in the Resource DB (mssqlsystemresource).

The first thing that must be cleared up is everything is an object, including Illuminati Views. All databases have a table, sysschobjs, which contain that database's objects. And all databases pull from the sysschobjs in Resource DB (mssqlsystemresource).

After that I started playing around with the mssqlsystemresource directly. With this you can just query mssqlsystemresource.sys.sysschobjs. Using that method, I found one more, sysschobjs_dbscoped$ which has no corresponding object. Most Illuminati Views are in fact just lower level sources for Catalog Views by similar names. One exception is sys.sysschobjs$; sysschobjs is not a view, but a SYSTEM_TABLE. And, it may be somewhat confusing to call them lower level because while often Catalog Views pull from then, at the very least they sit above System Tables,

After that I started playing around with the mssqlsystemresource directly. With this you can just query mssqlsystemresource.sys.sysschobjs. Using that method, I found one more, sysschobjs_dbscoped$ which has no corresponding object. Most Illuminati Views are in fact just lower level sources for Catalog Views by similar names. One exception is sys.sysschobjs$; sysschobjs is not a view, but a SYSTEM_TABLE. And, it may be somewhat confusing to call them lower level because while often Catalog Views pull from them, at the very least they sit above System Tables,