OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
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 />
Index–8<br />
Registering<br />
data sources 5–4<br />
RELEASE statement 2–35<br />
Remote databases<br />
starting a <strong>Data</strong><strong>Server</strong> broker B–11<br />
Remote <strong>Data</strong><strong>Server</strong> 1–12<br />
starting 6–3<br />
Requirements<br />
software 1–16<br />
result 3–3<br />
Result set<br />
definition 3–3<br />
Retrieving output parameter values 3–16<br />
Retrieving result sets using proc-text-buffer<br />
3–16<br />
Retrieving return codes 3–15<br />
Roll back<br />
on data sources 2–43<br />
ROWID characteristics 3–32<br />
ROWID function 2–52<br />
defining supporting index 7–35<br />
listing objects not supported 5–21, 7–10<br />
manually creating support 7–37<br />
reposition functions, INTEGER data<br />
type, and INT64 data type 2–53<br />
supporting in data source 7–37<br />
ROWID support 3–32<br />
additional Pro<strong>Data</strong>Set support 3–36<br />
ROWID characteristics 3–32<br />
using ROWID with RUN<br />
STORED-PROCEDURE and<br />
LOAD-RESULT-INTO 3–32<br />
Rows<br />
troubleshooting large rows 8–8<br />
RUN STORED-PROCEDURE statement<br />
complete syntax reference 3–6<br />
description 3–3<br />
retrieving parameter values 3–16<br />
send-sql-statement option<br />
with LOAD-RESULT-INTO option<br />
3–12<br />
without LOAD-RESULT-INTO<br />
option 3–11<br />
using the send-sql statement option 3–11<br />
with LOAD-RESULT-INTO phrase<br />
3–11<br />
with LOAD-RESULT-INTO phrase<br />
syntax 3–11<br />
without LOAD-RESULT-INTO phrase<br />
syntax 3–10<br />
Run Stored-Procedure statement<br />
details 3–7<br />
handling errors 3–30<br />
without LOAD-RESULT-INTO phrase<br />
3–10<br />
S<br />
-S shutdown parameter<br />
PROSHUT command B–12<br />
SAVE CACHE COMPLETE statement<br />
6–11, 6–27, D–2<br />
Schema<br />
defined 1–6<br />
loading process 1–6<br />
Schema caching<br />
defined 1–6<br />
Schema holder<br />
be<strong>for</strong>e you begin 5–15<br />
defined 1–6<br />
Schema holders 1–3, 1–6<br />
changing logical name 7–17<br />
connecting 6–9<br />
connection failure 6–28<br />
connection permissions 5–16<br />
creating 5–15<br />
deleting 7–19<br />
maintaining 5–22, 7–3<br />
modifying 7–32<br />
setting code page 5–18, 7–8<br />
system administration permissions 7–7<br />
updating 5–22, 7–11<br />
verifying 7–13<br />
where best to build 5–15<br />
Schema images<br />
security 5–15<br />
Scrolling<br />
backward 2–48<br />
<strong>for</strong>ward 2–48<br />
Security<br />
guideline considerations 1–7<br />
send-sql-statement option<br />
RUN-STORED-PROCEDURE<br />
statement 3–11<br />
Sequence generator 2–15<br />
defined 2–15<br />
<strong>Server</strong> Join (-nojoinbysqldb) startup<br />
parameter 4–10, 4–14, 6–18
Change language