Data processor allows you to see the names of tables and fields in the form in which DBMS works with them. Will be useful when designing the direct queries to the database server and integrating with other systems (bypassing 1С server).
1С platform is a high-level tool to work with databases. In general, the developer does not need to worry about what and how happens on the DBMS side, because the platform decides itself how many tables it will create and what fields will be inside them.
However, in large projects there is a need to work with data directly, for example, to analyse information using the third-party tools or, as in my case, to integrate databases with external applications. In this situation it is required to know in which fields of physical tables we should search the information we need.
Just for this case the built-in function GetDBStorageStructureInfo() is designed which returns all necessary data in the form of value table. And some attributes (Fields and Indexes) of this table are the tables of values by themselves.
On the one hand, it is convenient to have all data in a single structure, but, on the other hand, the additional problems occur associated with transfer of this table to the client (unfortunately, method Load() does not load the nested tables). On this account, we have to run through all table rows in a cycle that leads to the operation slowdown for large volumes.
In this regard, the best option will be to pass in the function the names of metadata objects in order to reduce the volume of returned data. However, not all DBMS tables are associated with configuration metadata, so, I left the opportunity to view the full list.
When activating the metadata tree item, the list of tables, fields and indexes is filled. When you double-click on the tree root, all tables are displayed including service ones.
In the table parts the standard commands are working to search and display the list.
This processor contains the most complete metadata tree (exchange plans, constants, document journals, etc.).
Data structure is presented clearly: list of metadata object tables, list of fields and list of indexes are displayed in the individual table parts.
P.S. Some employers in hiring ask the question on the number of physical and virtual tables for registers. It would be nice to know the answers to all these questions, more by token, this is a 1С:Professional level. If you want not only to learn this answer, but also to “examine” these tables, then this processor is for you!