OpenEdge Data Management: DataServer for Microsoft SQL Server

Figure 3 illustrates the schema-loading process.
Figure 3: The schema-loading process
DataServer components
If you plan to use the DataServer to send SQL statements directly to the data source
using only the RUN STORED–PROCEDURE syntax and you do not expect returned data, you
need not load data definitions into the schema holder. However, you must do the
following:
• Load the stored procedure into the schema holder.
• Connect to an empty data source.
However, the RDBMS stored procedures also supports s and ProDataSet functionality
which does support returning data to the foreign data source. For information on using
RUN STORED–PROCEDURE, see Chapter 3, “RDBMS Stored Procedure Details.”
Security
OpenEdge schema holder
Using the DataServer for MS SQL Server involves following the security guidelines
required by both the OpenEdge database and the MS SQL Server data source. By
default, OpenEdge security allows unrestricted access to data sources, so at a
minimum, you should follow the guidelines that the data source requires for your
applications.
OpenEdge security
Cust_num INTEGER
Name CHARACTER
Max_credit DECIMAL
The OpenEdge database management system has no minimum security
requirements. You can, however, impose security features on any OpenEdge
database or schema holder. There are four levels of application security that you can
impose:
• Database-connection security
• Schema security
• Compile-time security
• Runtime security
Data source
data definitions
Cust_nm INT
Name VARCHAR
Max_credit DECIMAL
For more information about compile-time and run-time security, see OpenEdge
Deployment: Managing ABL Applications. For general information about OpenEdge
security, see OpenEdge Getting Started: Core Business Services - Security and
Auditing.
OpenEdge Data Management: DataServer for Microsoft SQL Server 41