HTML Microdata document

This HTML5 document contains 40 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

Prefix	IRI
n21	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep4#
n29	https://www.openlinksw.com/about/id/entity/urn/howto:
n16	http://data.openlinksw.com/oplweb/
n17	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep6#
n28	http://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n30	http://data.openlinksw.com/oplweb/uda/howto/WindowsSampleAppUsageC++DemoUsageGuide#
wdrs	http://www.w3.org/2007/05/powder-s#
n8	https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:uda:howto:
n25	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep1#
oplsoft	http://www.openlinksw.com/ontology/software#
n13	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep8#
schema	http://schema.org/
n27	https://www.openlinksw.com/about/id/entity/urn/data:openlink:
n31	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n2	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuide#
n24	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep3#
n4	https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers/
n12	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep10#
n26	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n14	http://data.openlinksw.com/oplweb/opsys_family/Windows#
n18	http://data.openlinksw.com/oplweb/product_format/st#
n20	http://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n22	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep5#
n11	https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
n6	http://data.openlinksw.com/oplweb/dbms_family/ODBC#
n19	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep7#
n9	https://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n23	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep2#
xsdh	http://www.w3.org/2001/XMLSchema#
n15	http://data.openlinksw.com/oplweb/uda/howto/WindowsLiteODBCDataSourceNameConfigurationGuideStep9#
n10	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/uda2.openlinksw.com/data/turtle/general/

Statements

Subject Item: n2:this
schema:description: JDBC to ODBC Bridge Driver Data Source Name (DSN) Configuration for Windows Lite Edition (Single-Tier) JDBC Driver for ODBC Data Sources (JDBC to ODBC Bridge Driver) Data Source Name (DSN) Configuration for Windows Lite Edition (Single-Tier) JDBC to ODBC Bridge Driver Data Source Name (DSN) Configuration for Windows
wdrs:describedby: n8:seo n9:webs n10:UDAHowAndStepByGuides.ttl n11:seo n20:uda-howtos-seo.ttl n26:uda-howtos-qa.ttl n27:websites n26:uda-howtos.ttl n27:products n28:offers n29:island n31:uda-howtos.ttl
schema:name: JDBC to ODBC Bridge Driver Data Source Name (DSN) Configuration for Windows Lite Edition (Single-Tier) JDBC Driver for ODBC Data Sources (JDBC to ODBC Bridge Driver) Data Source Name (DSN) Configuration for Windows Lite Edition (Single-Tier) JDBC to ODBC Bridge Driver Data Source Name (DSN) Configuration for Windows
oplsoft:hasDatabaseFamily: n6:this n16:ODBC
oplsoft:hasOperatingSystemFamily: n14:this
schema:category: Data Source Name Configuration Guide
schema:relatedLink: n4:jodbc-lite-install-5d5e42ceecda n30:this
schema:genre: n18:this
schema:text: <ol> <li> The fourth dialog enables you to set optional ODBC connection parameters. <ul> <li> Read-only connection — Specifies whether the connection is "Read-only." Must be unchecked to INSERT, UPDATE, or DELETE records, and to run some Stored Procedures including some built-in functions. </li> <li> Defer fetching of long data — Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in query do not include LONG data fields. </li> <li> Disable interactive login — Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application. </li> <li> Row Buffer Size — This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999. </li> <li> Max Rows Override — Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit. </li> <li> Initial SQL — Lets you specify a file containing SQL statements that will be run automatically against the database upon connection. </li> <li> Dynamic Cursor Sensitivity — Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the High Cursor Sensitivity checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. </li> <li> Enable logging to the log file — Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information. </li> </ul> </li> <li> Click Next to continue. Start a JDBC-compliant application e.g., the JDBC Demo Application bundled with the OpenLink JDBC-ODBC Bridge Driver Installer Using the following JDBC URL template: <pre> jdbc:openlink://ODBC[/DSN=dsn][/UID=uid][/PWD=pwd][/READONLY=x] </pre> Construct a JDBC URL comprising the following connection attribute name and values pairings: <ul> <li> /DSN = Data Source Name (DSN) used to successfully connect to your target database in the prior step </li> <li> /UID = database username </li> <li> /PWD = password </li> <li> /READONLY = Y or N, subject to your preferred Read or Write session mode </li> </ul> </li> </ol> <ol> <li> The fourth dialog enables you to set optional ODBC connection parameters. <ul> <li> Read-only connection â Specifies whether the connection is "Read-only." Must be unchecked to INSERT, UPDATE, or DELETE records, and to run some Stored Procedures including some built-in functions. </li> <li> Defer fetching of long data â Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in query do not include LONG data fields. </li> <li> Disable interactive login â Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application. </li> <li> Row Buffer Size â This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999. </li> <li> Max Rows Override â Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit. </li> <li> Initial SQL â Lets you specify a file containing SQL statements that will be run automatically against the database upon connection. </li> <li> Dynamic Cursor Sensitivity â Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the High Cursor Sensitivity checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. </li> <li> Enable logging to the log file â Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information. </li> </ul> </li> <li> Click Next to continue. Start a JDBC-compliant application e.g., the JDBC Demo Application bundled with the OpenLink JDBC-ODBC Bridge Driver Installer Using the following JDBC URL template: <pre> jdbc:openlink://ODBC[/DSN=dsn][/UID=uid][/PWD=pwd][/READONLY=x] </pre> Construct a JDBC URL comprising the following connection attribute name and values pairings: <ul> <li> /DSN = Data Source Name (DSN) used to successfully connect to your target database in the prior step </li> <li> /UID = database username </li> <li> /PWD = password </li> <li> /READONLY = Y or N, subject to your preferred Read or Write session mode </li> </ul> </li> </ol> <ol> <li> The fourth dialog enables you to set optional ODBC connection parameters. <ul> <li> Read-only connection — Specifies whether the connection is "Read-only." Must be unchecked to INSERT, UPDATE, or DELETE records, and to run some Stored Procedures including some built-in functions. </li> <li> Defer fetching of long data — Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in query do not include LONG data fields. </li> <li> Disable interactive login — Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application. </li> <li> Row Buffer Size — This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999. </li> <li> Max Rows Override — Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit. </li> <li> Initial SQL — Lets you specify a file containing SQL statements that will be run automatically against the database upon connection. </li> <li> Dynamic Cursor Sensitivity — Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the High Cursor Sensitivity checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. </li> <li> Enable logging to the log file — Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information. </li> </ul> </li> <li> Click Next to continue. Start a JDBC-compliant application e.g., the JDBC Demo Application bundled with the OpenLink JDBC-ODBC Bridge Driver Installer Using the following JDBC URL template: <pre> jdbc:openlink://ODBC[/DSN=dsn][/UID=uid][/PWD=pwd][/READONLY=x] </pre> Construct a JDBC URL comprising the following connection attribute name and values pairings: <ul> <li> /DSN = Data Source Name (DSN) used to successfully connect to your target database in the prior step </li> <li> /UID = database username </li> <li> /PWD = password </li> <li> /READONLY = Y or N, subject to your preferred Read or Write session mode </li> </ul> </li> </ol> <ol> <li> The fourth dialog enables you to set optional ODBC connection parameters. <ul> <li> Read-only connection â Specifies whether the connection is "Read-only." Must be unchecked to INSERT, UPDATE, or DELETE records, and to run some Stored Procedures including some built-in functions. </li> <li> Defer fetching of long data â Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in query do not include LONG data fields. </li> <li> Disable interactive login â Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application. </li> <li> Row Buffer Size â This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999. </li> <li> Max Rows Override â Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit. </li> <li> Initial SQL â Lets you specify a file containing SQL statements that will be run automatically against the database upon connection. </li> <li> Dynamic Cursor Sensitivity â Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the High Cursor Sensitivity checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. </li> <li> Enable logging to the log file â Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information. </li> </ul> </li> <li> Click Next to continue. Start a JDBC-compliant application e.g., the JDBC Demo Application bundled with the OpenLink JDBC-ODBC Bridge Driver Installer Using the following JDBC URL template: <pre> jdbc:openlink://ODBC[/DSN=dsn][/UID=uid][/PWD=pwd][/READONLY=x] </pre> Construct a JDBC URL comprising the following connection attribute name and values pairings: <ul> <li> /DSN = Data Source Name (DSN) used to successfully connect to your target database in the prior step </li> <li> /UID = database username </li> <li> /PWD = password </li> <li> /READONLY = Y or N, subject to your preferred Read or Write session mode </li> </ul> </li> </ol>
rdf:type: schema:HowTo
schema:step: n12:this n13:this n15:this n17:this n19:this n21:this n22:this n23:this n24:this n25:this