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

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

Namespace Prefixes

PrefixIRI
n13http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep10#
n28http://data.openlinksw.com/oplweb/
n8https://www.openlinksw.com/about/id/entity/urn/howto:
n22http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep5#
n29http://data.openlinksw.com/oplweb/dbms_family/PostgreSQL#
n21http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep4#
n31http://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n17http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep9#
n10http://data.openlinksw.com/oplweb/uda/howto/WindowsSampleAppUsageC++DemoUsageGuide#
n4https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:uda:howto:
oplsofthttp://www.openlinksw.com/ontology/software#
wdrshttp://www.w3.org/2007/05/powder-s#
schemahttp://schema.org/
n23http://wikis.openlinksw.com/UdaWikiWeb/
n30https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n18https://www.openlinksw.com/about/id/entity/urn/data:openlink:
n26http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep3#
n16http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep8#
n12https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n6http://data.openlinksw.com/oplweb/product_format/st#
n7https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:
n15http://data.openlinksw.com/oplweb/opsys_family/Windows#
n24http://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n2http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuide#
n20http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep7#
n25http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep2#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n11https://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n27http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep1#
n19http://data.openlinksw.com/oplweb/uda/howto/WindowsLitePostgreSQLDataSourceNameConfigurationGuideStep6#
xsdhhttp://www.w3.org/2001/XMLSchema#
n9https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/uda2.openlinksw.com/data/turtle/general/

Statements

Subject Item
n2:this
schema:description
ODBC Driver for PostgreSQL Data Source Name (DSN) Configuration for Windows Lite Edition (Single-Tier) ODBC Driver for PostgreSQL Data Source Name (DSN) Configuration for Windows
wdrs:describedby
n4:seo n7:seo n8:island n9:UDAHowAndStepByGuides.ttl n11:webs n12:uda-howtos.ttl n18:products n12:uda-howtos-qa.ttl n24:uda-howtos-seo.ttl n18:websites n30:uda-howtos.ttl n31:offers
schema:name
ODBC Driver for PostgreSQL Data Source Name (DSN) Configuration for Windows Lite Edition (Single-Tier) ODBC Driver for PostgreSQL Data Source Name (DSN) Configuration for Windows
oplsoft:hasDatabaseFamily
n28:PostgreSQL n29:this
oplsoft:hasOperatingSystemFamily
n15:this
schema:category
Data Source Name Configuration Guide
schema:relatedLink
n10:this n23:InstallPostgreSQLLiteWin33
schema:genre
n6:this
schema:text
<ol> <li>Open the "ODBC Data Sources" application.</li> <li>Configure 64-bit drivers using the 64-bit application. Configure 32-bit drivers using the 32-bit application.</li> <li>Select the System DSN tab, then click Add.</li> <li>Select the OpenLink "Lite" Driver for JDBC Data Sources from the list of available drivers. Choose the Unicode version of the driver if you are working with multi-byte character sets to avoid unnecessary translations that can impact ODBC performance.</li> <li>Click Finish.</li> <li>The first dialog prompts for a Data Source Name and an optional description. Click Next.</li> <li>The second dialog prompts for information that identifies the PostgreSQL database server and the listening port. It also provides a checkbox to verify basic connection parameters before setting advanced and optional settings. <ol> <li><strong>Host name:</strong> The hostname or IP address of the server where PostgreSQL runs.</li> <li><strong>Port:</strong> The TCP port on which PostgreSQL listens.</li> <li><strong>Database:</strong> The PostgreSQL database.</li> <li><strong>No Transactions:</strong> Enable this option to automatically commit all transactions, which helps prevent memory errors for large transactions. For example, when exporting 10,000 records from Microsoft Access.</li> <li><strong>Connect now to verify that all settings are correct:</strong> The connection will be attempted once you click Continue.</li> <li><strong>Login ID:</strong> A PostgreSQL username.</li> <li><strong>Password:</strong> A valid PostgreSQL database password.</li> </ol> </li> <li>Click Next.</li> <li>The third dialog allows you to set PostgreSQL-specific parameters. <ul> <li><strong>Enable HSODBC (Oracle Heterogeneous Services) fix:</strong> Check this box if you plan to query PostgreSQL through Oracle HSODBC.</li> </ul> </li> <li>Click Next.</li> <li>The fourth dialog combines database-specific and optional parameters. <ul> <li><strong>Database:</strong> The Microsoft SQL Server database.</li> <li><strong>Character set:</strong> The client application's character set (8-bit only; the Unicode driver always returns UCS-2 on Windows).</li> <li><strong>Language:</strong> The language in which you want error messages to be returned. It must be supported by the target server.</li> <li><strong>Packet Size:</strong> Specifies the number of bytes per network packet transferred from the database server to the client. Adjusting this value can improve performance. Use 0 for the default packet size specified in the Microsoft SQL Server configuration, -1 to compute the maximum allowable packet size, or an integer from 1 to 10 as a multiple of 512 bytes (e.g., Packet Size of 6 sets the packet size to 6 * 512 = 3072 bytes).</li> <li><strong>Prepare Method:</strong> This option is specific to the TDS-based driver for Sybase & Microsoft SQL Server SQL Servers. It determines whether stored procedures are created on the server for SQLPrepare calls.</li> <li><strong>No Quoted Identifiers:</strong> Indicates that the underlying driver does not support quoted identifiers, which is required for Jet engine-based products like MS Access.</li> <li><strong>Use ANSI nulls, padding, and warnings:</strong> This option affects TDS agent & Lite Driver connections to Microsoft SQL Server databases. It does not affect Sybase connectivity.</li> <li><strong>Map Serializable to Snapshot isolation level:</strong> Enable Snapshot transaction isolation level in the driver.</li> </ul> </li> <li>Click Next to continue.</li> <li>The fifth dialog allows you to set optional ODBC connection parameters. <ul> <li><strong>Read-only connection:</strong> Specifies whether the connection is read-only. Uncheck this option to perform INSERT, UPDATE, or DELETE operations.</li> <li><strong>Defer fetching of long data:</strong> Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries, improving performance when the query does not include LONG data fields.</li> <li><strong>Disable interactive login:</strong> Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC-compliant application.</li> <li><strong>Row Buffer Size:</strong> Specifies the number of records to be delivered from the driver to the client application in a single batch (values range from 1 to 999).</li> <li><strong>Max Rows Override:</strong> 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><strong>Initial SQL:</strong> Lets you specify a file containing SQL statements to be automatically executed against the database upon connection.</li> <li><strong>Dynamic Cursor Sensitivity:</strong> Enables or disables the row version cache used with dynamic cursors.</li> <li><strong>Enable logging to the log file:</strong> Check this option and provide the full path to a file to log diagnostic information.</li> </ul> </li> <li>Click Next to continue.</li> <li>The sixth dialog enables you to set additional parameters to enhance compatibility with applications. <ul> <li><strong>Enable Microsoft Jet engine options:</strong> Facilitates translation of certain data types for the Microsoft Jet Engine.</li> <li><strong>Disable Autocommit:</strong> Changes the commit behavior of the OpenLink driver.</li> <li><strong>Disable rowset size limit:</strong> Disables a limitation enforced by the cursor library to prevent excessive memory usage with large result sets.</li> <li><strong>Multiple Active Statements Emulation:</strong> Enables the use of Multiple Active Statements in an ODBC application even if the underlying database does not support it.</li> <li><strong>SQL_DBMS Name:</strong> Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver.</li> </ul> </li> <li>Click Next to continue.</li> </ol> <ol> <li>Open the "ODBC Data Sources" application.</li> <li>Configure 64-bit drivers using the 64-bit application. Configure 32-bit drivers using the 32-bit application.</li> <li>Select the System DSN tab, then click Add.</li> <li>Select the OpenLink "Lite" Driver for PostgreSQL Data Sources from the list of available drivers. Choose the Unicode version of the driver if you are working with multi-byte character sets to avoid unnecessary translations that can impact ODBC performance.</li> <li>Click Finish.</li> <li>The first dialog prompts for a Data Source Name and an optional description. Click Next.</li> <li>The second dialog prompts for information that identifies the PostgreSQL database server and the listening port. It also provides a checkbox to verify basic connection parameters before setting advanced and optional settings. <ol> <li><strong>Host name:</strong> The hostname or IP address of the server where PostgreSQL runs.</li> <li><strong>Port:</strong> The TCP port on which PostgreSQL listens.</li> <li><strong>Database:</strong> The PostgreSQL database.</li> <li><strong>No Transactions:</strong> Enable this option to automatically commit all transactions, which helps prevent memory errors for large transactions. For example, when exporting 10,000 records from Microsoft Access.</li> <li><strong>Connect now to verify that all settings are correct:</strong> The connection will be attempted once you click Continue.</li> <li><strong>Login ID:</strong> A PostgreSQL username.</li> <li><strong>Password:</strong> A valid PostgreSQL database password.</li> </ol> </li> <li>Click Next.</li> <li>The third dialog allows you to set PostgreSQL-specific parameters. <ul> <li><strong>Enable HSODBC (Oracle Heterogeneous Services) fix:</strong> Check this box if you plan to query PostgreSQL through Oracle HSODBC.</li> </ul> </li> <li>Click Next.</li> <li>The fourth dialog combines database-specific and optional parameters. <ul> <li><strong>Database:</strong> The Microsoft SQL Server database.</li> <li><strong>Character set:</strong> The client application's character set (8-bit only; the Unicode driver always returns UCS-2 on Windows).</li> <li><strong>Language:</strong> The language in which you want error messages to be returned. It must be supported by the target server.</li> <li><strong>Packet Size:</strong> Specifies the number of bytes per network packet transferred from the database server to the client. Adjusting this value can improve performance. Use 0 for the default packet size specified in the Microsoft SQL Server configuration, -1 to compute the maximum allowable packet size, or an integer from 1 to 10 as a multiple of 512 bytes (e.g., Packet Size of 6 sets the packet size to 6 * 512 = 3072 bytes).</li> <li><strong>Prepare Method:</strong> This option is specific to the TDS-based driver for Sybase & Microsoft SQL Server SQL Servers. It determines whether stored procedures are created on the server for SQLPrepare calls.</li> <li><strong>No Quoted Identifiers:</strong> Indicates that the underlying driver does not support quoted identifiers, which is required for Jet engine-based products like MS Access.</li> <li><strong>Use ANSI nulls, padding, and warnings:</strong> This option affects TDS agent & Lite Driver connections to Microsoft SQL Server databases. It does not affect Sybase connectivity.</li> <li><strong>Map Serializable to Snapshot isolation level:</strong> Enable Snapshot transaction isolation level in the driver.</li> </ul> </li> <li>Click Next to continue.</li> <li>The fifth dialog allows you to set optional ODBC connection parameters. <ul> <li><strong>Read-only connection:</strong> Specifies whether the connection is read-only. Uncheck this option to perform INSERT, UPDATE, or DELETE operations.</li> <li><strong>Defer fetching of long data:</strong> Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries, improving performance when the query does not include LONG data fields.</li> <li><strong>Disable interactive login:</strong> Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC-compliant application.</li> <li><strong>Row Buffer Size:</strong> Specifies the number of records to be delivered from the driver to the client application in a single batch (values range from 1 to 999).</li> <li><strong>Max Rows Override:</strong> 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><strong>Initial SQL:</strong> Lets you specify a file containing SQL statements to be automatically executed against the database upon connection.</li> <li><strong>Dynamic Cursor Sensitivity:</strong> Enables or disables the row version cache used with dynamic cursors.</li> <li><strong>Enable logging to the log file:</strong> Check this option and provide the full path to a file to log diagnostic information.</li> </ul> </li> <li>Click Next to continue.</li> <li>The sixth dialog enables you to set additional parameters to enhance compatibility with applications. <ul> <li><strong>Enable Microsoft Jet engine options:</strong> Facilitates translation of certain data types for the Microsoft Jet Engine.</li> <li><strong>Disable Autocommit:</strong> Changes the commit behavior of the OpenLink driver.</li> <li><strong>Disable rowset size limit:</strong> Disables a limitation enforced by the cursor library to prevent excessive memory usage with large result sets.</li> <li><strong>Multiple Active Statements Emulation:</strong> Enables the use of Multiple Active Statements in an ODBC application even if the underlying database does not support it.</li> <li><strong>SQL_DBMS Name:</strong> Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver.</li> </ul> </li> <li>Click Next to continue.</li> </ol> <ol> <li>Open the "ODBC Data Sources" application.</li> <li>Configure 64-bit drivers using the 64-bit application. Configure 32-bit drivers using the 32-bit application.</li> <li>Select the System DSN tab, then click Add.</li> <li>Select the OpenLink "Lite" Driver for PostgreSQL Data Sources from the list of available drivers. Choose the Unicode version of the driver if you are working with multi-byte character sets to avoid unnecessary translations that can impact ODBC performance.</li> <li>Click Finish.</li> <li>The first dialog prompts for a Data Source Name and an optional description. Click Next.</li> <li>The second dialog prompts for information that identifies the PostgreSQL database server and the listening port. It also provides a checkbox to verify basic connection parameters before setting advanced and optional settings. <ol> <li><strong>Host name:</strong> The hostname or IP address of the server where PostgreSQL runs.</li> <li><strong>Port:</strong> The TCP port on which PostgreSQL listens.</li> <li><strong>Database:</strong> The PostgreSQL database.</li> <li><strong>No Transactions:</strong> Enable this option to automatically commit all transactions, which helps prevent memory errors for large transactions. For example, when exporting 10,000 records from Microsoft Access.</li> <li><strong>Connect now to verify that all settings are correct:</strong> The connection will be attempted once you click Continue.</li> <li><strong>Login ID:</strong> A PostgreSQL username.</li> <li><strong>Password:</strong> A valid PostgreSQL database password.</li> </ol> </li> <li>Click Next.</li> <li>The third dialog allows you to set PostgreSQL-specific parameters. <ul> <li><strong>Enable HSODBC (Oracle Heterogeneous Services) fix:</strong> Check this box if you plan to query PostgreSQL through Oracle HSODBC.</li> </ul> </li> <li>Click Next.</li> <li>The fourth dialog combines database-specific and optional parameters. <ul> <li><strong>Database:</strong> The Microsoft SQL Server database.</li> <li><strong>Character set:</strong> The client application's character set (8-bit only; the Unicode driver always returns UCS-2 on Windows).</li> <li><strong>Language:</strong> The language in which you want error messages to be returned. It must be supported by the target server.</li> <li><strong>Packet Size:</strong> Specifies the number of bytes per network packet transferred from the database server to the client. Adjusting this value can improve performance. Use 0 for the default packet size specified in the Microsoft SQL Server configuration, -1 to compute the maximum allowable packet size, or an integer from 1 to 10 as a multiple of 512 bytes (e.g., Packet Size of 6 sets the packet size to 6 * 512 = 3072 bytes).</li> <li><strong>Prepare Method:</strong> This option is specific to the TDS-based driver for Sybase & Microsoft SQL Server SQL Servers. It determines whether stored procedures are created on the server for SQLPrepare calls.</li> <li><strong>No Quoted Identifiers:</strong> Indicates that the underlying driver does not support quoted identifiers, which is required for Jet engine-based products like MS Access.</li> <li><strong>Use ANSI nulls, padding, and warnings:</strong> This option affects TDS agent & Lite Driver connections to Microsoft SQL Server databases. It does not affect Sybase connectivity.</li> <li><strong>Map Serializable to Snapshot isolation level:</strong> Enable Snapshot transaction isolation level in the driver.</li> </ul> </li> <li>Click Next to continue.</li> <li>The fifth dialog allows you to set optional ODBC connection parameters. <ul> <li><strong>Read-only connection:</strong> Specifies whether the connection is read-only. Uncheck this option to perform INSERT, UPDATE, or DELETE operations.</li> <li><strong>Defer fetching of long data:</strong> Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries, improving performance when the query does not include LONG data fields.</li> <li><strong>Disable interactive login:</strong> Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC-compliant application.</li> <li><strong>Row Buffer Size:</strong> Specifies the number of records to be delivered from the driver to the client application in a single batch (values range from 1 to 999).</li> <li><strong>Max Rows Override:</strong> 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><strong>Initial SQL:</strong> Lets you specify a file containing SQL statements to be automatically executed against the database upon connection.</li> <li><strong>Dynamic Cursor Sensitivity:</strong> Enables or disables the row version cache used with dynamic cursors.</li> <li><strong>Enable logging to the log file:</strong> Check this option and provide the full path to a file to log diagnostic information.</li> </ul> </li> <li>Click Next to continue.</li> <li>The sixth dialog enables you to set additional parameters to enhance compatibility with applications. <ul> <li><strong>Enable Microsoft Jet engine options:</strong> Facilitates translation of certain data types for the Microsoft Jet Engine.</li> <li><strong>Disable Autocommit:</strong> Changes the commit behavior of the OpenLink driver.</li> <li><strong>Disable rowset size limit:</strong> Disables a limitation enforced by the cursor library to prevent excessive memory usage with large result sets.</li> <li><strong>Multiple Active Statements Emulation:</strong> Enables the use of Multiple Active Statements in an ODBC application even if the underlying database does not support it.</li> <li><strong>SQL_DBMS Name:</strong> Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver.</li> </ul> </li> <li>Click Next to continue.</li> </ol>
rdf:type
schema:HowTo
schema:step
n13:this n16:this n17:this n19:this n20:this n21:this n22:this n25:this n26:this n27:this