Connection preferences specify the way certain aspects of the Interactive Reporting database connection file are managed. The preferences are saved with an Interactive Reporting database connection file and are applied each time you use the connection.
For example, use connection preferences to filter extraneous tables from the Table Catalog or change the way the connection software handles SQL transaction statements.
Connection preferences differ depending on the Interactive Reporting Studio edition, connection API, and DBMS.
Connection preferences are accessed by selecting the Show Advanced Options check box in the Database Connection Wizard. Table 234 list all of possible options that are available in the Wizard: the options available to you depend on the connection configuration.
Table 234. Database Connection Configuration Wizard options
Description | |
---|---|
Enables support for the Intersection and Difference operators in the Append Query option. | |
Apply Filters to restrict the tables that are displayed in the table catalog | Enables specification of table filter conditions for limiting or customizing the list of tables in the table catalog. |
Excludes all repository tables from the table catalog. “Filter by” and “metadata” definitions override this preference. | |
Prohibits processing when topics are not joined in the Query Contents frame. | |
Specifies use of SQL to retrieve tables, instead of using SQL Server sp_tables and sp_columns stored procedures. This option enables table filtering, but may be slower than stored procedures. (Sybase and MS SQL Server) | |
Specifies how the server returns data. In most cases, “Retrieve data as Binary” is the most appropriate, and fastest method. Select “Retrieve data as Strings” if the connection API does not support native datatype retrieval, or if queries return incorrect or unreadable data. | |
Establishes an automatic disconnect from the database after the specified period of inactivity. | |
Sends a commit statement to the database server with each Interactive Reporting Studio SQL statement to unlock tables after they have been used. Use this feature if tables are locked after use or users experience long waits for tables. | |
Save Interactive Reporting Database connection Without User Name | Enables general distribution of an Interactive Reporting database connection file by saving it generically, without a user name. Instead, any user can log on by typing their own user name. |
Specifies that internal keywords or table and column, or owner names with special characters sent to the server be enclosed in quotation marks. For example, SELECT SUM(“AMOUNT”), “STORE_ID” FROM “HYPERION”.”PCS_SALES”GROUP BY”STORE_ID” | |
Adds Database field to logon dialog box enabling the user to select a specific database when logging on to the DBMS. (Sybase and MS SQL Server) | |
Specifies a binding process to retrieve more records per fetch call. If the ODBC driver supports binding, use this option for faster retrieval. (ODBC only). If this feature is turned on, the ODBC Extended Fetch call requests data at 32k at a time. | |
Enables Sybase’s DB-Lib users to set up a large buffer retrieval from the database so that more data can be transferred at one time. If this feature is selected, you can specify a multiple of 512 bytes for the number of bytes to transfer at one time. Before you specify a multiple of 512 bytes, the server must have enough memory to allocate for the transmission of the selected packet size. To check which packet size the Sybase server supports, run the isql command: sp_configure A list of parameters is returned. Find the parameter showing the “Maximum Network Packet Size.” If the packet size you entered exceeds the maximum packet size, you have to enter again a smaller packet size. To change the packet size, issue the following command in isql: Sp_configure “maximum network packet size”. <new value> | |
Determines the default buffer size when retrieving rows of data from an Oracle connection. The default size is 8000 bytes. A user can change this value to retrieve more rows per buffer, which may result in a performance improvement, but at the expense of additional memory requirements. The minimum size is 8000. If a user specifies a smaller value, nor error is returned, but 8000 bytes is used. There is no hard coded maximum size value for this field. | |
Turns off the ability to make simultaneous requests to the database server. This feature is available in Interactive Reporting Studio only. Note: | |
Interactive Reporting Studio uses the default formats specified by the database server when handling date, time, and timestamp values. If the default formats of the server have been changed, you can retain or preserve these adjusted preferences to ensure Interactive Reporting Studio interprets date/time values correctly. | |
Enables alteration of internal Interactive Reporting Studio date handling to match server default settings in case of a discrepancy. For more information on this feature, see Modifying Server Date Formats. | |
On upload to the repository, Interactive Reporting Studio brackets SQL Insert statements with transaction statements. Disable Transaction Mode if the RDBMS does not support transactions. This feature is only available in Interactive Reporting Studio. | |
Enables you to save theInteractive Reporting database connection file so that it can be reused at a later time. | |
Inserts an outer join operator (+) in the SQL on limits applied to the “inner” table for Oracle Net connection software to an Oracle database. By default this feature is enabled and is recommended; it is provided to work around Oracle restrictions when using outer joins with certain limit conditions, such as when an OR expression is needed. An outer join operator enables Interactive Reporting Studio to retrieve all rows from the “left” or “right” table matching joined column values if found or retrieves nulls for non-matching values. If this feature is disabled, then nulls for non-matching values are not retrieved. Use the Join Properties dialog box to assist in determining which is the “left” and “right” table. Oracle does not support full (left AND right) outer joins with the (+) operator. When an ODBC driver is used, this feature is greyed out. | |
When a limit has been applied to an inner table of an outer join, this feature enables the limit to be placed on the On clause of the SQL statement instead of the Where clause. The default setting for this feature is unchecked. | |
Inserts ODBC outer join escape syntax in the SQL statement. Note: Disable this option if nested outer joins are needed. |