KB_SQL Release Notes Version 4.3.Q2. Knowledge Based Systems, Inc.

Transcription

1 KB_SQL Release Notes Version 4.3.Q2

2 Copyright 2003 by All rights reserved., 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, 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 Professional Plaza, Suite 230 Ashburn, Virginia WWW KB_SQL is a registered trademark of MUMPS is a registered trademark of the Massachusetts General Hospital. All other trademarks or registered trademarks are properties of their respective companies.

3 TABLE OF CONTENTS INTRODUCTION... 1 NEW FEATURES... 2 KB_SQL SERVER... 2 Support for Multi-line Comments... 2 Support for User Authentication... 3 Stored Procedures to Add Groups and Users... 5 KB_SQL ODBC DRIVER... 7 Password Encrypted in ODBC Connection... 7 QRE... 8 Foreign Keys Can Be Dragged and Dropped from Explorer... 8 QRE Usage Manuals Accessible from within QRE... 9 FIXED ITEMS KB_SQL SERVER FIXES KB_SQL ODBC DRIVER FIXES QRE FIXES ESERVICE CENTER FIXES KNOWN PROBLEMS KB_SQL SERVER KNOWN PROBLEMS QRE KNOWN PROBLEMS... 23

4 Introduction The Version 4.3.Q2 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

5 New Features KB_SQL Server Support for Multi-line Comments Multi-line comments in a query are now supported. Comment text should be enclosed within /* and */ tags. For example, /* Enter comment text between the beginning and ending comment tags. */ SELECT NAME FROM EMPLOYEES Important Notes: The previous syntax (--) will continue to be supported for comment lines that are <= 80 characters long. We recommend using the syntax for long comments if the comment length exceeds 80 characters. Comment types can be mixed within a query. For example, /* This query returns information about the projects that have a budget greater than $50,000 per year. */ SELECT PROJ_NO, PROJECT, LEADER, BUDGET FROM PROJECTS -- Restrict results to rows with a budget over WHERE BUDGET > Comments can be nested within other comments. 2

6 Support for User Authentication Beginning with version 4.3.Q2, server-side ^SQL entry points may require a username at login. The optional site parameter can be configured by setting the Require username at login? field under Configuration Site Edit Default Info. By default, user authentication disabled. Setting the Require username at login to Yes will require that the user provide a valid username and matching password when attempting to access any of the ^SQL entry points. Setting the Require username at login to No will prompt the user for a password. Resulting feedback if user authentication is enabled. Input at login Result A valid username and valid Logged in password No username The No User message displays: Username: No User A valid username and no password The No User message displays: Username: DBA Password: No User An invalid username The Enter a valid user username message displays and the user is prompted for a username again: Username: ABC Enter a valid user username Username: 3

7 Input at login A valid username with an invalid password: Result The Enter a valid user password message displays and the user is prompted for a password again: Username: DBA Password: Enter a valid user password Password: Programs that provide SQLUNAME and/or SQLAUTH values for API entry points should be aware of the following: 1. If a SQLUNAME is not provided, no username authentication is performed. As in previous versions, only the password provided by SQLAUTH will be verified. 2. If SQLUNAME is provided, it will be verified. 4

8 Stored Procedures to Add Groups and Users Several new stored procedures have been added to create and delete KB_SQL user groups and users. For additional information on these stored procedures, please see answer 496 in the online knowledge base. SQL_SP_USER_GROUP_ADD Creates a new user group. Required Argument Description Argument Group name The name of the group to be added. The group name must be unique and a valid SQL identifier. Default schema* An existing schema name that will be the default schema for the group. Base routine prefix An existing base routine prefix. Note that if no value is provided, the site s base routine prefix (Configuration Site Edit M Info) will be used for the group. SQL_SP_USER_GROUP_DELETE Deletes an existing user group. Required Argument Description Argument Group name The name of the group to be deleted. SQL_SP_USER_ADD Adds a new user. Required Argument Description Argument User name The name of the user to be added. The user name must be unique. Password A password for the user. The password must be unique within KB_SQL and must be <= 30 characters. 5

9 Group name The name of the group to which the user will belong. The group name must already exist in KB_SQL. SQL_SP_USER_DELETE Deletes an existing user. Required Argument Description Argument User name The name of the user to be deleted. 6

10 KB_SQL ODBC Driver Password Encrypted in ODBC Connection Previous versions of the KB_SQL ODBC Driver did not encrypt the password when sending the TCP/IP packet to the server. SQLConnect("KB_SQL Data Source","dba","SHARK") = (0,"100034") Figure 1. Network packet capture without encryption Version 4.3.Q2 and future versions of the KB_SQL ODBC Driver will send an encrypted password as shown in the following trace and network packet capture SQLConnect("KB_SQL Data Source","dba","X ","1") = (-1,"100034") Figure 2. Network packet capture with encryption In order to take advantage of the ODBC Driver s password encryption, the Server must be running version 4.3.Q2 or higher. 7

11 QRE Foreign Keys Can Be Dragged and Dropped from Explorer Foreign key links are now included in the list of table columns. This allows for foreign key links to be dragged and dropped to the query area. The foreign keys will continue to be listed in the Extended Properties window: 8

12 QRE Usage Manuals Accessible from within QRE The QRE Usage Manuals are now accessible from within QRE. The manuals are installed with QRE and are provided in Adobe.pdf format. To access the manuals, select the Help QRE Professional/Standard Usage Manual menu option. 9

13 Fixed Items This section has been categorized based on the affected component. KB_SQL Server KB_SQL ODBC Driver QRE Within each section, a table below lists the key items that were fixed in version 4.3. The following information is included: Description This is a high level description of the problem. Customer Incident # As customers submit issues to KBS support, each customer is given a unique identifier for their incident. This column represents the incident numbers that were assigned to individual reports of the problem. Online Knowledge Base Answer ID In situations where additional documentation is available, the information can be found in the online knowledge base using the Answer ID provided. If you do not have an account to the online knowledge base, please contact us at info@knowledgebasedsys.com to request an account. To search the online knowledge base with the provided id: 1. Log on to the online knowledge base at 2. Select the Answers tab. 3. In the Search Text field, enter the answer id. 4. Select Answer ID from the Search by list. 10

14 5. Click the Search button. For a complete update of incidents submitted by your company, please log onto our web site at and select the My Knowledge Base tab. 11

15 KB_SQL Server Fixes Problem Description (4) Multi-line comments were not supported. Please see the New Features section for more information. (18) A stored procedures created by a non-dba user could not be called by the user. (32) The number of non-zero digits available after division in MSE has been expanded to ten. To illustrate, the following query Customer Incident # Online Knowledge Base Answer ID SELECT ROUND(100/6, 10) FROM SQL_ONEROW Returned in versions prior to 4.3.Q2. In version 4.3.Q2, the query returns (63) By default, the Integrity Check in MSE will look for data dictionary entries with null subscripts. Any null subscripts in the ^SQL global that are found will be dropped and recorded in the Integrity Check Log as DROP NULLSUB errors. 534 If needed, the check for null subscripts can be disabled by setting SQLX("NO_NULLSUB") before running the Integrity Check (125) Committing changes, or lack of changes, to a table in Map Existing Globals was unnecessarily regenerating statistics on a table that had not had changes to its primary keys

16 Problem Description (298) Verbose transaction logging can be disabled at either the query level or the site level. By default, verbose transaction logging is enabled. To change the site level setting, set the Suppress verbose transaction log detail under Configuration Site Edit Date/Time Limits. To enable/disable verbose transaction logging at the query level, set TXLOG_VERBOSE appropriately. For example, the following query runs with verbose transaction logging disabled: SET TXLOG_VERBOSE OFF SELECT NAME, SALARY FROM EMPLOYEES Customer Incident # Online Knowledge Base Answer ID 536 (325) A new pseudo column, QRE_TITLE, has been added to allow users to query the site s display text for the QRE title bar. (408) The If Needed option has been modified to only regenerate statistics if either of the following are true: (a) The table s primary key definition was accessed (regardless of whether or not changes were made). (b) A primary key column was accessed (regardless of whether or not changes were made) (471) The EVERYHOUR start date was not properly padding the time value in ANSI causing queries to miss scheduled runs after midnight. (475) Sites that journaled the ^SQL global were journaling large structures such as ^SQL(77) that did not need to be journaled. Beginning with 4.3.Q2, the data that was stored in ^SQL(77,SQL(2),50) will be stored in the temporary global ^SQLXX($JOB,"Text")

17 Problem Description (478) Entries in the DESCRIBE_QUERY table (^SQL(611)) were unnecessarily being stored for file download queries. Customer Incident # Online Knowledge Base Answer ID (482) Compile All Queries now provides an option to specify queries that were run within a user-specified date range. (487) The DDL interface did not check the lengths of object names being created and incorrectly allowed for names > 30 characters. (490) The product did not provide an option to authenticate user names on the server interfaces. Please see the New Features section for more information. (491) There was no programmatic API for adding or deleting users. Please see the New Features section for more information. (496) There was no programmatic API for adding or deleting user groups. Please see the New Features section for more information (501) The user password field has been expanded to allow for passwords up to 30 characters long. (504) SQLFreeStmt Close was not clearing parameter conversion results (506) Several new functions have been added to return the first day, first weekday, last day, and last weekday of the quarter. New start date rules have also been added to schedule a query to run at quarterly intervals , 556 (508) Running a query that sends output to file without a filename caused an invalid error to be displayed for SQL Editor queries during the session

18 Problem Description (509) The Query Transaction Detailed Log incorrectly showed 25 rows rejected instead of the actual number if the number of rows rejected exceeded 25. (521) Site s that had the Nothing to Print message enabled encountered an error at 2^SQL0OUT if a query with no results was run to the background. (522) In EZQ, constraining on a foreign key column using a numeric with a decimal value incorrectly displayed the error "Invalid INTEGER". (550) Importing a table that had been made inactive caused the table to not be accessible. (551) The PLANNER_MAX_COST_CEILING site setting added in 4.3.Q1 did not have an associated window where its value could be viewed and modified. Customer Incident # Online Knowledge Base Answer ID (552) Custom code can be executed when a query is deleted from the query queue (558) The host file name handler was returning a nondescriptive 999 message instead of the 0732: Illegal filename error message. (560) A new parameter, COST_CEILING, has been added to allow a query s cost ceiling to exceed the site s specified cost ceiling. 563 (561) Tables with a sample size of 0 were incorrectly being resubmitted to the statistics if the difference between the base table s row count and index table s row count exceeded 75%. (564) The ALTER RENAME syntax in SQL Editor was not checking the length of the new name to ensure that it did not exceed 30 characters

19 Problem Description (566) RESET^SQL was not removing the background queue, compile queries, statistics, or user locks. Customer Incident # Online Knowledge Base Answer ID (567) No menu options were available to clear the statistics queue or error log. (569) Once the 0239: Device <value> is not a printer message occurred, it incorrectly displayed for all queries in SQL Editor until the user skipped out of SQL Editor and re-entered. (570) The SQL_FN_TIMESTAMPADD and SQL_FN_TIMESTAMPDIFF functions for week, month, quarter, and year intervals were corrected , (571) Sending a query to run in the background did not provide any feedback as to the time or date that the query was set to run. In addition to the 0811: Query execute has been added to the background queue message, a new message, 898 will be returned that includes the date, time and start date if applicable for when the query is scheduled to run. (573) The ELAPSED_TIME output format was not associated with the TRANSACTION_LOG.TOTAL_TIME column

20 KB_SQL ODBC Driver Fixes Description (1) If the default description for a version 4.x KB_SQL ODBC Driver had been changed, the installer was overwriting the modified description during an upgrade. (489) Passwords were not encrypted when the TCP/IP packet was sent to the server. Please see the New Features section for more information. Customer Incident # Online Knowledge Base Answer ID

21 QRE Fixes Description (11) The Find dialogue has been simplified so that both object names and their descriptions are searched. (14) The status bar displayed while refreshing the Repository did not provide an accurate representation of the amount of time remaining for the refresh. Customer Incident # Online Knowledge Base Answer ID (33) Queries created, altered, or dropped from QRE were not logged in the Query Transaction Log. (68) The QRE Usage Guides were not available from within QRE. (80) A new method, GetKBSUID, has been added to QRE Services to return the KBSUID from KB_SQL (83) If the \data directory did not exist when a user attempted to create a new draft query, an error was returned. (325) Additional information, such as the server identifier, can be added to the QRE title bar (356) Foreign key links were not available for drag and drop from the Explorer window. Although they were viewable from the Extended Properties window, they could not be dropped into the query area. (358) The values displayed for the "Columns", "Foreign Keys Out" and "Foreign Keys In" in Extended Properties are not listed in alphabetical order. (371) Columns returned by a Repository search did not include the column description

22 Description (396) The default width of the Queue Inspector columns Query, User, Rule, and Status were not wide enough to accommodate the longest possible value. (402) When running a query to a host device, the cursor was not automatically positioned in the Device Name field. (403) Underscores in comment lines were not always visible depending on the cursor s position within the query text. (424) The Host Device Dialog s partial device lookup was not displaying the complete device name in the Device Name field. (434, 466) The device name column was not wide enough to accommodate the entire device name in the Host Device Dialogue. (459) Tasks were not deleted from the background queue if they were selected from the bottom of the list up. (469) The New Query Properties Dialog was not being cleared after an invalid entry. (470) The list of available host devices was being repopulated each time a query sent output to a host device. For sites that had a large number of devices (>1000), the repopulation of the device list was slow. (486) A regular expression entered in the Find window was not being preserved after a match was found. (488) The 767 Query references table(s) without statistics" message was not displayed in QRE. (493) The installer has been updated to install a customized version of the CodeMax Edit control called kbsedit.ocx. Customer Incident # Online Knowledge Base Answer ID 19

23 Description (497) A table name that exceeded the 30 character limit caused the repository refresh to generate the following error: Error Number: Source Module: KBSExplorer Description: A string literal was not closed. (510) Table Print generated 6-8 extra lines of whitespace at the bottom of each page of output. (528) The keyboard shortcut to display the Replace window was incorrectly displaying the Find window. Customer Incident # Online Knowledge Base Answer ID 20

24 eservice Center Fixes Description The Answer ID was not displayed in the answers list. (520) QRE Professional, QRE Standard, and QRE Services were listed separately. The three products are now listed as sub-products of QRE: The information displayed for an answer has been simplified to show only pertinent information: 21

25 Known Problems Below are some of the known problems that still exist in version 4.3. For updates on these or other known problems, please visit our website. KB_SQL Server Known Problems Description (8) Job Watch does not stop a running query. (13) It is possible for some errors to exceed the width of the display box used to display error text. This causes the error message to become truncated. (78) There are certain situations in MSE that cause the IN clause to not be optimized. (255) Virtual columns defined with foreign key references beyond the first level of foreign key indirection have the potential to be incorrectly evaluated. (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. Customer Incident # Online Knowledge Base Answer ID (455) An outer join view with a constraint on nonpreserved table can fail with a <SUBSCRIPT> error. (468) A query run from a batch query cannot be commented out after a parsing error occurs (500) <STACKCRIT> errors can occur if error trapping logic is called recursively in GT.M. 22

26 Description (507) If a query in the queue is changed, the query is recompiled when it is time for it to run. However, the query output is not sent to the device. (524) The Query Transaction Detail report prints "Nothing to Print" when run in the background in MSE. Running the report in foreground produces results. (574) Running NOTRAP^SQL0LOAD on GT.M can fail if the site does not have a SQLSCR.2 file. Customer Incident # Online Knowledge Base Answer ID QRE Known Problems Description (7) The "Refresh This Node" at the schema level has no affect on its underlying objects (tables, columns, indices, views, and stored procedures). The only way to get underlying objects to reflect an update is to specifically select the object type before selecting "Refresh this Node". (526) Using the Edit > Find/Mark All feature more than once on a query does not clear the arrows from the previous Mark All. Customer Incident # Online Knowledge Base Answer ID 23