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.

Index<br />

complete syntax reference 124<br />

description 121, 127<br />

retrieving parameter values 135<br />

Code pages 59<br />

changing in a schema holder 275<br />

collation table 61<br />

conversion table 61<br />

setting in schema holder 201, 264<br />

COMPILE statement 115<br />

Configuration examples<br />

local <strong>Data</strong><strong>Server</strong> 222<br />

remote <strong>Data</strong><strong>Server</strong> 223<br />

CONNECT statement<br />

failure response 243<br />

NO-ERROR option 243<br />

Connecting schema holders 218<br />

at startup 219<br />

Connection BINDING Options 227<br />

Connection pool<br />

defined 160<br />

Connection pooling 160<br />

considerations 161<br />

disabling 162<br />

enabling 162<br />

impact on commits 163<br />

ODBC 161<br />

Connection to data source<br />

blank space in data source name 225<br />

<strong>Data</strong><strong>Server</strong> opens multiple<br />

connections 244<br />

failure response due to existing<br />

connection 243<br />

failure response due to logical name<br />

243<br />

failures with <strong>SQL</strong> <strong>Server</strong> 243<br />

guidelines 217<br />

interactive connection 225<br />

non-standard connections 225<br />

security on NT 217<br />

troubleshooting 244, 325<br />

Connection-string<br />

defined 224<br />

Connects log entry type 235<br />

CONTAINS operator 117<br />

COUNT-OF function 117<br />

CREATE statement 91, 117<br />

Creating a temp-table layout plan 144<br />

dynamic temp-table in an prepared<br />

state 146<br />

dynamic temp-table in an unprepared<br />

state 145<br />

options 145<br />

Creating <strong>OpenEdge</strong> databases 199<br />

Cursor<br />

defined 105<br />

Cursor log entry type 235<br />

Cursors 105<br />

cursor downgrades 166<br />

monitoring cursor and connection use<br />

164<br />

multiple 244<br />

statement cache 166<br />

362 <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><br />

D<br />

<strong>Data</strong> Dictionary<br />

changing data types 309<br />

connection failure response 243<br />

modifying schema holders 307<br />

<strong>Data</strong> output and retrieval options<br />

results retrieved from a database 132<br />

defining a special view on the MSS<br />

data source 132<br />

<strong>OpenEdge</strong>-supplied<br />

proc-text-buffer 132<br />

return codes 132<br />

values of output parameters you<br />

define when creating a procedure<br />

132<br />

data source<br />

defined 57<br />

<strong>Data</strong> sources 37<br />

adding objects to schema holder 203,<br />

267<br />

code page 201, 264<br />

data types 71<br />

database objects 57<br />

keys 65<br />

locking behavior 93<br />

logical name 200, 264<br />

login name 117, 198<br />

naming conventions 58<br />

null value 89<br />

password 117, 198<br />

permissions 197<br />

physical name 201, 265<br />

registering 184<br />

security levels 42<br />

triggers 69<br />

views 68<br />

zero-length character strings 89<br />

<strong>Data</strong> types 71, 353<br />

changing 309<br />

conversion details 354

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

Saved successfully!

Ooh no, something went wrong!