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

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

Namespace Prefixes

PrefixIRI
n12https://www.openlinksw.com/about/id/entity/urn/howto:
n11http://data.openlinksw.com/oplweb/
n2http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuide#
n29http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep4#
n26http://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n28http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep7#
oplsofthttp://www.openlinksw.com/ontology/software#
n18https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:uda:howto:
n19http://data.openlinksw.com/oplweb/dbms_family/SQLServer#
n31http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep10#
wdrshttp://www.w3.org/2007/05/powder-s#
n10http://data.openlinksw.com/oplweb/opsys_family/MacOSX#
schemahttp://schema.org/
n22http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep3#
n24https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n30http://wikis.openlinksw.com/UdaWikiWeb/
n13https://www.openlinksw.com/about/id/entity/urn/data:openlink:
n16http://data.openlinksw.com/oplweb/uda/howto/MacOSXSampleAppUsageiODBCDemoUsageGuide#
n25http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep6#
n15https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n20http://data.openlinksw.com/oplweb/product_format/st#
n27https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:
n7http://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n5http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep9#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n21http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep2#
n8https://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n14http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep5#
xsdhhttp://www.w3.org/2001/XMLSchema#
n4http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep8#
n23http://data.openlinksw.com/oplweb/uda/howto/MacOSXLiteSQLServerDataSourceNameConfigurationGuideStep1#
n17https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/uda2.openlinksw.com/data/turtle/general/

Statements

Subject Item
n2:this
schema:description
Configuration of the Lite Edition (Single-Tier) ODBC Driver for Microsoft SQL Server Data Sources, for macOS Installation and Configuration of the Lite Edition (Single-Tier) ODBC Driver for Microsoft SQL Server Data Sources, for macOS
wdrs:describedby
n7:uda-howtos-seo.ttl n8:webs n12:island n13:products n13:websites n15:uda-howtos-qa.ttl n15:uda-howtos.ttl n17:UDAHowAndStepByGuides.ttl n18:seo n24:uda-howtos.ttl n26:offers n27:seo
schema:name
Configuration of the Lite Edition (Single-Tier) ODBC Driver for Microsoft SQL Server Data Sources, for macOS Installation and Configuration of the Lite Edition (Single-Tier) ODBC Driver for Microsoft SQL Server Data Sources, for macOS
oplsoft:hasDatabaseFamily
n11:SQLServer n19:this
oplsoft:hasOperatingSystemFamily
n10:this
schema:category
Data Source Name Configuration Guide
schema:relatedLink
n16:this n30:InstallSQLLiteOSX
schema:genre
n20:this
schema:text
<ol> <li>To configure an ODBC DSN, run the OpenLink iODBC Administrator located in the /Applications/iODBC folder:</li> <li>Click the <strong>System DSN</strong> tab:</li> <li>Click the <strong>Add</strong> button. Then, select the OpenLink SQL Server Lite Driver from the list of available drivers. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance:</li> <li>Click <strong>Finish</strong>.</li> <li>The <strong>Data Source</strong> tab prompts for a DSN name, description, and information that identifies the target Microsoft SQL Server DBMS:</li> <ul> <li><strong>DSN</strong> - (Required) A brief and meaningful title for your Data Source Name</li> <li><strong>Description</strong> - (Optional) A longer description for your Data Source Name</li> <li><strong>Server Name</strong> - (Required) Use the drop-down menu to invoke the driver's dynamic discovery of Microsoft SQL Server instances on the network and choose the desired instance.</li> <li>Use the "Advanced" button to manually configure a connection if the Microsoft SQL Server instance could not be dynamically located, as detailed below:</li> <li><strong>Server Type</strong> - An OpenLink proprietary parameter that associates the connection with a particular TDS version.</li> <li><strong>Hostname</strong> - The hostname or IP address on which Microsoft SQL Server listens. May include an instance name, as discussed below (e.g., "MySQLHost.example.com\MySQLInstance").</li> <li><strong>Port number</strong> - The TCP port on which Microsoft SQL Server listens. Leave blank when SQL Server TCP/IP port setting is "Dynamic."</li> <li><strong>Server Name</strong> - (Optional) Microsoft SQL Server instance name on the specified host. Usually not specified unless SQL Server TCP/IP port setting is "Dynamic." Though not optimal, a Microsoft SQL Server instance name can be specified by instead appending "\\InstanceName" to the Hostname field above (e.g., "MySQLHost.example.com\\MySQLInstance").</li> <li><strong>Mirror Host</strong> - The name of the Failover Server hosting the mirrored database if configured</li> <li><strong>Use strong encryption of data</strong> - The driver will demand an SSL encrypted connection to the Microsoft SQL Server instance. If the target instance is not configured for or capable of SSL connections, the connection will fail. This setting is not needed for connections to Microsoft SQL Server instances which are configured to demand SSL connections from clients; such demands are handled automatically by the driver. Note that SSL connections are never supported by Microsoft SQL Server 7 or earlier, nor when using TDS Version 7.0 or 4.2.</li> <li><strong>Use MARS</strong> - Multiple Active Result Sets enables the concurrent processing of multiple statements/queries and/or result sets on a single connection.</li> <li><strong>Verify Server Certificate</strong> - Verify the SSL Certificate presented by the database server against the one specified in the "CA file" field</li> <li><strong>CA file</strong> - Specify the location of a Valid SSL Certificate for use during the connection</li> </ul> <li>After selecting your preferences, click <strong>OK</strong> to continue.</li> <li>The <strong>Connection</strong> Tab takes a combination of required and optional parameters required to make a connection to the target database:</li> <ul> <li><strong>User name</strong> - A valid Microsoft SQL Server username. Windows Authentication may be triggered by using the DOMAIN\username syntax.</li> <li><strong>Choose a database, charset, language to use with the data source</strong></li> <li><strong>Password</strong> - A valid Microsoft SQL Server (or Windows Authentication) password</li> <li><strong>Database</strong> - The Microsoft SQL Server catalog/schema you want to work with</li> <li><strong>Language</strong> - The language for SQL Server error messages</li> <li><strong>Character set</strong> - The character set (a/k/a codepage) required by your ODBC client application. For most users, the default is best. The driver will automatically translate between this codepage and whatever the SQL Server is using.</li> <li><strong>Disable character set translation</strong> - All character IDs will be passed directly from ODBC client application to SQL Server, with no translation. This is rarely desirable and is provided to address historic issues.</li> <li>Click <strong>Continue</strong>.</li> <li>The <strong>Options</strong> tab enables you to set some standard and Microsoft SQL Server specific parameters:</li> <ul> <li><strong>Row Buffer Size</strong> - This attribute specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.</li> <li><strong>Hide Login Dialog</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>Read Only connection</strong> - Specifies whether the connection is "Read-only." Make sure the checkbox is unchecked to request a "Read/Write" connection.</li> <li><strong>TDS packet size</strong> - A value that determines the number of bytes per network packet transferred from the database server to the client. The correct setting of this attribute can improve performance. When set to 0, the initial default, the driver uses the default packet size as specified in the Sybase server configuration. When set to -1, the driver computes the maximum allowable packet size on the first connect to the data source and saves the value in the system information. When set to x, an integer from 1 to 10, which indicates a multiple of 512 bytes (for example, Packet Size of 6 means to set the packet size to 6 * 512 equal 3072 bytes). For you to take advantage of this connection attribute, you must configure the System 10 server for a maximum network packet size greater than or equal to the value you specified for Packet Size.</li> <li><strong>Prepare Method</strong> - This option is specific to the TDS Driver for Sybase and Microsoft SQL Server. It can take the values None, Partial, or Full (connectoptions -O [0, 1, 2] respectively). It is used to determine whether stored procedures are created on the server for calls to SQLPrepare().</li> <li><strong>No Quoted Identifiers</strong> - This option 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. Sybase connectivity is not affected.</li> <li><strong>Map Serializable to Snapshot isolation level</strong> - Enable Snapshot transaction isolation level in the driver. Snapshot Isolation is a new transaction isolation level first available in Microsoft SQL Server 2005.</li> <li><strong>SQL_DBMS Name</strong> - Manuallyoverrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath for which the return value should be "SQL Server".</li> <li>Click <strong>Continue</strong> to view additional preferences that can be set for the connection.</li> <li>The <strong>Initialization SQL</strong> field lets you specify a file containing SQL statements that will be run automatically against the database upon connection.</li> <li><strong>Cursor Sensitivity</strong> - 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><strong>Max Rows Override</strong> - Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit.</li> <li><strong>Enable Microsoft Jet Engine options</strong></li> <li><strong>Disable autocommit</strong> - Changes the default commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).</li> <li><strong>Disable rowset size limit</strong> - Removes OpenLink's default 100 rowset restriction.</li> <li><strong>Defer fetching of long data</strong> - Defers fetching of LONG (BINARY, BLOB, etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in the query do not include LONG data fields.</li> <li><strong>Multiple Active Statements Emulation</strong></li> <li><strong>Always include VIEWS in table list</strong> - This switch is needed for Microsoft Excel and Query, Stata, and some other tools that explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see VIEWS in the graphical query builder. This option is redundant when Always include all types is ticked.</li> <li><strong>Always include all types in table list</strong> - This switch is needed for Microsoft Excel and Query, Stata, and some other tools that explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see SYSTEM TABLEs, VIEWS, SYSTEM VIEWS, SYNONYMs, GLOBAL TEMPORARYs, ALIASes, and/or LOCAL TEMPORARYs in the graphical query builder. Note: the TABLE list will be much longer thanwhen this box is not ticked, and SYSTEM objects will be sorted to the top of the list due to typical naming conventions.</li> <li>When finished, click the <strong>Finish</strong> button to save your new Data Source Name.</li> </ol> <ol> <li>To configure an ODBC DSN, run the OpenLink iODBC Administrator located in the /Applications/iODBC folder:</li> <li>Click the <strong>System DSN</strong> tab:</li> <li>Click the <strong>Add</strong> button. Then, select the OpenLink SQL Server Lite Driver from the list of available drivers. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance:</li> <li>Click <strong>Finish</strong>.</li> <li>The <strong>Data Source</strong> tab prompts for a DSN name, description, and information that identifies the target Microsoft SQL Server DBMS:</li> <ul> <li><strong>DSN</strong> - (Required) A brief and meaningful title for your Data Source Name</li> <li><strong>Description</strong> - (Optional) A longer description for your Data Source Name</li> <li><strong>Server Name</strong> - (Required) Use the drop-down menu to invoke the driver's dynamic discovery of Microsoft SQL Server instances on the network and choose the desired instance.</li> <li>Use the "Advanced" button to manually configure a connection if the Microsoft SQL Server instance could not be dynamically located, as detailed below:</li> <li><strong>Server Type</strong> - An OpenLink proprietary parameter that associates the connection with a particular TDS version.</li> <li><strong>Hostname</strong> - The hostname or IP address on which Microsoft SQL Server listens. May include an instance name, as discussed below (e.g., "MySQLHost.example.com\MySQLInstance").</li> <li><strong>Port number</strong> - The TCP port on which Microsoft SQL Server listens. Leave blank when SQL Server TCP/IP port setting is "Dynamic."</li> <li><strong>Server Name</strong> - (Optional) Microsoft SQL Server instance name on the specified host. Usually not specified unless SQL Server TCP/IP port setting is "Dynamic." Though not optimal, a Microsoft SQL Server instance name can be specified by instead appending "\\InstanceName" to the Hostname field above (e.g., "MySQLHost.example.com\\MySQLInstance").</li> <li><strong>Mirror Host</strong> - The name of the Failover Server hosting the mirrored database if configured</li> <li><strong>Use strong encryption of data</strong> - The driver will demand an SSL encrypted connection to the Microsoft SQL Server instance. If the target instance is not configured for or capable of SSL connections, the connection will fail. This setting is not needed for connections to Microsoft SQL Server instances which are configured to demand SSL connections from clients; such demands are handled automatically by the driver. Note that SSL connections are never supported by Microsoft SQL Server 7 or earlier, nor when using TDS Version 7.0 or 4.2.</li> <li><strong>Use MARS</strong> - Multiple Active Result Sets enables the concurrent processing of multiple statements/queries and/or result sets on a single connection.</li> <li><strong>Verify Server Certificate</strong> - Verify the SSL Certificate presented by the database server against the one specified in the "CA file" field</li> <li><strong>CA file</strong> - Specify the location of a Valid SSL Certificate for use during the connection</li> </ul> <li>After selecting your preferences, click <strong>OK</strong> to continue.</li> <li>The <strong>Connection</strong> Tab takes a combination of required and optional parameters required to make a connection to the target database:</li> <ul> <li><strong>User name</strong> - A valid Microsoft SQL Server username. Windows Authentication may be triggered by using the DOMAIN\username syntax.</li> <li><strong>Choose a database, charset, language to use with the data source</strong></li> <li><strong>Password</strong> - A valid Microsoft SQL Server (or Windows Authentication) password</li> <li><strong>Database</strong> - The Microsoft SQL Server catalog/schema you want to work with</li> <li><strong>Language</strong> - The language for SQL Server error messages</li> <li><strong>Character set</strong> - The character set (a/k/a codepage) required by your ODBC client application. For most users, the default is best. The driver will automatically translate between this codepage and whatever the SQL Server is using.</li> <li><strong>Disable character set translation</strong> - All character IDs will be passed directly from ODBC client application to SQL Server, with no translation. This is rarely desirable and is provided to address historic issues.</li> <li>Click <strong>Continue</strong>.</li> <li>The <strong>Options</strong> tab enables you to set some standard and Microsoft SQL Server specific parameters:</li> <ul> <li><strong>Row Buffer Size</strong> - This attribute specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.</li> <li><strong>Hide Login Dialog</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>Read Only connection</strong> - Specifies whether the connection is "Read-only." Make sure the checkbox is unchecked to request a "Read/Write" connection.</li> <li><strong>TDS packet size</strong> - A value that determines the number of bytes per network packet transferred from the database server to the client. The correct setting of this attribute can improve performance. When set to 0, the initial default, the driver uses the default packet size as specified in the Sybase server configuration. When set to -1, the driver computes the maximum allowable packet size on the first connect to the data source and saves the value in the system information. When set to x, an integer from 1 to 10, which indicates a multiple of 512 bytes (for example, Packet Size of 6 means to set the packet size to 6 * 512 equal 3072 bytes). For you to take advantage of this connection attribute, you must configure the System 10 server for a maximum network packet size greater than or equal to the value you specified for Packet Size.</li> <li><strong>Prepare Method</strong> - This option is specific to the TDS Driver for Sybase and Microsoft SQL Server. It can take the values None, Partial, or Full (connectoptions -O [0, 1, 2] respectively). It is used to determine whether stored procedures are created on the server for calls to SQLPrepare().</li> <li><strong>No Quoted Identifiers</strong> - This option 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. Sybase connectivity is not affected.</li> <li><strong>Map Serializable to Snapshot isolation level</strong> - Enable Snapshot transaction isolation level in the driver. Snapshot Isolation is a new transaction isolation level first available in Microsoft SQL Server 2005.</li> <li><strong>SQL_DBMS Name</strong> - Manuallyoverrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath for which the return value should be "SQL Server".</li> <li>Click <strong>Continue</strong> to view additional preferences that can be set for the connection.</li> <li>The <strong>Initialization SQL</strong> field lets you specify a file containing SQL statements that will be run automatically against the database upon connection.</li> <li><strong>Cursor Sensitivity</strong> - 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><strong>Max Rows Override</strong> - Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit.</li> <li><strong>Enable Microsoft Jet Engine options</strong></li> <li><strong>Disable autocommit</strong> - Changes the default commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).</li> <li><strong>Disable rowset size limit</strong> - Removes OpenLink's default 100 rowset restriction.</li> <li><strong>Defer fetching of long data</strong> - Defers fetching of LONG (BINARY, BLOB, etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in the query do not include LONG data fields.</li> <li><strong>Multiple Active Statements Emulation</strong></li> <li><strong>Always include VIEWS in table list</strong> - This switch is needed for Microsoft Excel and Query, Stata, and some other tools that explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see VIEWS in the graphical query builder. This option is redundant when Always include all types is ticked.</li> <li><strong>Always include all types in table list</strong> - This switch is needed for Microsoft Excel and Query, Stata, and some other tools that explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see SYSTEM TABLEs, VIEWS, SYSTEM VIEWS, SYNONYMs, GLOBAL TEMPORARYs, ALIASes, and/or LOCAL TEMPORARYs in the graphical query builder. Note: the TABLE list will be much longer thanwhen this box is not ticked, and SYSTEM objects will be sorted to the top of the list due to typical naming conventions.</li> <li>When finished, click the <strong>Finish</strong> button to save your new Data Source Name.</li> </ol>
rdf:type
schema:HowTo
schema:step
n4:this n5:this n14:this n21:this n22:this n23:this n25:this n28:this n29:this n31:this