KB_SQL 2018 (Version 6.1) Release Notes 04 December KBS eservice Center ( 3. KBS.NET Download Agent...

Transcription

1 Table of Contents KBS eservice Center ( 3 KBS.NET Download Agent... 4 KB_SQL ADO.NET Data Provider... 5 KB_SQL JDBC Driver... 6 KB_SQL ODBC Driver Bug: VS2015 Redistributed Components... 7 QREPro Desktop Bug: Splash Screen causing Anti-Virus quarantine Enh: Add support for Wildcards in QREPro Desktop Explorer Search Bug: Setting 'Use Server Format for Data' can cause Server API Cache corruption... 8 KB_SQL Server Enh: Need safe process-id usage in KB_SQL temporary globals, including ^SQLXX Bug: FUNCTION import fails on import of existing function object Bug: Export ALL functions generates empty file Bug: SITE EDIT imposes arbitrary restriction of 32kb for longest global value Bug: SITE EDIT imposes arbitrary 1MB restriction on routine size Bug: With rapid connections using same query errors can occur Bug: JOB Watch can fail when process is terminated Bug: SQL_FN_ISINTEGER errors on large numbers Bug: GTM Routine/Object paths are required Bug: Import Tables skip Identical new parameter values Bug: Import Identical Tables Index Tables Bug: Diagnostic data can be carried over from a previous query selection... 10

2 Bug: SQLDescribeCol catalog function handling of NULLABLE property Bug: SQLColumns request without TABLE specification Bug: Parsing error affects use of IS NOT NULL in a nested subquery Bug: Query post run execute is getting done 2x Enh: Remove references to un-used index tables in SHOW_ALL_PLANS Bug: DATE formatting can be incorrect for '12' hour formats Enh: New SITE parameter can be set to restrict delete of USER definitions Enh: Several XFER objects updated to use current standard formats Enh: XFER package updates to allow use of GLOBAL for input/output Bug: Address various issues with USER API routine SQL0USR Bug: Handle failed user authentication using SITE Execute Enh: Speed-up handling of STOP SQLCleanupAgent Bug: Correct handling of NOIC parameter on SQL0LOAD Feature: Add support for TO_GLOBAL and FROM_GLOBAL for DEVICE_TYPE Transfers: Feature: Implement concurrent TCP for GT.M: Bug: Transaction log maintenance should remove transactions for deleted queries: Bug: Export of Table Statistics should include Index tables: Bug: Import of FUNCTION data using FROM_GLOBAL method fails to initialize data: Enh: Implement $HALT for user-supplied execute code (InterSystems Cache) Enh: Allow customization of the QUERY TRANSACTION DETAIL report: Enh: Allow display/print of INDEX table definitions separately from the master table: Enh: Generate Transaction Log entry for queries that RUN but abort with Error: Enh: Allow FINAL event to process regardless of rows selected Bug-Transaction Log options confusion:... 14

3 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.

4 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.

5 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.

6 KB_SQL JDBC Driver The KB_SQL JDBC Driver connects Java applications to KB_SQL Server. There are no changes in this release.

7 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) Bug: VS2015 Redistributed Components We have updated the Visual Studio 2015 Redistributed Components. In some cases, we were seeing runtime errors with certain Microsoft Office applications until we corrected the distribution.

8 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 Bug: Splash Screen causing Anti-Virus quarantine The Splash Screen is removed from the QREPro Desktop startup Enh: Add support for Wildcards in QREPro Desktop Explorer Search The Explorer Search will now support the use of SQL Wildcards in order to refine the search criteria. With a check-box, the user can opt to use Regular Expressions for searching as a powerful alternative Bug: Setting 'Use Server Format for Data' can cause Server API Cache corruption A correction was applied to avoid Server API Cache corruption when QREPro Desktop is configured to 'Use Server Format for Data'.

9 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 Enh: Need safe process-id usage in KB_SQL temporary globals, including ^SQLXX The primary subscript of the ^SQLXX global is changed from '$JOB' to 'SQLJOB'. This allows for the use of the software in a clustered environment where multiple nodes could generate the same $JOB identifier. Additional configuration is required. The customer must have a SITE_PROCESS_ID execute that includes the node identifier in the definition of the process id. For example: >S SQLJOB=$$myNode()_" "_$job Bug: FUNCTION import fails on import of existing function object IMPORT FUNCTION procedure is corrected to properly handle import of existing function object Bug: Export ALL functions generates empty file A correction was made to the transfer of FUNCTION objects when 'Select all' is requested Bug: SITE EDIT imposes arbitrary restriction of 32kb for longest global value A correction is applied to SITE EDIT to remove arbitrary restriction on size of global value. This can be set to value supported by M Technology (MUMPS) Implementation Bug: SITE EDIT imposes arbitrary 1MB restriction on routine size A correction is applied to SITE EDIT to remove arbitrary restriction on size of routine. This can be set to value supported by M Technology (MUMPS) Implementation Bug: With rapid connections using same query errors can occur When many simultaneous connections submit the same (or similar) query to the Server API, errors could occur. We changed the scope of the semaphore lock that ensured exclusive access to the Server Queue to include the QueryFind, optional QueryAdd, and optional QueryCompile phases Bug: JOB Watch can fail when process is terminated The JOB WATCH utility is updated to handle situations where the process listing is changing rapidly while viewing job activity.

10 Bug: SQL_FN_ISINTEGER errors on large numbers Functions SQL_FN_ISINTEGER and SQL_FN_ISNUMERIC are updated to handle situations where the value would exceed maximum number size Bug: GTM Routine/Object paths are required The GTM Routine and Object paths are required for proper installation of KB_SQL. Whatever the paths are, they must be consistent with the $ZROUTINES configuration of the site. We need to know where to write source and object code so that it can be run at execution time. The GTMRTN and GTMOBJ values are also added to the AUTO^SQL0LOAD() entry Bug: Import Tables skip Identical new parameter values When importing tables, with skip identical, newly added parameter values can be overlooked by the processor causing misrepresentation of identical status. This is resolved in the current release Bug: Import Identical Tables Index Tables When importing tables with 'skip identical', new Index Tables are imported but existing Index Tables can be deleted. This has been corrected Bug: Diagnostic data can be carried over from a previous query selection In some cases, we are seeing diagnostic/error data being carried forward from prior query selections. We have added a call to KILLDIAG^SQL0ERR to initialize diagnostic control structures on each query selection Bug: SQLDescribeCol catalog function handling of NULLABLE property The SQLDescribeCol catalog function is used to return a set of metadata for select-list columns. The NULLABLE property indicates whether a column value can be NULL. The NULLABLE property is set either to SQL_NO_NULLS if the expression is a column that is required in the data dictionary table definition. Or, it will be SQL_ALLOW_NULLS Bug: SQLColumns request without TABLE specification The SQLColumns catalog function can be used to return a set of column metadata. Certain applications were calling SQLColumns without specifying a source TABLE. This effectively returns all columns for all tables and can be an expensive process. We have yet to see a practical use of this feature. The SQLColumns catalog function is modified to return an empty set if called without a TABLE specification Bug: Parsing error affects use of IS NOT NULL in a nested

11 subquery A correction was applied to the handling of the NULL predicate in nested subqueries. Under certain conditions, the NULL predicate could be corrupted in an attempt to ensure proper syntax Bug: Query post run execute is getting done 2x A correction was applied to avoid redundant execution of the QUERY POST RUN custom code Enh: Remove references to un-used index tables in SHOW_ALL_PLANS The SHOW_ALL_PLANS parameter behavior is modified to exclude references to index tables that are not being considered by the query planner. To include the maximum details, consider the SHOW_ALL_PLANS_VERBOSE parameter Bug: DATE formatting can be incorrect for '12' hour formats When using the 12-hour formats, the value of '30 minutes past midnight' should be '12:30 AM'. It was incorrectly being formatted as '00:30 AM' Enh: New SITE parameter can be set to restrict delete of USER definitions A new SITE parameter can be set to restrict delete of USER definitions. -- SITE.SITE_RESTRICT_USER_DELETE (61,23) If set, attempts to delete a USER definition will be restricted with an error message. It is recommended that USER accounts are disabled, as this will maintain transaction records Enh: Several XFER objects updated to use current standard formats The following XFER objects are updated to use the current standard formats: - DEVICE_TYPE - FUNCTION - PSEUDO_COLUMN Note that the TABLE object type continues to use the legacy format. Note also that pre-v6.1 exports of DEVICE_TYPE, FUNCTION, and PSEUDO_COLUMN will continue to work Enh: XFER package updates to allow use of GLOBAL for input/output The XFER package is updated to allow for user-specified global for input/output.

12 For example: (output) s SQLXTO="TABLE" s SQLXTM="TO_GLOBAL" s SQLXTM("GLOBAL")="^MYEXP(SQLXTO)" s SQLXNM="MYSCHEMA.*" d XFER^SQL Note: Output will be stored in ^MYEXP("TABLE"). If "GLOBAL" parameter is not provided, data will be saved into ^SQLIX(SQL(1),"TABLE") where SQL(1) is connection identifier. (input) s SQLXTO="TABLE" s SQLXTM="FROM_GLOBAL" s SQLXTM("GLOBAL")="^MYEXP(SQLXTO)" s SQLOW=1 d XFER^SQL Note: Input will be processed from ^MYEXP("TABLE"). If "GLOBAL" parameter is not provided, data will be processed from ^SQLIX(SQL(1),"TABLE") where SQL(1) is connection identifier Bug: Address various issues with USER API routine SQL0USR The USER API in routine SQL0USR is updated to address several issues Bug: Handle failed user authentication using SITE Execute When using the SITE.DETERMINE_USER execute, login should test for an error code in SQLERR or a missing value of SQLUSER and will *NOT* prompt for login Enh: Speed-up handling of STOP SQLCleanupAgent Previously, the handler for STOP of the SQLCleanupAgent could take up to the total interval time. While the default of 60 seconds wasn't too much, some customers have configured the agent to run every 10 minutes. Depending on the cycle, the STOP could take up to 10 minutes to complete. With the modifications, the STOP will most often complete in under 5 seconds Bug: Correct handling of NOIC parameter on SQL0LOAD The NOIC parameter on AUTO^SQL0LOAD allows for the suppression of the INTEGRITY CHECK procedure

13 after the last script step of the process. This parameter has been corrected to work properly. Note that the NOIC parameter does *not* work when upgrading across versions Feature: Add support for TO_GLOBAL and FROM_GLOBAL for DEVICE_TYPE Transfers: The TO_GLOBAL and FROM_GLOBAL methods are now supported for DEVICE_TYPE transfers. Note that the global is ^SQLIX(SQL(1),"DEVICE_TYPE") where SQL(1) is the connection handle value Feature: Implement concurrent TCP for GT.M: KB_SQL for GTM (Version 6.+) now supports the concurrent TCP model eliminating the need for alternate ports. This new feature will allow for simpler administration of KB_SQL environments using GTM. Note that the alternate ports method continues to be supported but requires the setting of a SITE parameter named SITE_TCPIP_FORCE_ALTERNATES (61,22) Bug: Transaction log maintenance should remove transactions for deleted queries: A correction was made to the maintenance of transaction log rows. We were allowing rows with SQL Text to remain indefinitely for source change purposes. We should not have preserved rows where the associated query was deleted. This has been corrected Bug: Export of Table Statistics should include Index tables: The \UTILITIES\EXPORT\TABLE STATISTICS procedure is modified so that index tables are automatically included with base tables that are submitted for processing Bug: Import of FUNCTION data using FROM_GLOBAL method fails to initialize data: The import process for FUNCTION data using the FROM_GLOBAL method is corrected to properly initialize the local storage of data Enh: Implement $HALT for user-supplied execute code (InterSystems Cache) For InterSystems Cache implementations of KB_SQL, a halt execute will be used in the EXEC^SQL0H module. This will cause execution of a 'HALT' command to be treated as an error condition that simply quits returning control to the caller Enh: Allow customization of the QUERY TRANSACTION DETAIL report: We have modified the QUERY TRANSACTIONS DETAIL report to allow customization of the output. The user can specify whether built-in queries should be excluded (default=yes). The user can specify a custom LIKE pattern match for queries to be included (e.g., MY\_STUFF\_%). Note use of LIKE pattern match wildcard (_%) and escape (\) characters.

14 Enh: Allow display/print of INDEX table definitions separately from the master table: We have modified the TABLE PRINT procedure to allow for the printing of a single INDEX table definition. When the FROM/TO values match exactly, the query will ignore the MASTER_TABLE setting, allowing display of an index (or base) table Enh: Generate Transaction Log entry for queries that RUN but abort with Error: We have added a wrapper function to those places where we execute query routines. This allows us to process an error condition by adding an entry in the transaction log at run time. Note that this is in addition to any error logging that might already be configured. When viewed using the \UTILITIES\TRANSACTION LOGS\QUERY TRANSACTIONS\QUERY TX DETAIL report, these transactions will include information about the Error that occurred. Note that they will also appear to have a TYPE=RUN *, where the asterisk is displayed based on the END_TYPE value of 99. This is a special end value for queries that abort Enh: Allow FINAL event to process regardless of rows selected We have updated the \CONFIGURATION\SITE EDIT\CUSTOM LOGIC\TRANSACTION LOGS module to make certain configurations more obvious. First, the 'Disable all transaction logs' setting will mark all other settings as disabled. Likewise, the 'Disable verbose transaction logs' setting will mark all of the lower level settings as disabled. The interface allows the use of the [undo] key to revert the changes in case of error Bug-Transaction Log options confusion: We have updated the \CONFIGURATION\SITE EDIT\CUSTOM LOGIC\TRANSACTION LOGS module to make certain configurations more obvious. First, the 'Disable all transaction logs' setting will mark all other settings as disabled. Likewise, the 'Disable verbose transaction logs' setting will mark all of the lower level settings as disabled. The interface allows the use of the [undo] key to revert the changes in case of error.