OpenEdge Data Management: DataServer for Microsoft SQL Server

Configuring the DataServer
Maintaining a schema holder
5–22
The Data Administration provides a set of DataServer utilities that you can use to maintain a
schema holder. Chapter 7, “The DataServer Tutorial,” describes these utilities.
Note: Keep in mind that you must have SELECT privileges on certain data source objects to
update a schema holder. See the “Permission requirements” section on page 5–15 for
details.
If you make changes to a MS SQL Server database, make sure to update the associated schema
holder to reflect those changes if you want them to be accessible to a DataServer application.
Note that you do not need to update the schema holder if the application will never access data
objects affected by the change. For example, if you add a table object that a DataServer
application will never access, you do not need to update the schema holder.
Each time that you update the schema holder, you must recompile your DataServer application
(.p and .w files) to generate new r-code.
Updating a deployed schema holder
The guidelines and techniques that apply to deploying an OpenEdge database also apply to
deploying a schema holder for a MS SQL Server database. However, if you make any changes
to the data source schema, make sure to update its schema holder. There are two techniques for
updating a deployed schema holder:
• Allow your users to use the DataServer Update/Add Table Definitions utility.
• Send a new data definition file for the schema holder. Your users can use the DataServer
Delete Schema utility to empty the original schema holder. They can then load the new
data-definition file into the schema holder.
To update a deployed DataServer application:
1. Run an SQL script to make changes to the MS SQL Server database.
2. Run the Update/Add Table Definitions utility on one schema holder.
3. Recompile code against the updated schema holder to build new r-code.
4. Send out copies of the new .r files to your users.
5. Distribute copies of the new schema holder .db and .bi files to your users. You must use
the PROCOPY utility to distribute them.