KB_SQL 2018 (Version 6.1) Release Notes 4 January KBS eservice Center ( 2. KBS.NET Download Agent...

Transcription

1 Table of Contents KBS eservice Center ( 2 KBS.NET Download Agent... 3 KB_SQL ADO.NET Data Provider... 4 KB_SQL JDBC Driver... 5 KB_SQL ODBC Driver... 6 QREPro Desktop... 7 KB_SQL Server 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:... 9

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

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

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

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

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

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

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

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