External data sources are applied configuration objects. They allow managing third-party databases beyond 1C:Enterprise. This said these configuration objects help use data from external databases within an application as if it was stored in the infobase itself.
An external source may get data from ODBC sources on Windows and Linux. With that, using such DBMS's as Microsoft SQL Server, IBM DB2, PostgreSQL, and Oracle Database allow the full range of capabilities of the query language. Besides, external data sources allow connecting multidimensional data sources to an application. Examples:
-
Microsoft Analysis Services
-
Oracle Essbase
-
IBM InfoSphere Warehouse
During using other DBMS's, some query language structures may be unavailable as they are limited to the capabilities of the ODBC driver used.
An external data source consists of a set of tables.
Tables of an external data source can be described manually or with the use of a constructor.
Using the connection string, a constructor may connect to an external database and provide a list of tables available for adding to an external source.
Basically, every table constitutes a standalone configuration object. It contains a set of fields. For a table, forms may be defined, commands created, and templates set.
Tables of external data sources are used in the configuration in the very same way as tables of any other configuration objects.
For instance, the platform automatically generates forms for them; otherwise, the developer can manually create a form.
Data in those tables can be referred to with the help of the query language.
Those tables can be used in reports in the data composition systems.
Also, items of those tables can be referred to as any other object-type data— e.g. catalog items or documents.
Next page: DBF files
