 |
|
 |
|
 |
|
 |
|
 |
|
|
|
For more information, download our .pdf format brochure: The ETI Solution DSL for C/Microsoft SQL Server |
The ETI Solution® Data System Library? for
C/Microsoft SQL Server™
With support for OLE DB/ODBC
The ETI Solution Data System Library (DSL) for C/Microsoft SQL Server provides users with the ability to populate Microsoft SQL Server with data from disparate sources in an efficient and flexible manner as well as query SQL Server data. The DSL can be easily customized to meet a wide range of enterprise application integration needs. In addition, the DSL's architecture is based on OLE DB for access to OLE DB and ODBC data.
A powerful tool for data population
All SQL Server functions, SQL statements, and all commonly used data types are fully supported. Numerous features
increase programmer productivity; for example, automatic table lookup enables users to derive data values from
additional sources. The DSL generates all of the components required to populate or query a SQL Server database,
including all programs and batch scripts.
The DSL supports a variety of interfaces to provide maximum flexibility and optimal performance, including, for
example, OLE DB SQL to insert or update data and OLE DB FatLoad to facilitate bulk copying of when loading large
amounts of data. Another interface supported is Batch Fetch for fast reading of data.
Designed for high-level performance
The DSL for C/Microsoft SQL Server was designed from the ground up for high-level, automated performance. With
the DSL, users are not required to declare variables. Instead, they simply execute the SQL statement and the DSL
binds all columns automatically. The ordinals for the columns are resolved from the row meta data and are used in
specifying the bindings of the columns. Bindings include data value, length, and status of a column.
The DSL also uses batch fetching by default. This capability helps minimize overhead and provides maximum performance
for fetching data.
Fully customizable to meet unique needs
Users can take advantage of the DSL's extensive features out of the box. However, they can also customize the DSL for C/Microsoft SQL Server to meet highly specific requirements for migration and transformations. User-specific code, such as specialized read modules, can be incorporated by automatically inserting them into ETI Solution-generated code at certain points. These numerous, pre-specified code insertion points allow users can to define additional processing, alter processing behavior, or incorporate environment- or application-specific logic and routines.
OLE DB architecture enables connection
with other databases
The DSL for C/Microsoft SQL Server is based on the OLE DB architecture to allow the exchange of data with OLE DB
bridges (including ODBC), either as source or target.
This means that the DSL for C/Microsoft SQL Server allows connection with almost any database on the market today, including Lotus Notes, Excel, Access, Progress, and many other OLE DB/ODBC databases not supported by existing ETI Solution DSLs. A complete list of tested and supported drivers will be provided with the next release of the DSL.
DSL Architecture provides a powerful,
flexible foundation
The DSL for C/Microsoft SQL Server was constructed using ETI's new DSL Architecture, a fourth-generation foundation
for Data System Libraries. The new architecture (abbreviated to "DA," for "DSL Architecture")
ensures that all DSLs share the same rich, modular functionality. The end result is more power for users.
DA provides for consistency between all DSLs-if a user knows one DSL he or she knows them all. DA makes it easier
than ever before to specify business rules, and easier to understand meta data about business rules. And new features
ensure that DSLs can be easily customized to meet unique corporate or industry requirements.
A strategic database solution
With ETI Solution and the DSL for C/Microsoft SQL Server, users can now:
- Populate Microsoft SQL Server with data from a number of sources, in an effective manner,
- Reduce or completely eliminate handcoding required to migrate data among Microsoft SQL Server databases,
- Migrate data among OLE DB/ODBC databases,
- Develop a standardized, reusable solution for database connectivity, and
- Expand the usability of their Microsoft SQL Server solution, helping to create a database environment that can leverage legacy databases as well as accommodate future growth and expansion.
