13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Creating a schema holder<br />

Creating a schema holder<br />

A schema holder contains a schema image of the MS <strong>SQL</strong> <strong>Server</strong> database that your<br />

<strong>Data</strong><strong>Server</strong> application accesses. The schema image contains the schema <strong>for</strong> your<br />

data source—that is, its data definitions—in an <strong>OpenEdge</strong> <strong>for</strong>mat. Although <strong>OpenEdge</strong><br />

applications can access a data source directly by sending <strong>SQL</strong> statements through the<br />

<strong>Data</strong><strong>Server</strong>, they cannot directly access its data definitions and must use the<br />

schema-image in<strong>for</strong>mation instead.<br />

Be<strong>for</strong>e you begin<br />

Consider your business needs and deployment strategy when you decide where to<br />

build your schema holder. The schema holder can reside on the client machine or on<br />

any host in an enterprise configuration. Client schema holders improve per<strong>for</strong>mance<br />

<strong>for</strong> some applications. Host schema holders give you the flexibility of having them run<br />

as Windows services. Additionally, host schema holders might be easier to maintain.<br />

In a WebSpeed configuration, placing the schema holder on the Transaction <strong>Server</strong><br />

machine optimizes per<strong>for</strong>mance.<br />

General schema holder creation tasks<br />

In general, you must do the following to create a schema holder:<br />

1. Establish the appropriate server permissions needed <strong>for</strong> pulling the schema<br />

image into the schema holder.<br />

2. Per<strong>for</strong>m some preparatory steps.<br />

3. Create and then connect an empty <strong>OpenEdge</strong> database. This database becomes<br />

your schema holder and contains your schema image.<br />

4. Create the schema holder, which involves specifying connection parameters and<br />

pulling the schema from the data source.<br />

The following sections describe these steps in detail.<br />

Permission requirements<br />

When you use the <strong>Data</strong><strong>Server</strong> to create a schema image in a schema holder, it<br />

accesses the associated MS <strong>SQL</strong> <strong>Server</strong> database. This section describes the data<br />

source permissions required when you create, update, or connect to a schema image.<br />

Permissions <strong>for</strong> creating or updating a schema holder<br />

You must have privileges to use the SELECT statement on certain data source objects<br />

to per<strong>for</strong>m certain tasks. In this chapter, these privileges are referred to as SELECT<br />

privileges.<br />

<strong>OpenEdge</strong> <strong>Data</strong> <strong>Management</strong>: <strong>Data</strong><strong>Server</strong> <strong>for</strong> <strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong> 197

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!