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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 5: Configuring the <strong>Data</strong><strong>Server</strong><br />

5. Choose OK. The following dialog box appears. By default, the name of the newly<br />

created data source appears in the Physical Name field, as shown:<br />

You do not have to provide any additional connection in<strong>for</strong>mation. You can add<br />

connection parameters when you create the data source or edit connection<br />

in<strong>for</strong>mation later. See the online help <strong>for</strong> a complete description of the Connect<br />

<strong>Data</strong>base dialog box.<br />

6. Choose OK to connect the empty <strong>OpenEdge</strong> database and return to the <strong>Data</strong><br />

Administration main window.<br />

Creating a schema holder<br />

This section addresses the steps needed to create a schema holder.<br />

To create the schema holder:<br />

1. From the <strong>Data</strong> Administration main menu, select <strong>Data</strong><strong>Server</strong>→ MS <strong>SQL</strong> <strong>Server</strong><br />

Utilities→ Create <strong>Data</strong><strong>Server</strong> Schema. The following dialog box appears:<br />

2. In the Logical <strong>Data</strong>base Name field, type the name that you will use to connect<br />

to your data source and refer to it in your programming applications. This name<br />

must be different from the schema holder name. For more in<strong>for</strong>mation on<br />

database names, see the database access chapter in <strong>OpenEdge</strong> Getting Started:<br />

ABL Essentials.<br />

Note: If you place the schema from a second MS <strong>SQL</strong> <strong>Server</strong> database into a<br />

schema holder, the second schema must have a different logical database<br />

name from the first schema. The schema holder has one physical name,<br />

but each schema that it contains must have a different logical name.<br />

200 <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>

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

Saved successfully!

Ooh no, something went wrong!