KB SQL Release Notes Version 4 - Oracle · KB_SQL Release Notes Version 4.5 Knowledge Based Systems, Inc. Last Updated: Tuesday, March 21, ... KB_SQL Server Query locking algorithms

KB_SQL Release Notes Version 4.5

Knowledge Based Systems, Inc.

Last Updated: Tuesday, March 21, 2006

© Copyright 2006 by Knowledge Based Systems, Inc. All rights reserved. Knowledge Based Systems, Inc., Ashburn, Virginia, USA. Printed in the United States of America. No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Knowledge Based Systems, Inc., as governed by United States and international copyright laws. The information contained in this document is subject to change without notice. Knowledge Based Systems, Inc. does not warrant that this document is free of errors. If you find any problems in the documentation, please report them to us in writing.

Knowledge Based Systems, Inc. 43053 Midvale Court Ashburn, Virginia 20147

Alternatively you can suggest the correction in the KBS eService Center at www.knowledgebasedsys.com/support. Website: www.knowledgebasedsys.com Email: [email protected] KB_SQL is a registered trademark of Knowledge Based Systems, Inc. MUMPS is a registered trademark of the Massachusetts General Hospital. All other trademarks or registered trademarks are properties of their respective companies.

Release Notes Version 4.5 Knowledge Based Systems, Inc.

http://www.knowledgebasedsys.com/support

http://www.knowledgebasedsys.com/

mailto:[email protected]

TABLE OF CONTENTS INTRODUCTION......................................................................................................................... 1

NEW FEATURES......................................................................................................................... 2 KB_SQL SERVER ........................................................................................................................ 2

Query locking algorithms are improved. ................................................................................ 2 New Security features ............................................................................................................. 2 New Exception Rule handling................................................................................................. 2 Enhancements to the Compile Queries procedure.................................................................. 2 Enhancements to the Help Documentation............................................................................. 2

KB_SQL ODBC DRIVER ............................................................................................................ 3 New installer leaves Microsoft MDAC components untouched. ............................................ 3 Driver will make multiple attempts to achieve TCP/IP connection........................................ 3 Driver will identify type and version to server on connection................................................ 3

KB_SQL QRE PROFESSIONAL .................................................................................................... 4 Explorer allows browsing of live data. ................................................................................... 4 Explorer can evaluate functions. ............................................................................................ 4 Explorer repository loading provides more feedback, rollback on cancel, and more. .......... 4 Explorer adds “Copy” menu to assist with query development ............................................. 4 Query Editor enhancements to make query development even easier.................................... 4 Query Editor allows automatic navigation of foreign key columns. ...................................... 4

KBS JDBC DRIVER ..................................................................................................................... 5 New driver supports Java connectivity solutions.................................................................... 5 New JDBC Client Tool provides interface for testing. ........................................................... 5 New JDBC Sample code illustrates using the KBS JDBC Driver. ......................................... 5

KBS DOWNLOAD AGENT............................................................................................................. 6 New application allows automated retrieval of saved File Images........................................ 6

FIXED ITEMS .............................................................................................................................. 7 KB_SQL SERVER FIXES .............................................................................................................. 8 KB_SQL ODBC DRIVER FIXES ................................................................................................ 14 KB_SQL QRE PROFESSIONAL FIXES ........................................................................................ 15 KBS JDBC DRIVER FIXES ......................................................................................................... 19 KBS DOWNLOAD AGENT FIXES................................................................................................. 20 KBS ESERVICE CENTER FIXES................................................................................................... 21

KNOWN PROBLEMS ............................................................................................................... 22

KB_SQL SERVER KNOWN PROBLEMS....................................................................................... 22 KB_SQL ODBC DRIVER KNOWN PROBLEMS........................................................................... 24 KB_SQL QRE PROFESSIONAL KNOWN PROBLEMS................................................................... 25 KBS JDBC DRIVER KNOWN PROBLEMS ................................................................................... 26 KBS DOWNLOAD AGENT KNOWN PROBLEMS ........................................................................... 27

Release Notes Version 4.5 Knowledge Based Systems, Inc.

Introduction The Release Notes provides information about the product's new features, fixes, and known problems for Knowledge Based Systems' VARs and enterprise clients. The features are documented to provide the reader with information regarding the purpose of the feature and its intended use. Key fixes are documented to provide the problem definition and possible symptoms of the problem. Known problems are documented to provide a detailed description of the problem, situations that may cause the problem, and in situations where possible, a workaround.

1 Release Notes Version 4.5 Knowledge Based Systems, Inc.

New Features

KB_SQL Server

Query locking algorithms are improved. The query locking algorithms are improved to ensure that users have exclusive rights when opening queries for editing, but shared access when running queries.

New Security features Several new security features are added to help manage controlled access to your data. A newly reorganized SITE SECURITY EDIT procedure allows management of settings that apply to all users. A reformed USER EDIT procedure manages security settings for individual users.

New Exception Rule handling A new mechanism will perform custom logic on each occurrence of a particular error code. You can create your own exception rules to gather more information on error codes of your choosing. Use this feature to complement the existing set of diagnostic tools. See the new procedure option named \CONFIGURAION\EXCEPTION RULE EDIT on the DBAS menu.

Enhancements to the Compile Queries procedure The Compile All Queries procedure is enhanced to allow selection of a set of queries owned by a particular user group. Also, the compile process can now be launched to run in the background. This will free up the terminal for other activities.

Enhancements to the Help Documentation We have tried to update the new prompts in the system with help documentation. In addition, we have made some subtle changes to the behavior of the help system overall. Rather than taking over the entire screen, the help will now display on the bottom panel of the screen. We’ve reversed the ordering of help segments so that the context specific help will come first, before any domain or data-type specific help.


KB_SQL ODBC Driver

New installer leaves Microsoft MDAC components untouched. A new version of the ODBC Driver installer is available that does not include the Microsoft MDAC components. Clients can distribute this installer in situations where they don’t want to upgrade the MDAC components for whatever reason.

Driver will make multiple attempts to achieve TCP/IP connection. Sometimes the TCP/IP server cannot keep up with the pace of incoming connection requests. In order to accommodate this situation, the KB_SQL ODBC Driver is modified to try the TCP/IP connection several times in sequence before raising an error.

Driver will identify type and version to server on connection The server will receive a signature from the driver at connect time to indicate the type of driver (e.g., ODBC or JDBC) and the version. This information will be available for driver versions starting with v4.5. Initially, this information will appear in the UTILITIES\JOB WATCH procedure. Note: The KB_SQL ODBC Driver v4.5 requires the matching version of the KB_SQL Server v4.5.


KB_SQL QRE Professional

Explorer allows browsing of live data. The data dictionary explorer will now allow the browsing of live data for Tables, Views, and Stored Procedures. This new option is designed to help the infrequent user to determine which table is the right one for their research.

Explorer can evaluate functions. The data dictionary explorer has a new “Evaluate” function for Functions, Pseudo Columns, and Stored Procedures. The evaluate option will execute the component and display the results for the user. In the case of Functions and Stored Procedures, the user can enter a set of input parameters.

Explorer repository loading provides more feedback, rollback on cancel, and more. The explorer repository now includes a status window showing the progress as data dictionary, function, and other data is loaded. The process can be cancelled leaving the previous repository intact.

Explorer adds “Copy” menu to assist with query development The explorer repository now includes a right-click “Copy” menu that allow the object name or syntax to be copied to the clipboard. Using the Edit|Paste function will insert the text into the query. These menu options complement the existing drag-and-drop functionality.

Query Editor enhancements to make query development even easier. The Query Editor has been enhanced to allow for automated assistance while typing data dictionary references to schemas, tables, and columns. Once the table references from the FROM clause are known, references to table names and/or aliases will raise a list of columns to be selected.

Query Editor allows automatic navigation of foreign key columns. Along with the new functionality provided to streamline schema, table, and column references, the Query Editor can now resolve foreign key references. Type the ‘@’ character after a known foreign key column, and the Query Editor will raise a list of columns from the target table.


KBS JDBC Driver

New driver supports Java connectivity solutions. An all new JDBC Driver is included in this release. The KBS JDBC Driver supports connectivity from Java applications. These applications can be written in Java for Windows or Unix/Linux.

New JDBC Client Tool provides interface for testing. An all new utility is include to assist the Java developer working with KB_SQL using the KBS JDBC Driver. You can explore the tables in the data dictionary. You can write queries against the KB_SQL tables and views and see the results in a data grid. This tool is designed for the Java/JDBC developer. Note: This application is written in Java and uses the KBS JDBC Driver. Your workstation is expected to have either the Java Runtime Environment (JRE) or the Java Development Kit (JDK) installed. For more information on these Java development packages, please go to http://www.sun.com.

New JDBC Sample code illustrates using the KBS JDBC Driver. Sample code is always good. We have included a couple of samples that are designed to show you the basics of working with the KBS JDBC Driver. These samples and the documentation are designed for the Java/JDBC Developer.


http://www.sun.com/

KBS Download Agent

New application allows automated retrieval of saved File Images. A new system tray application, KBS Download Agent, automatically saves File Images saved using the SQL_FILE_IMAGE method and with a filename specified using the SET FILE parameter. Note: This application is written in Java and uses the KBS JDBC Driver. Your workstation is expected to have the Java Runtime Environment (JRE) installed. For more information on the JRE, please go to http://www.sun.com.


http://www.sun.com/

Fixed Items This section has been categorized based on the affected component.

• KB_SQL Server • KB_SQL ODBC Driver • KB_SQL QRE Professional • KBS JDBC Driver • KBS JDBC Client • KBS Download Agent • KBS eService Center

Within each section, a table below lists the key items that were fixed in this release. The following information is included: KBS Number This is the unique development database identifier. This value is searchable in the KBS eService Center. Description This is a high level description of the problem.

Answer ID In those situations where additional documentation is available, the information can be found in the KBS eService Center using the Answer ID provided. If you do not have an account to the KBS eService Center, please contact us at [email protected] to request an account. To search the online knowledge base with the provided id:

1. Log on to the KBS eService Center at http://www.knowledgebasedsys.com/support. 2. Select the “Answers” tab.

3. In the “Search Text” field, enter the answer id.

4. Select “Answer ID” from the “Search by” list. 5. Click the “Search” button.

For a complete update of incidents submitted by your company, please log onto our web site at http://www.knowledgebasedsys.com/support and select the “My Knowledge Base” tab.




KB_SQL Server Fixes KBS Number

Description Answer ID

1126 Ensure that all prompts have some help documentation. We’ve tried to add help text where it was missing.

1124 The processing of the SQL_UNIQUE_COUNTER table (844) was corrected to handle the reset of the counter value. This affected the following M types: ISM, Cache, and GTM.

1122 New report options added to the \UTILITIES\REPORTS menu option for DBAS, including: • DBA MESSAGE LOG • DBA RESET LOG • DBA TX MAINT LOG • LOGIN FAILURE LOG • INSTALL HISTORY LOG

1119 Stopping and Starting the Server API Trace feature will be logged in the DBA Message Log and in the Exception Log. See error code #914.

1118 The SQL_* queries are no longer marked as PUBLIC. In the case of queries used as stored procedures or as menu options, the queries will be marked as hidden. For other SQL_* queries that are useful, but haven’t’ found a permanent home, only the DBAS group will have access.

1117 The DEMO_* queries are no longer marked as PUBLIC. Privileges will be granted on these queries to members of the USERS and SYS_MGRS groups. These queries will not appear for new groups that you create unless you specifically grant privileges on them.

1109 The SECURITY\USER EDIT procedure renames the “DISABLE” option to “DISABLE/ENABLE” for all user groups.

1107 The EXCEPTION RULE PRINT option is added to the \CONFIGURATION\REPORTS menu option. This report will list all Exception Rules as well as the Error Codes and/or SQLState values associated with each rule.

1106 Exception Rules will be distributed with the KB_SQL Software. These built-in rules cannot be modified outside of KBS development. You can create new Exception Rules. These will be preserved by the software update process.

1100 Renamed the “Miscellaneous User Data” section to “General User Data” in the \SECURITY\USER EDIT procedure.

1097 A problem was fixed that caused the [undo] key to exit back too far in the SITE SECURITY EDIT procedure.


1094 A problem was fixed that caused the output device information to be removed from a background task after the first execution.

1091 The UTILITIES\JOB WATCH procedure can now show information about the Driver type (e.g., ODBC or JDBC), the Version, and the Application. Note that this information is only relevant for applications using the newest versions of the drivers.

1081 A problem was fixed with the READ LOOKUP feature so that it will now trap and report errors that occur in the lookup at run-time.

1080 A problem was fixed with the READ LOOKUP TABLE feature that caused errors when using empty parentheses after the lookup column reference. See also #1081.

1069 A problem was corrected affecting the use of the COLUMN_HEADINGS parameter in queries being compiled as a group through the COMPILE ALL QUERIES procedure. The initialization logic that is done for TAB formats was not being done for the other formats such as COMMA. Consequently, if there are two queries with the COLUMN_HEADINGS parameter enabled, and the first one has more display columns than the second, the code to display the headings in the second query would be corrupt. It would include the 'additional' columns from the first query.

1068 A problem was corrected with the automatic resolution of ODBC Escaped Function references. ODBC Allows the syntax {fn function-name(parameters)}. KB_SQL resolves these function references by appending the prefix “SQL_FN_” to the function-name reference. In certain cases, the resolution of the function name required an additional step. The affected functions are: {fn CURRENT_TIMESTAMP()} {fn CURRENT_TIME()} {fn CURRENT_DATE()}

1064 The AllowMultipleQueues feature is moved from the SITE definition to the USER definition. A conversion step will update the USER accounts according to the current SITE setting.

1063 The SECURITY\USER EDIT procedure is modified to reorganize existing and new prompts.

1062 Security options moved from CONFIGURATION\SITE EDIT to SECURITY\SITE SECURITY EDIT procedure.


1054 There were situations where clear text passwords were visible in the local symbol table. This could allow someone with programmer access to view someone else’s password. We have attempted to remove these from several locations including temporary variables.

1053 There were situations where messages were displayed using EM^SQL or ER^SQL and did not allow the user to see the message before it was cleared. The display will include a 'Press any key to continue' with a single character read.

1051 The tracking of errors reported since last login is corrected. 1047 Compile Query Log report shows the Last Run Date for all

queries.

1043 New query shows errors only for Compile Query Log. The results are ordered by the Last Run Date. This allows a quick inspection to determine if queries need to be fixed, or if the errors can be ignored.

1042 The COLUMN_HEADINGS parameter could have caused compilation errors when the total line length exceeded the global limits. It could also fail when certain non-display character was used as a delimiter. Both problems are corrected.

1041 SQL Editor [list] feature shows expanded details for COLUMNS including DOMAIN, LENGTH, and SCALE when applicable.

1039 The TRANSACTION LOG DETAIL report front-end now allows exit with the [undo] key.

1038 The TRANSACTION LOG DETAIL report now uses the correct setting for the start date.

1037 The overall performance of retrieving TEXT data type values is improved.

1036 Syntax, description, and examples are added to all built-in KB_SQL functions.

1030 The COMPILE ALL QUERIES procedure is enhanced to allow query selection based on ownership by a selected USER GROUP.

1029 The COMPILE ALL QUERIES procedure is enhanced to allow processing as a background job.

1028 The TRANSACTION LOG DETAIL report will now format values of variables that are of DATE, TIME, or FLAG data types.

1016 User accounts can now be marked as disabled. Based on a SITE setting, this can happen automatically when a user account fails the login process with too many sequential failures.


1015 Failed logins are now tracked in a table named SQL_LOGIN_FAILURE. This table will capture information about the failed login to support your efforts to secure your systems against unauthorized access.

1010 The stored procedure functions for deleting USER and USER_GROUP rows lacked sufficient referential integrity handling. This affected the following procedures: • SQL_SP_USER_DELETE • SQL_SP_USER_GROUP_DELETE

1008 Errors would occur when using RESET^SQL after previously running the STOP^SQL utility.

1007 The order of processing was fixed for download queries that include the PRE_RUN_ROUTINE parameter setting. Now the routine will be processed before opening the output device or file.

1006 The product report “COMPILED QUERY TRANSACTIONS” using query SQL_COMPILE_QUERY_LOG needed to include the MAX_SORTKEY_LENGTH setting to ensure that queries were grouped correctly using long descriptions.

999 TCP/IP related errors will now be trapped in both the Exception log and the DBA Message log. This includes the starting and stopping of the Server. See error code #915.

997 A problem was fixed that could have affected certain CREATE VIEW queries that included views in the FROM clause.

995 The AUTO^SQL0LOAD will now update the SITE NAME using the supplied value for the Customer Name.

994 When batch queries are run via the QrePro Screen Preview function, the query locks are now released upon completion.

992 The READ LOOKUP processing will now ignore columns of TEXT data type when displaying the rowset for a lookup. These columns cannot be displayed properly in a grid and should not be used in lookups.

990 There were corrections to the query delete function, including the external interface, DELETE^SQL, to ensure that the target row was locked.

989 There were corrections to the SQL EDITOR and EZQ EDITOR procedures regarding the deletion of queries. A diagnostic message should now appear to let the user know the status of the delete operation. See also #974.

986 A change was made to the algorithm that splits query text into an array of lines. The dot (.) character is now an acceptable split point. This was done to ensure that long lines could be split even when the line contained no spaces.

984 The [undo] key now works to allow the user to exit the Query Transactions Detail report.


983 The LOCK HISTORY report now accepts a date range for limiting the results.

982 A correction was made to the Query Import process so that as new versions of queries are imported, their previous base routine assignment is cleared and the routine is added to the free list of routines.

980 The Integrity Check procedure will now show a progress message when searching for NULL nodes in the SQL global. Note that this option only applies to those MUMPS environments that allow null subscripts.

979 Corrections were made to the query checkout process to ensure that only one user can own the lock allowing query modification. Previously, the lock was released prior to the device selection prompt. This could have allowed multiple users to modify the same query, with unpredictable results.

977 A change to a query name will now be reflected in the background queue. Previously, the old name would show for tasks for the query.

974 A change was applied to the SQL EDITOR and EZQ EDITOR procedure that affected the display of the ‘Commit’ prompt during the delete process. If the query cannot be deleted, a message will be displayed. The Commit prompt will not be presented. See also #989.

973 A change was made to the SQL EDITOR and EZQ EDITOR procedures. When a query cannot be deleted, an error message will be displayed. See also #989 and #974.

966 A correction was made to the SQLColumnPrivileges function. It could hang trying to process columns for a table if that same table name appeared in more than one schema.

964 Queries run via the Server API will now maintain a read lock on the query during execution. This helps to ensure consistency with queries run through other methods.

963 The EXPORT METHOD handler is modified to clear the value of the last ROW processed before the POST_RUN method is executed. This helps to avoid confusion as well as some errors when processing very large values of the ROW variable.

932 Error code #910 is now raised for errors that occur when writing to host files. These errors are considered serious and therefore are logged in the Exception Log and the DBA Message Logs. The file being written will be truncated to avoid confusion.

915 Variables that are used with the LIKE predicate need to be processed for pattern matching. This logic is now applied to variables that are set via Event Blocks.


909 When changing a user password in SECURITY\USER EDIT, the default expiration date will default based on the rule set for the SITE.

868 A long, lost feature has returned. Using the SQL EDITOR to edit and compile queries will once again return your cursor to the location of a recently discovered error.

860 Additional display columns can be added to READ LOOKUP TABLE extensions. READ LOOKUP TABLE table-ref.column-ref [(additional-column-references)] e.g., READ LOOKUP TABLE sql_test.employees.emp_ssn(name,salary,manager_link@name)

640 A problem was corrected with the SQL_QUERY_LINE table so that it should now support the ORDER BY clause correctly when working with multiple queries. Be sure to include the SEQUENCE number in the ORDER BY clause to ensure correct ordering of the statements.

594 The Last Run Date should be updated for queries run as subqueries.


KB_SQL ODBC Driver Fixes KBS

Number


1050 Connections can be refused if multiple simultaneous connections attempts occur and the server process is overwhelmed. We have added re-try logic to the connection handler to compensate for this situation.

1011 The ODBC Driver installer no longer installs the Microsoft Data Access Components (MDAC). If these are not included with your Microsoft Windows installation, the files can be downloaded directly from Microsoft at http://www.microsoft.com/data.

1002 When retrieving data from TEXT columns, the ODBC Driver could cause corruption in the data. This happened in situations where the application attempted to retrieve small chunks of text that were less than the GVMAX setting on the server. For example, ADO.NET uses a chunk size of 201 characters. This could cause the 201st character of a TEXT result to be corrupted.

Note: The KB_SQL ODBC Driver v4.5 requires the latest version of the KB_SQL Server v4.5.


http://www.microsoft.com/data

KB_SQL QRE Professional Fixes

KBS Number


1121 When using the Explorer to Browse tables, views, and stored procedures, you can now request a vertical display of a single row. While in the Navigator, highlight the desired row and press the right-click button. Select the “Show Fields” option to see a vertical display.

1116 You can now use the QueryReferences option to search for queries that use METHODS.

1102 When using the Evaluate option with Procedures or Functions, the input form will attempt to protect you from errors. The [Execute] button will be disabled until you complete the data input with the closing right parentheses. A Tool tip “hint” will appear if you hover over the input area.

1096 When attempting to create a new password via QrePro, the messages are corrected to match those that would appear for the same operation done on the server.

1085 The About window shows the correct version number as 4.5 1084 A problem was corrected that prevented change of user

passwords.

1083 A problem was corrected that caused QrePro to hang if the first activity was to create a new query.

1082 A problem was corrected so that QrePro will handle errors in READ LOOKUP commands.

1079 A problem was corrected in the feature that allows the creation of a “Select All Query” from the Explorer. Foreign keys are now correctly identified regardless of naming convention.

1073 New option added to allow quick syntax check and data dictionary object resolution. See File|Parse Query option.


1071 Query Editor supports code-completion. Once a query has been successfully prepared, the list of tables becomes available for code-completion. This also includes aliases. Schema. (e.g., SQL_TEST.) -- brings up list of tables in schema Schema.Table. (e.g., SQL_TEST.EMPLOYEES.) -- brings up list of columns in table Table. (EMPLOYEES.) -- brings up list of columns in table Alias. (EMPS. – assuming EMPS is used as an alias on FROM clause) -- brings up list of columns in table

1070 New features added to Query Editor.

• Comments - single and multiple line can be commented / uncommented

• Bookmarks - set and return to multiple bookmarks (placeholders)

• Keywords – full or partial match lookup keywords Add new features in query editor on Edit menu. - Comments [F8] [F9] - Bookmark [F6] [F7] - Category List [F2] - Keyword list [CTRL+J]

1066 FileImage Inspector will now detect an illegal filename provided via the SET FILE parameter. An error message will be presented. The user must fix the filename or abort.

1059 New options for Explorer Copy menu for Syntax: Commands -> partial command syntax illustration FileTypes -> SET FORMAT = 'name' Methods -> SET METHOD = 'name' OutputFormats -> FORMAT 'name' Parameters -> name = StartDateRules -> SET START_DATE = 'name'


1058 Query properties option will correctly limit the length of query name values to 30 characters.

1049 A Copy menu option is added to the Explorer. This will expose the options available via drag-and-drop making the feature more obvious.

1048 Exit of QueryProperties function could remove query name. This is now correctly handled.

1046 The Explorer now allows searching across all objects in the repository. Right-click on the very top node and select the Find option. A list will be presented of objects found along with their name, type, and description.

1044 New system tray application, KBS Download Agent, automatically saves File Images saved using the SQL_FILE_IMAGE method and with a filename specified using the SET FILE parameter.

1025 The Explorer drag-and-drop will no longer put spaces around the text to be pasted into the query editor.

1024 The Explorer can show Index tables. Note that the default is for Index Tables to be off. To enable Index Tables currently requires setting the Registry Key as shown below. HKEY_CURRENT_USER\Software\Knowledge Based Systems\Explorer\SkipIndices = No Note that this change requires you to also refresh the repository for the affected tables, or for all tables.

1023 File Image Inspector will show the filename for images that have a SET FILE parameter, regardless of whether the image has been saved.

1005 File Image Inspector will dim menu options that are not available. This affects the Tool Bar options as well.

993 The Explorer can search for Query References on all relevant object types in the repository. A list of queries is presented, from which the user can make multiple selections prior to closing the form. Note that to open queries you need to point to them with the mouse pointer and right-click. A single menu option named “Open Query” will appear. Select this option and the query should be opened in the query editor. Continue this process for all queries that you want opened, and then close the form.

985 The new query name will now show in the File Image list for queries whose name is changed since the image was created.

972 The Explorer allows Stored procedure result sets to be browsed like tables and views.


971 The Explorer allows Stored procedures that don’t return result sets (e.g., Insert/Update/Delete) to be executed.

970 The Explorer now allows Functions to be evaluated using inputs specified by the user.

969 The Explorer now shows PseudoColumn values in the Properties window.

968 The Explorer is enhanced to allow browsing of live data for Tables, Views, and Stored Procedures.

938 An all new “Navigator” component is in use by the Explorer. The Navigator allows for a free form query result to be browsed with very quick feedback to the user.

878 Explorer repository load can be cancelled, reverting to previous repository.

877 Show status information during loading of Explorer repository. 738 The speed of loading the data dictionary repository has been

improved for non-DBA users. Note also that the repository is always loaded completely in a single step.

618 The Functions list is filtered to restrict access to hidden functions as well as functions that require a specific MUMPS type. These functions are still available to be included in SQL statements (where applicable), but are not shown in the list.

617 The Explorer Find window can be resized and the position saved for future use.


KBS JDBC Driver Fixes KBS

Number


1065 A problem was corrected with the processing of long TEXT type values where the data contained the colon character.

1060 A problem was corrected with the SQLFreeStmt() message as it was using the wrong parameter set.

1052 The driver now correctly handles failed connections. Note: The KBS JDBC Driver v4.5 requires the latest version of the KB_SQL Server v4.5.


KBS Download Agent Fixes KBS

Number


1123 A problem was corrected that affected the use of the user-directory versus the application-install directory. In addition to creating log files and saving preferences in the wrong places, this error could have prevented the Help option from working.

1103 Log files are cleaned up to ensure that Image Id values are displayed correctly.

1101 Images are processed in first-in-first-out order. 1095 On uninstall, preferences and log files are removed. 1089 Preferences are stored in encrypted formats. 1086 An error will be reported for any File Image saved with a

filename that would be illegal to save to the client file system. This includes: - no path specified - non-existent path specified - existing file (if Overwrite mode is disabled)

1072 A problem was corrected with the KBS JDBC Driver in how it retrieved TEXT Data. This affected the KBS Download Agent as this application uses the KBS JDBC Driver for connectivity.

Note: The KBS Download Agent requires the Java Runtime Environment (JRE)


KBS eService Center Fixes KBS

Number



Known Problems Below are some of the known problems that still exist in this release. For updates on these or other known problems, please visit our website.

KB_SQL Server Known Problems KBS

Number

Customer Incident # Answer ID

1019 Views with fully qualified columns can generate ‘818: Fixed value Predicate’ errors. We have duplicated the "Fixed value predicate" error with the following queries: CREATE VIEW AA (EMPNAME) AS SELECT SQL_TEST.EMPLOYEES.NAME FROM SQL_TEST.EMPLOYEES SELECT * FROM AA WHERE EMPNAME IS NOT NULL As a workaround, please do not include the schema name on the reference to the columns in the SELECT clause.

955 The LIKE and FIND functions can fail to find strings when the value is split across nodes in the temporary storage area. This can sometimes be overcome by using a large value for the GVMAX setting.

874 SQLColumns reports incorrect COLUMN_SIZE for view columns based on expressions. This error manifests itself in MSAccess by retrieving only 20 characters (the default size) for view columns based on expressions. The problem is that SQLColumns can only retrieve the column size from the base_column definition. In the case of an expression, there is no base_column reference.

760 In some circumstances, when a query is run from the background queue, and that query has to be compiled, the query can run without being “locked”.


KBS Number

Customer Incident # Answer ID

712 The query planner can sometimes consider “bad” plans despite an apparently high setting for the COST_CEILING parameter.

694 In some cases, where two adjacent tasks in the background queue run the same query, and that query is open for editing, the background queue will be stalled until that query lock is released.

614 In some cases, illegal event block command references can go unnoticed by the SQL language parser. An example is the typo “INTIAL” meant to be the INITIAL event. The parser goes right past this without a warning.

572 In some cases, tables submitted to the statistics queue using a non-zero sample size can remain in the queue, trying over and over to calculate stats.

455 In some cases, views using an outer join query that includes a constraint on the non-preserved table, can fail.

363 Accessing tables with 'Programmer Only' columns via SQL Server linked server can return the following message:

Server: Msg 7355, Level 16, State 1, Line 3 OLE DB provider 'MSDASQL' supplied inconsistent metadata for a column. The name was changed at

execution time.

508

260 The TCP/IP testing utility, TEST^SQL0TCP, is not implemented for the MSE version.

92 The QUERY_COMMAND table (72) can sometimes grow without bound when processing of DML queries against user defined tables. We have added some controls to try to limit this problem, but don’t have the full correction.

8 In some cases, the JOB WATCH utility cannot stop a running query because the halt check threshold is never reached.


KB_SQL ODBC Driver Known Problems KBS

Number


1040 Memory management failures can occur with large query results where each row has TEXT data.


KB_SQL QRE Professional Known Problems KBS

Number


805 There is a pop-up menu including options such as ‘Delete’ that is raised from a right click after using the File|Open Query option. When the same functionality is raised from the Query Manager “Search” option, the pop-up options do not appear.

759 There can be a number of blank lines apparently “wasted” at the bottom of the Table Print when printed from QRE Pro.

749 From the Dictionary Explorer, the refresh date and time details are not always correct.

526 The “Mark All” feature doesn’t always clear previously marked items when doing additional searches.

150 If the TCP/IP connection is broken, QRE can become unresponsive.


KBS JDBC Driver Known Problems KBS

Number


1092 Driver fails on SuccessWithWarning messages during connection attempt. It should make these messages available to the application, but it should not treat it as a fatal error.

1072 Driver needs to inform server of driver type (JDBC) and driver version during connection.

1056 Driver needs to allow multiple attempts to achieve TCP/IP connection during the connect request.


KBS Download Agent Known Problems KBS

Number



This page intentionally left blank.


Documents

KB SQL Release Notes Version 4 - Oracle · KB_SQL Release Notes Version 4.5 Knowledge Based Systems, Inc. Last Updated: Tuesday, March 21, ... KB_SQL Server Query locking algorithms