KB_SQL 2016 (Version 5.8) Release Notes 03/28/2016. KBS eservice Center ( KBS.NET Download Agent...

Transcription

1 Table of Contents KBS eservice Center ( 4 KBS.NET Download Agent... 5 KB_SQL ADO.NET Data Provider... 6 KB_SQL JDBC Driver... 7 * Prepared Statement should not pass SQL on executequery() method... 7 * JDBC using multiple statements fails... 7 * Error in JDBC Driver when using prepared statements Bug: Correct save of Connection parameters and Login credentials Enh: Allow retrieval of RowCount on SQLExecute and/or SQLExecDirect Enh: Enable the setfetchsize method to set buffer sizes Enh: New method SQLAutoKeys allows access to automatically incremented key values Enh: Allow specification of default schema on statement allocation KB_SQL ODBC Driver Bug: SQLDriverConnect using DriverPrompt options: Bug: DSN-Less Connection failures: Enh: Add support for column and row binding using arrays and SQLFetchScroll / SQLExtendedFetch... 9 QREPro Desktop KB_SQL Server * Bug: Incorrect handling of CHARACTER key values * Bug: SQL_FN_TX_QUERY_IMAGE function fails to locate transaction with SQL command data * Bug: SQL EDITOR can display incorrect seed value for query name * Bug: XFER^SQL returns unexpected "information" message in SQLERR... 11

2 Bug: Handling of Virtual Column parsing is corrected Bug: DELETE^SQL tag can generate errors with leftover data Enh: Allow SITE to disable auto generation of table statistics Bug: Symbol table restore fails on local variables that exceed maximum global value length Bug: Retain selected query name in SQL EDITOR Enh: Modify TEST^SQL0TCP to use a default (4) number of connections : - Enh: Modify SQLCleanup process to clear orphaned temporary data Enh: Process numbers ($job) can be reused Bug: Manual Statistics procedure allows zero (0) entry Enh: TCP/IP Error Reporting Enh: New Functions for creating DATE, TIME, and MOMENT values Enh: Allow TABLE IMPORT to skip identical definitions Enh: Enable support for larger communication buffer sizes Enh: Enable return of RowCount on SQLExecute and/or SQLExecDirect Enh: Report failures to lock Server Query Queue and log for DBA review Bug: Reference to physical pointer corrupts data type reference Bug: Primary key initial values tested for string vs. numeric types Enh: Enable support for subqueries on the FROM clause Enh: Enable no-op handling of non-supported keywords on CREATE TABLE command Enh: Enable support for queries without FROM clause Enh: Enable support for the TOP clause Enh: Enable support for the LIMIT clause Bug: Correct handling of protected variables in TransactionLogSave (MSE) Bug: Correct handling of Transaction Log information for queries that fail to compile Bug: Correct handling of Transaction Log copy of SQL Text Bug: Correction to SQL_FN_TX_QUERY_IMAGE function Bug: The pseudo column SYS_CURRENT_UCI is removed

3 Bug: Corrected handling of TIME value 00:00:00 AM

4 KBS eservice Center ( The KBS eservice Center is the first place to go when looking for FAQs, Software Downloads, Product Documentation, and more. Anonymous accounts are allowed to search public answers. Client accounts are allowed more privileged access based on having an active maintenance agreement.

5 KBS.NET Download Agent The KBS.NET Download Agent automates the local save of File Image data from the Server to a local (or network) drive. There are no changes in this release.

6 KB_SQL ADO.NET Data Provider The KB_SQL ADO.NET Data Provider connects Microsoft.NET applications to KB_SQL Server. There are no changes in this release.

7 KB_SQL JDBC Driver The KB_SQL JDBC Driver connects Java applications to KB_SQL Server. * Prepared Statement should not pass SQL on executequery() method The prepared statement model was incorrectly allowing the use of the executequery() method to pass a SQL statement. This parameter usage was ambiguous since the SQL was already passed on the prepared statement methods. We have disabled the use of the executequery() method with a SQL text parameter in the context of prepared statements. * JDBC using multiple statements fails One of the benefits of using the prepared statement model is the ability to re-use a SQL statement, providing new sets of parameter values at runtime. A problem was introduced that caused a premature close of the active statement, effectively disabling support for the re-use of a prepared statement. This problem has been resolved. * Error in JDBC Driver when using prepared statements There was a change in the previous release of the JDBC Driver ( ) that allowed the communication buffer size to be specified as a parameter. The fetchsize() method was added as well as a connection string option to set the communication buffer size. There was a mistake that caused the statement-specific value to be ignored when creating a KBSRowsetFrame() message package to exchange data between the JDBC Driver and the KB_SQL Server. This could have caused errors related to a zero (0) sized communication buffer. The problem has been resolved Bug: Correct save of Connection parameters and Login credentials The KB_SQL JDBC Test Client is corrected (on Windows 10) to properly save the connection parameters and login credentials Enh: Allow retrieval of RowCount on SQLExecute and/or SQLExecDirect JDBC Driver performance is improved by reducing server round trips to retrieve count of rows affected by DML commands. The SQLExecute and SQLExecDirect methods can retrieve the row count as part of the return message. Note that for backwards compatibility, the SQLRowCount method will be used when connecting to older server environments. Note also that this feature primarily affects the performance of DML (Insert/Update/Delete) commands where the row count is known at execution time. For SELECT queries, the row count is not known until the result set is processed Enh: Enable the setfetchsize method to set buffer sizes. The JDBC Driver is enhanced to support the setfetchsize method. This allows the developer to request a custom sized communication buffer used to store rows retrieved from the server. A larger value reduces the number of round trips to collect a large result set. Acceptable values are between 20 and 64k.

8 Enh: New method SQLAutoKeys allows access to automatically incremented key values. A new method is implemented to allow access to automatically generated primary key values. This prevents the user from having to query the database to determine the keys. Note that this method has value when modifying rows in a modifiable table with an internally updated key value Enh: Allow specification of default schema on statement allocation. Support is added for the SetSchema method, allowing the user to specify a default schema. Note that the default schema will be used to resolve ambiguity when an unqualified table reference is used to specify a table that exists in multiple schemas.

9 KB_SQL ODBC Driver The KB_SQL ODBC Driver connects Windows applications to KB_SQL Server. The KB_SQL ODBC Driver is available in 32 and 64-bit versions. Both versions can support Unicode if enabled by the application and by the Server (available for InterSystems Cache only). There are no changes in this release Bug: SQLDriverConnect using DriverPrompt options: KB_SQL ODBC Driver is updated to allow use of SQLDriverConnect with the DriverPrompt method. This is similar to SQLBrowseConnect. It allows the connection string to be configured dynamically at connection time Bug: DSN-Less Connection failures: Corrections made to accommodate certain client-specific behaviors when using DSN-less connections. Affected applications include Microsoft Access, QTODBC70, and others that rely on this type of connection Enh: Add support for column and row binding using arrays and SQLFetchScroll / SQLExtendedFetch Corrections made to support for binding of result rows using arrays. Changes apply to use of ODBC 2.x method using SQLExtendedFetch (SQL_ROWSET_SIZE), and to ODBC 3.x method using SQLFetchScroll (SQL_ATTR_ROW_ARRAY_SIZE).

10 QREPro Desktop QREPro Desktop provides a graphical user interface to all of the KB_SQL Reporting features. You can browse the data dictionary. You can create, edit, and deploy KB_SQL Queries and Reports. It provides a rich experience for query design and execution. There are no changes in this release.

11 KB_SQL Server The KB_SQL Server is the foundation of KB_SQL. It provides the SQL Engine and the Data Dictionary. Together, these provide access to all of your application data. Server utilities allow configuration of the major behaviors of the server including security, transaction management, and more. The SQL EDITOR is the legacy interface for query design using a character terminal interface. * Bug: Incorrect handling of CHARACTER key values An error was discovered in the processing of WHERE-clause predicates together with the existence of 'start at' values on primary keys. The 'start at' processing was changed for v5.7 to accommodate alternate collation schemes. An unwanted side effect went unnoticed until there was a case where these two conditions were in play. * Bug: SQL_FN_TX_QUERY_IMAGE function fails to locate transaction with SQL command data The SQL_FN_TX_QUERY_IMAGE function is trying to return the ID for an entry in the transaction log that has SQL command data. It is using an expression that tries to locate the most recent transaction by date and time. The expression needed to have an extra second added in order to not step over a transaction that happened in the same instant. * Bug: SQL EDITOR can display incorrect seed value for query name The SQL EDITOR attempts to retain the query name as a seed value to minimize typing. In some cases, including when navigation keys are used, the seed value could be stored incorrectly. This has been corrected. * Bug: XFER^SQL returns unexpected "information" message in SQLERR When using the program entry point XFER^SQL under certain conditions including with messaging disabled, a misleading informational message is returned. The variable SQLERR="Finished [date-andtime]". This has been corrected Bug: Handling of Virtual Column parsing is corrected During query compilation, virtual column expressions can be parsed. This logic is corrected to ensure that only one process can perform the parse at a given instance of the query compiler. A record lock is established on virtual column data during query compilation. This record lock is cleared after processing the virtual column parse data Bug: DELETE^SQL tag can generate errors with leftover data A problem with the DELETE^SQL tag was corrected to avoid spurious errors related to leftover data from transactions on the same connection Enh: Allow SITE to disable auto generation of table statistics. By default, KB_SQL will attempt to generate statistics for tables that have none. This behavior can be suppressed by a SITE by setting the SITE_DISABLE_AUTO_STATS parameter. This can be done by directly setting the value (61,19) or by using the \CONFIGURATION\SITE EDIT\ACCESS PLAN INFO procedure by setting the "Disable Auto stats" value to YES.

12 Bug: Symbol table restore fails on local variables that exceed maximum global value length When the local symbol table includes variables with length greater than the Global value max (GVMAX), the management process fails to store/restore the symbols. Code is corrected to properly handle long variables. Affects MSE implementation Bug: Retain selected query name in SQL EDITOR The name of the selected query is retained in SQL EDITOR with the goal of supporting user workflow by "remembering" the last query Enh: Modify TEST^SQL0TCP to use a default (4) number of connections. The TEST^SQL0TCP procedure is modified to use a default of four (4) connections. You can override this default and specify any number of connections for testing purposes. 2901: - Enh: Modify SQLCleanup process to clear orphaned temporary data The SQLCleanup process will rollback (or undo) incomplete transactions associated with process ($job) that have terminated. The process is enhanced to clear any orphaned data structures that might not be associated with a connection Enh: Process numbers ($job) can be reused. Code is enhanced in KILL^SQLV3 to remove process-specific data structures including ^SQLXX($JOB). This is to help ensure that if process numbers are re-allocated, we do not associate temporary data with the wrong process Bug: Manual Statistics procedure allows zero (0) entry. The MANUAL STATISTICS procedure is modified to ensure that data entry for the number of average distinct values is greater than zero (0) for all keys. This is to avoid errors during the query planning process Enh: TCP/IP Error Reporting. If multiple error messages are available, we will concatenate them together using the semi-colon (;) character as a separator Enh: New Functions for creating DATE, TIME, and MOMENT values. New functions allow for the dynamic creation of DATE, TIME, and MOMENT value expressions. SQL_FN_MAKE_DATE(year-value,month-value,day-value) = date-valued-expr SQL_FN_MAKE_TIME(hour-value,minute-value,second-value) = time-valued-expr SQL_FN_MAKE_MOMENT(date-value, time-value) = moment-valued-expr 2893 Enh: Allow TABLE IMPORT to skip identical definitions. When importing table definitions, skip ones that are identical to currently stored tables. This not only

13 saves the work of deleting and re-creating the tables, it saves marking all of the queries as dirty, then compiling the queries, etc. Note that the IMPORT TRANSACTIONS log will show entries as skip identical when this rule has been applied. To enable at the SITE level, use the \CONFIGURATION\SITE EDIT procedure to customize the DEFAULT values. Specify YES for Skip identical?. Note also, you can directly set the parameter at ^SQL(1,SQLSITE,61), ~,18)=1. When importing tables, you will be prompted once again to Skip identical? based on the SITE parameter setting. You can override in the import procedure. Note also, from direct program access, you can specify the handling of identical tables using the variable SQLOWX=1 to enable the feature Enh: Enable support for larger communication buffer sizes. Allow use of larger communication buffer to do more work on server when returning large result sets. Note that 20k remains the default value. Acceptable values are in the range of 20 to 64k. A larger value allows for more work to be done on the server in each packaged retrieval of result set values. This can improve performance, especially in queries that retrieve very large numbers of rows Enh: Enable return of RowCount on SQLExecute and/or SQLExecDirect. To reduce server trips, return RowCount on SQLExecute and/or SQLExecDirect packages. Note that this enhancement is primarily to support the performance improvement in the KB_SQL JDBC Driver Enh: Report failures to lock Server Query Queue and log for DBA review. When a process fails to acquire the exclusive lock on the Server Query Queue, an error will be returned to the process and logged for DBA review. Note that the lock will be tried up to 5 times for a total wait time of approximately 20 seconds before the process aborts with an error Bug: Reference to physical pointer corrupts data type reference. References to physical column pointer values (primarily in data_dictionary schema) can corrupt references to data type values. A column reference such as link@name should inherit the data type of the name column. With this error, the column incorrectly inherits the data type of the link column. The error primarily affects the DATA_DICTIONARY tables and has been corrected Bug: Primary key initial values tested for string vs. numeric types. We had an error in a pattern attempting to identify initial values as being either numeric or string. Based on the result, we would use either the FOLLOWS (string) or GREATER-THAN (numeric) operators. This is now resolved Enh: Enable support for subqueries on the FROM clause. We now allow the use of subqueries on the FROM clause. For example: select xvalues.name from (select name, description from data_dictionary.table) as xvalues Note that this is part of an effort to support certain 3rd party applications such as Tableau Software Enh: Enable no-op handling of non-supported keywords on CREATE

14 TABLE command. We now handle certain optional parameters on CREATE TABLE command are ignored, including: LOCAL, TEMPORARY, ON, COMMIT, PRESERVE ROWS. Note that this is part of an effort to support certain 3rd party applications such as Tableau Software Enh: Enable support for queries without FROM clause. Queries without FROM clause will be processed, using internal association with the DATA_DICTIONARY.SQL_ONEROW table. Note that this is part of an effort to support certain 3rd party applications such as Tableau Software Enh: Enable support for the TOP clause. A new keyword is supported to limit rows returned from a query result set. -- select TOP 10 name from table Note that this is part of an effort to support certain 3rd party applications such as Tableau Software Enh: Enable support for the LIMIT clause. A new keyword is added to limit the number of rows returned from a query result set. -- select name from table LIMIT 10 Note that this is part of an effort to support certain 3rd party applications such as Tableau Software Bug: Correct handling of protected variables in TransactionLogSave (MSE) The error was discovered in the TXSAVE module of the SQLV5 routine. This module has responsibility to govern whether transaction logging is enabled for the query being executed. We found an MSE-specific coding error that allowed certain variables (SQL2, SQL7, SQL8) to remain in the symbol table after execution of the module. Over time, and with enough transactions over the same connection, this could exhaust the available memory for the server process, causing an error that aborted the process Bug: Correct handling of Transaction Log information for queries that fail to compile. A correction was made to the transaction log for queries compiled via the COMPILE ALL QUERIES procedure. The correction ensures that failed compiles will be properly recorded in the log Bug: Correct handling of Transaction Log copy of SQL Text. In order to maintain query change history, we will not delete transaction log entries that have query text saved. Note that this can have storage implications as we will expect to see an increase in the storage allocated to the TRANSACTION_LOG (209) table Bug: Correction to SQL_FN_TX_QUERY_IMAGE function. The behavior of the Transaction Log SQL store/retrieval has been corrected. This affected the built-in function SQL_FN_TX_QUERY_IMAGE that returned the ID of the Transaction Log row that contains SQL Text for a specific query Bug: The pseudo column SYS_CURRENT_UCI is removed. The pseudo column SYS_CURRENT_UCI was mistakenly included in the distribution and has been removed.

15 Bug: Corrected handling of TIME value 00:00:00 AM. The TIME and MOMENT conversion utilities are corrected to properly handle the case where an hour value of zero (0) is combined with the 'AM' suffix as in '00:00:01 AM'. Note that the TIME '00:00:01' (without the 'AM' suffix) is not affected and was working as expected.