Table of Contentskbs.custhelp.com/ci/fattach/get/4840/0/filename/KBSQL...KB_SQL Version 5.3 Release Notes 4/13/2011 9:10 AM KB_SQL Version 5.3 Release Notes 4/13/2011 9:10 AM page

KB_SQL Version 5.3 Release Notes 4/13/2011 9:10 AM

KB_SQL Version 5.3 Release Notes 4/13/2011 9:10 AM page 1

Table of Contents KBS eService Center (http://www.kbsreporting.com/support) ................................................................... 4

2413: Bug:Incidents do not [Print] properly ............................................................................................. 4

2506: Enh:KBS eService Center to support mobile devices ...................................................................... 4

KBS.NET Download Agent ............................................................................................................................. 5

2421: Enh:DownloadAgent - allow specific start time for interval ........................................................... 5

2419: Enh:DownloadAgent - Allow Log File management ....................................................................... 5

1154: Enh:Download Agent to allow user-defined 'Purge' settings ......................................................... 5

2531: Enh:Allow KBS Download Agent to run as a service ....................................................................... 5

2556: Bug:Reduce volume of messages in log .......................................................................................... 5

KB_SQL ADO.NET Provider ............................................................................................................................ 6

2425: Enh:ADO.NET Provider to support older servers ............................................................................ 6

KB_SQL JDBC Driver ...................................................................................................................................... 7

2477: Enh:Allow JDBC Driver to connect to older servers (back to v43) .................................................. 7

2485: Bug:JDBC Driver to support wasNull() operation ........................................................................... 7

KB_SQL ODBC Driver ..................................................................................................................................... 8

2426: Bug:ODBC Driver fails memory save via ODBC.NET Connection .................................................... 8

QREPro Desktop ............................................................................................................................................ 9

2386: Enh:Enable Syncfusion editor feature for maximum line length .................................................... 9

2402: Enh:Incorporate new license of Syncfusion into development environment ................................ 9

2404: Bug:Incorrect references to History and Log files .......................................................................... 9

2405: Query Copy fails on column QUERY_TEXT ...................................................................................... 9

2470: Enh:Clear history both external file and memory copy .................................................................. 9

2496: Enh:Enable cross-reference of queries by column ......................................................................... 9

2512: Bug:Function SQL_FN_QRE_TABLE_PRIVILEGE error ..................................................................... 9



2513: Bug:System function SQL_FN_SCHEMA_HAS_PROCEDURES error .............................................. 10

2529: Enh:Allow same user from same session or client address jump lock ......................................... 10

2557: Enh:New procedure to View/Print Query Folder List ................................................................... 10

KB_SQL Server ............................................................................................................................................. 11

2409: Bug:Queue Manager cleanup MGRCLEAN fails ............................................................................ 11

2410: Bug:Queue Manager worker fails to start on DSM ....................................................................... 11

2411: Bug:Illegal WHEN syntax causes infinite loop in Parse ................................................................. 11

2414: Bug:Top line comment for SQLR* routines is always the same.................................................... 11

2416: Bug:Variable scope error in SQLDescribeCol for MSE .................................................................. 11

2417: Enh:Add transaction logging for @SERVER_nnnn queries ........................................................... 11

2418: Enh:Capture input parameters used with @SERVER_nnnn queries ............................................ 12

2422: Enh:Move TRANSACTION_LOG data to alternate global .............................................................. 12

2455: Bug:On GT.M Save routine with different object directory .......................................................... 12

2456: Bug:TRANSACTION_LOG QUERY_START_TIMESTAMP can be incorrect ...................................... 12

2457: Bug:TRANSACTION_LOG.TOTAL_TIME generates value > 86400 ................................................. 12

2458: Bug:Integrity Check should run with System Lock set .................................................................. 13

2482: Bug:On GT.M, alternate port needs to timeout if no connect attempt ....................................... 13

2483: Bug:When optimizing object code, don't create GOTO lists ........................................................ 13

2484: Bug:Fix management of QUERY_DESCRIBE (611) table ................................................................ 13

2487: Bug:On GT.M, Server listener needs to reuse TCP Socket devices ............................................... 13

2490: Enh:Improvements to XFER interface to allow SQLXNM parsing ................................................. 13

2491: Enh:Test for Query already in queue on submission .................................................................... 14

2493: Enh:Modify BASE_ROUTINE_PRINT to show Free routine count/pct .......................................... 14

2494: Enh:Allow SQL_FN_CONCAT() function to follow behavior of || ................................................. 14

2498: Enh:Query Print report adds "History" section ............................................................................. 14



2504: Bug: External interface symbol table management ..................................................................... 14

2505: Enh:SQL Activity Inspector ............................................................................................................ 15

2507: Enh:Show query activity for a Date Window ................................................................................ 15

2510: Enh:Conditionalize warning messages for connected applications .............................................. 15

2511: Enh:Allow extended SQL domain references in CREATE TABLE ................................................... 15

2522: Enh:Save SQL QUERY TEXT in Transaction Log ............................................................................. 16

2527: Bug:SQLGetInfo for *_NAME_LEN could be too short ................................................................. 16

2528: Enh:Adjustments to list of audited tables. ................................................................................... 16

2545: Enh:System Status to show if Base Routines need check ............................................................. 16

2550 - Enh:New SITE controls for Transaction Log components ............................................................ 16

2551: Enh:Consolidate Transaction Log settings in SITE EDIT ................................................................ 17

2552: Enh:Improve handling of Unicode characters for locales ............................................................. 17

2553: Enh:Create a client aware version of QuickSQL ............................................................................ 17

2554: Bug:Transaction log creates double entries for ‘RUN query’ ....................................................... 17

2557: Enh:New procedure to view/print Query Folders ........................................................................ 17

2558: Enh:New Custom Start Date Rules ................................................................................................ 17

2559: Enh:New PseudoColumns ............................................................................................................. 18

2561: Enh:Show Query RunTime data .................................................................................................... 19

2564: Enh:Integrity Fix for SQL_FILE_IMAGE table ................................................................................. 19

2565: Bug:TRANSLATE function fails with integer replacement [MSE] .................................................. 19

2569: Bug:TCP/IP session can become corrupted by spurious output ................................................... 19



KBS eService Center (http://www.kbsreporting.com/support)

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.

2413: Bug:Incidents do not [Print] properly

A correction was made by RightNow Technologies, the provider of the KBS eService Center.

When printing incidents, the entire text will show. Previously, the text was being truncated.

Note that the behavior is tested in the newer versions of Firefox, Safari, Chrome, and Internet

Explorer.

2506: Enh:KBS eService Center to support mobile devices

The KBS eService Center is now available on your mobile device. You'll see the same

information including FAQs, your questions, etc. formatted properly for your mobile device.

This is the same information that appears via your desktop browser.

http://www.kbsreporting.com/support



KBS.NET Download Agent

The KBS.NET Download Agent enables the automatic save of File Images created via QREPro

Desktop. Note that the JDBC Download Agent provides similar functionality but is unchanged

in this release.

2421: Enh:DownloadAgent - allow specific start time for interval

We now allow the customer to set an explicit starting time for the download agent interval.

2419: Enh:DownloadAgent - Allow Log File management

The log file can get very large. We now allow the customer to configure an upper limit on size

(default=2mb) to keep. As we add messages to the log file, we will check to see if truncation is

required. If so, we'll truncate the oldest information.

1154: Enh:Download Agent to allow user-defined 'Purge' settings

The 'Purge' option is current defaulting to 'Yes'. We now allow the customer to control this setting using

the DownloadAgent|Preferences option.

2531: Enh:Allow KBS Download Agent to run as a service

The KBSDownloadAgent is updated to run as a Windows service. It is now possible to start the process

on a remote server and allow it to continue processing independently of any user login.

2556: Bug:Reduce volume of messages in log

We have reduced the volume of messages in the log file. Generally speaking, we add a message to the

log whenever a task is executed including:

- start service

- stop service

- request list of images // how many returned?

- Processing image // result

The goal is to make the log file easier to read and understand.



KB_SQL ADO.NET Provider

The KB_SQL ADO.NET Provider connects applications to KB_SQL Server using the .NET

protocols. We use the KB_SQL ADO.NET Provider to manage the connections from our own

QREPro_Desktop application.

2425: Enh:ADO.NET Provider to support older servers

The KB_SQL ADO.NET Provider is enhanced to allow connection to older KB_SQL Server

versions going back to KB_SQL Version 4.3. Note that this change affects only the baseline

driver. Certain applications that use the driver may still require a newer version of the KB_SQL

Server. An example of this is the QREPro application.



KB_SQL JDBC Driver

The KB_SQL JDBC Driver connects Java applications to KB_SQL Server.

2477: Enh:Allow JDBC Driver to connect to older servers (back to v43)

The KB_SQL JDBC Driver is enhanced to allow connection to older KB_SQL Server versions

going back to KB_SQL Version 4.3. Note that this change affects only the baseline driver.

Certain applications that use the driver may still require a newer version of the KB_SQL Server.

An example of this is the Download Agent application.

2485: Bug:JDBC Driver to support wasNull() operation

A correction was made to the JDBC Driver function WasNull(). This function was previously

returning TRUE in all cases. Now, it is corrected to return TRUE only when the value was

actually Null.



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

2426: Bug:ODBC Driver fails memory save via ODBC.NET Connection

A correction was made to the SQLDriverConnect() function in the KB_SQL ODBC Driver.

The ODBC.NET provider does not provide a valid pointer for the OutConnectionString or the

corresponding string length pointer. As a result, there is a possible memory corruption as part of

the connection process.



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.

2386: Enh:Enable Syncfusion editor feature for maximum line length

A new option is added to QREPro to allow the display and enforcement of a line length limitation. This

option can be set using the Tools|Options menu. The goal is to make it more clear how to edit queries

that are referenced both by QREPro and by SQL EDITOR. Since SQL EDITOR has an implied line length

maximum, we offer the same support in QREPro.

2402: Enh:Incorporate new license of Syncfusion into development

environment

A new version of the Syncfusion Editor Control is added to the QREPro application.

2404: Bug:Incorrect references to History and Log files

A correction was made to the file reference when using the QREPro Tools|Options settings to remove

'Log' and 'History' files.

2405: Query Copy fails on column QUERY_TEXT

A correction was made to the Query->Copy() function. Selecting a query in QueryManager and choosing

Copy from the popup menu produces the following error message: System.Data:Column 'QUERY_TEXT'

does not belong to table SQL_ONEROW. This has been corrected.

2470: Enh:Clear history both external file and memory copy

A correction was made to the QREPro Tools|Options function that clears the AutoComplete history. The

function will now correctly remove the copy from disk and memory.

2496: Enh:Enable cross-reference of queries by column

We now provide a cross-reference of queries by Table and View Column values. This allows users of the

Explorer in QREPro to find all queries that reference a specific column in a table or view. This improves

on the existing cross-reference of queries by table/view allowing a greater level of detail.

2512: Bug:Function SQL_FN_QRE_TABLE_PRIVILEGE error

System function SQL_FN_QRE_TABLE_PRIVILEGE() could return incorrect results for a TABLE. This would

cause the table to appear in the explorer listing when that table was not privileged for the user group.



2513: Bug:System function SQL_FN_SCHEMA_HAS_PROCEDURES error

System function SQL_FN_SCHEMA_HAS_PROCEDURES() could return incorrect results for a TABLE. This

would cause the table to appear in the explorer listing when that table was not privileged for the user

group.

2529: Enh:Allow same user from same session or client address jump lock

If a timed lock remains on the server due to a hard error, we now allow it to be "jumped" if the same

user tries to open the query from the same session or from the same client address.

2557: Enh:New procedure to View/Print Query Folder List

A new report is created to provide a view/print listing of query folder content. The report is accessible

on the server using the \UTILITIES\REPORTS\QUERY FOLDER LIST procedure. The same report can be

accessed from QREPro Desktop using the Folder | View Report option.



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.

2409: Bug:Queue Manager cleanup MGRCLEAN fails

A correction was made to the logic that cleans up dormant Queue Manager Process data. The goal is to

validate the list appearing in JOB WATCH.

2410: Bug:Queue Manager worker fails to start on DSM

A correction was made to the Queue Manager Worker start logic on DSM environments.

2411: Bug:Illegal WHEN syntax causes infinite loop in Parse

A correction was made to the parser that affected MSE environments. In some cases, parsing errors

were encountered but not handled properly by the parsing code. This was happening when errors were

encountered in the processing of WHEN-THEN statements.

2414: Bug:Top line comment for SQLR* routines is always the same

A correction was made to the generation of the top line comment for generated queries. The top line

should now correctly reflect the name of the query as shown below.

--

V53>W $O(^SQL(155,-1,"DEMO_SELECT_ALL",””))

5457

V53>W ^SQL(155,5457,1)

~DEMO_SELECT_ALL~1~SQLR397~62039~49923~62081~50353~62039~49987~SQLR397~1~~~~

V53>W $T(+1^SQLR397)

SQLR397 ;DEMO_SELECT_ALL [KB_SQL V5.3.7985];12/21/2010@13:59:13

2416: Bug:Variable scope error in SQLDescribeCol for MSE

A correction was made to the SQLDescribeCol() function that affected the MSE environment. The

variables DD,SST,NRC were saved but not killed in certain circumstances.

2417: Enh:Add transaction logging for @SERVER_nnnn queries

We now save a query run transaction for Server API queries. This is done to provide a more complete

record of SQL activity through the query transaction logging feature. Note that Server API queries are

potentially more dynamic that regular stored queries. If you have a small queue with a lot of activity,

the actual query instance can be changing. When you see @SERVER_0123 in the query transaction log,



check the content of the query by copying this query into a new one to make sure you are evaluating the

proper SQL statements.

2418: Enh:Capture input parameters used with @SERVER_nnnn queries

We now capture input parameters for Server API queries. These query run instances are made available

on the Transaction Log reports.

For example:

Instance: SQL_SP_COLUMNS(@ColumnName='NAME')

2422: Enh:Move TRANSACTION_LOG data to alternate global

The TRANSACTION_LOG (209) table data is moved into the alternate global of ^SQLXH. This further

reduces the activity in the journal files that is tied to temporary and/or transaction related activity. Be

sure that your journaling rules exclude all globals except for the primary ^SQL global. This will have a

positive effect on query run performance.

2429: Bug:NULLSUBS fails on M21 error trapping

The error trap set/clear code is corrected for M21 environments. There was a problem encountered

while running the NULLSUBS tag in the SQL0H routine at installation time. This has been corrected.

2455: Bug:On GT.M Save routine with different object directory

A correction was made to the routine save logic used with the GTM environment. We were incorrectly

saving the object code in the same location as the stored source code. We now use the proper behavior

so that the source and object code can be stored in different folders. Note that during installation, you

will have the opportunity to enter paths for routine source and object code.

GTM>w $zro /mygtm/v53/objects(/mygtm/v53/routines) /usr/local/gtm …SQL0LOAD… Routine directory: /mygtm/v53/routines/ Object directory: /mygtm/v53/objects/

2456: Bug:TRANSACTION_LOG QUERY_START_TIMESTAMP can be incorrect

We have made some corrections to the way that query run transactions calculate their processing time.

There were a couple variants of the logic which have now been centralized.

2457: Bug:TRANSACTION_LOG.TOTAL_TIME generates value > 86400

A correction was made to query transaction log TOTAL_TIME values. In some cases, the time was

recorded incorrectly as a timestamp instead of seconds. This made the actual run time appear to be

several orders of magnitude more than reality.



2458: Bug:Integrity Check should run with System Lock set

A correction is made to allow the Integrity Check procedure to be initiated when the System lock is set.

Previously, the System lock would have to be cleared in order to run the Integrity Check.

2482: Bug:On GT.M, alternate port needs to timeout if no connect attempt

A 60-second timeout is added to the TCP/IP Listen process for alternate port connections. If the client

fails to connect on the alternate port in 60-seconds, the process will abort and exit.

2483: Bug:When optimizing object code, don't create GOTO lists

A minor correction is made to the routine object code optimizer to avoid generating unreachable code

with GOTO statements. Previously, when collapsing GOTO expressions, we could end up with a line like

'GO 1,2' where clearly it could never reach tag 2.

2484: Bug:Fix management of QUERY_DESCRIBE (611) table

A correction is made to the management of the QUERY_DESCRIBE (611) table. This table is used to

describe the result set columns for a query. There were some indexing issues that have been corrected.

2487: Bug:On GT.M, Server listener needs to reuse TCP Socket devices

A correction is made to the TCP/IP interface for GTM environments. When closing the listening

connection, we needed to reuse the GTM TCP device. Otherwise, we were wasting memory that could

eventually cause problems. This was especially evident on systems with a lot of query transaction data.

2490: Enh:Improvements to XFER interface to allow SQLXNM parsing

An enhancement is made to the Object Transfer (XFER) utility. We still allow the creation of an export

list by adding specific entries in the XFER globals. We now allow these lists to be dynamically created

based on parsing of the input variable SQLXNM. This variable can include zero or more ranges (using

either ':' or '-') and pattern matches (using '*'), with multiple groups separated by the semi-colon

character.

For example, to export all queries in the name range of B through G, plus all queries with names

matching X*, you could use the following setup.

>S SQLXTO="QUERY"

>S SQLXTM="TO_FILE"

>S SQLFILE="/tmp/export.qry"

>S SQLXNM="B:G;X*"

>D XFER^SQL



2491: Enh:Test for Query already in queue on submission

A new feature is enabled that will report either an error or an informational message if the user

attempts to submit a duplicate query to the background queue. Note that the logic takes into account

the set of input parameters provided with the query, such that query(':XDT=TODAY') is seen as different

from query(':XDT=YESTERDAY'). Each user is treated separately, allowing multiple users to submit tasks

that are identical.

The \CONFIGURATION\SITE EDIT\BACKGROUND TASKS option has a new prompt [Restrict duplicate

tasks?]. The default is 'No'. The default behavior is to provide an informational warning message.

-- 0932: Duplicate task --

Query=DEMO_FORMAT_COMMA/Task=300009/Date=12/22/2010/Time=05:00:00 PM

If the value is set to "Yes", any attempt to submit a duplicate task will be rejected with an error message.

-- 0931: Duplicate task --

Query=DEMO_FORMAT_COMMA/Task=300009/Date=12/22/2010/Time=05:00:00 PM

The goal is to limit redundant query executions.

2493: Enh:Modify BASE_ROUTINE_PRINT to show Free routine count/pct

The BASE ROUTINE LIST report is enhanced to show the number of free routines available for the

routine prefix. In addition, the report will indicate with an asterisk the base routine prefix that is

configured for the SITE.

2494: Enh:Allow SQL_FN_CONCAT() function to follow behavior of ||

A modification was made to the SQL_FN_CONCAT() function. We now allow the sql_fn_concat()

function to follow the behavior of the concatenation (||) operator. The implicit truncation at 255

characters is removed. Also, the function is extended to allow more than two argument values.

2498: Enh:Query Print report adds "History" section

A [History] section is added to the QUERY PRINT report. It shows a dated history of query run

transactions including the rows searched, selected, and processing time. We’ll show any input

parameters under the transaction record allowing you to see the combination of inputs that generated

the result.

2504: Bug: External interface symbol table management

There are a couple of external interface entry points that were adversely affected by a symbol table

management bug. We were not returning the required values.



Affected interfaces:

COMP^SQL

DDLI^SQL

EXDDLI^SQL

2505: Enh:SQL Activity Inspector

A new procedure is provided using the \TRANSACTION LOGS\QUERY TRANSACTIONS\QUERY TX

SUMMARY procedure. This new procedure provides a summary view of query run transactions. It

provides a summary showing a count of queries run along with statistics. It also allows you to break

down the transactions by User, Query, and Date. This procedure is provided to help diagnose query

performance issues.

2507: Enh:Show query activity for a Date Window

A new procedure at \UTILITIES\TRANSACTION LOGS\QUERY TRANSACTIONS\QUERY TX WINDOW allows user to provide a Date Window to search for query activity. This is provided as a tool to help diagnose performance issues that are reported for a specific date/time range.

2510: Enh:Conditionalize warning messages for connected applications

Error messages 818 (Fixed Value Predicate) and 659 (Cartesian Product) can get in the way of connected applications. These can also be useful for debugging when using the SQL EDITOR. These messages are only to be stored only when using the SQL EDITOR application.

2511: Enh:Allow extended SQL domain references in CREATE TABLE

SQL Syntax is updated to support extended DOMAIN names in CREATE TABLE command. This makes KB_SQL more cooperative with 3rd party applications that want to generate supplemental tables.

SQL_BIGINT-->INTEGER SQL_BIT-->FLAG SQL_CHAR-->CHARACTER SQL_DECIMAL-->INTEGER SQL_DOUBLE-->NUMERIC SQL_FLOAT-->NUMERIC SQL_INTEGER-->INTEGER SQL_LONGVARCHAR-->TEXT SQL_NUMERIC-->NUMERIC SQL_REAL-->NUMERIC SQL_SMALLINT-->INTEGER SQL_TINYINT-->INTEGER SQL_VARCHAR-->CHARACTER SQL_WCHAR-->CHARACTER SQL_WLONGVARCHAR-->TEXT SQL_WVARCHAR-->CHARACTER



2522: Enh:Save SQL QUERY TEXT in Transaction Log

A copy of the SQL Query Text is saved in the Transaction Log. Note that the SQL is saved only when it is the first Transaction entry for the day, or when the SQL text has been changed. Note also that SQL text will not be saved if the query has the TXLOG_VERBOSE setting turned OFF. The SQL will also not be saved for queries with HIDE_QUERY turned ON. The SQL Text will show on the QUERY TX DETAIL report.

2527: Bug:SQLGetInfo for *_NAME_LEN could be too short

Several SQLGetInfo type values attempted to retrieve values of the type _MAX_NAME_LEN and would return a hard-coded value of 30. Some applications would use this value as an absolute limit. This could cause truncation when the name included escape characters such as THIS\_NAME where the '\' character means that the following underscore (_) character is part of the name and not a meta character. The logic has been changed for the following InfoTypes so that the value returned is twice as long as the longest SQL identifier value.

SQL_MAX_COLUMN_NAME_LEN(30)

SQL_MAX_CURSOR_NAME_LEN(31)

SQL_MAX_OWNER_NAME_LEN(32)

SQL_MAX_SCHEMA_NAME_LEN(32)

SQL_MAX_PROCEDURE_NAME_LEN(33)

SQL_MAX_CATALOG_NAME_LEN(34)

SQL_MAX_QUALIFIER_NAME_LEN(34)

SQL_MAX_TABLE_NAME_LEN(35)

SQL_MAX_USER_NAME_LEN(107)

2528: Enh:Adjustments to list of audited tables.

The audit setting is removed for the following tables:

SQL_USER_QUERY (204) SQL_USER_TABLE(215)

This is done in order to remove unnecessary entries that are the result of low impact transactions. The result is to make the audit data more clear for those key tables that are in the audit set.

2545: Enh:System Status to show if Base Routines need check

The System Status will now show the status of Base Routine Prefixes. If all is well, it will simply show "Ok". Otherwise, it will show "Check!" with a list of one or more Base Routines that are 95% full. Use the \CONFIGURATION\REPORTS\BASE ROUTINE PRINT report to see the details. Use the \CONFIGURATION\BASE ROUTINE EDIT procedure to allocate new Base Routine prefixes as necessary.

2550 - Enh:New SITE controls for Transaction Log components

SITE configuration can control how much information is saved for query transactions.



SITE_DISABLE_TXLOG -- If you just don't want any transaction logging, period. SITE_TXLOG_VERBOSE_OFF -- If you want just the minimal transaction logging. (new) SITE_TXLOG_NO_SERVER_QUERY -- If you only want transaction logging for named queries, and NOT for queries generated from ODBC/JDBC/ADO.NET connections. (new) SITE_TXLOG_NO_SQL_STORE -- If you don't want to store SQL Statements with the query transactions. (new) SITE_TXLOG_NO_DIAGNOSTICS -- If you don't want to store diagnostics. (new) SITE_TXLOG_NO_OUTPUT -- If you don't want to store information about output. (new) SITE_TXLOG_NO_VARIABLES -- If you don't want to store information about query variables.

2551: Enh:Consolidate Transaction Log settings in SITE EDIT

The SITE EDIT procedure is updated to provide a central location for all prompts related to the TRANSACTION LOGS. See CUSTOM LOGIC/TRANSACTION LOG INFO.

2552: Enh:Improve handling of Unicode characters for locales

Special characters are stored using xml notation, such as € for euro. Utilities unwind and rewind

the stored data into the actual characters as needed.

2553: Enh:Create a client aware version of QuickSQL

QUICKR^SQL is a new utility QuickSQL-Remote. It allows connection to a remote KB_SQL Server.

Otherwise, it operates in the same manner as QUICK^SQL, except that it allows for remote testing of

KB_SQL Connectivity.

2554: Bug:Transaction log creates double entries for ‘RUN query’

When running a batch of queries such as 'run q1', there were double entries for the query being run.

(i.e., q1 in this case).

2557: Enh:New procedure to view/print Query Folders

A new procedure is added to allow view/print of Query Folders. See the \UTILITIES\REPORTS\QUERY

FOLDER PRINT procedure.

2558: Enh:New Custom Start Date Rules

Several new Custom Start Date Rules are added, including:

SQL_DAY_1 1st Day of month



SQL_DAY_10 10th Day of month










SQL_DAY_2 2nd Day of month


SQL_DAY_21 21st Day of month

SQL_DAY_22 22nd Day of month

SQL_DAY_23 23rd Day of month






SQL_DAY_3 3rd Day of month




SQL_DAY_7 7thDay of month



SQL_WEEK_1 Run weekly (every 7 days)

SQL_WEEK_2 Run every two weeks (14 days)

SQL_WEEK_3 Run every three weeks (21 days)

SQL_WEEK_4 Run every four weeks (28 days)

SQL_YEAR_1 Run on same date every year

2559: Enh:New PseudoColumns

Several new PseudoColumns are added, including:

sql_fn_date_today() -- Returns date of today

sql_fn_date_tomorrow() -- Returns date of tomorrow

sql_fn_date_yesterday() -- Returns date of yesterday

sql_fn_fy_month_start() -- Returns the FY Start Month



2561: Enh:Show Query RunTime data

The [History] section of the Query Print Report will show Run Times, including Average, Minimum, and

Maximum running times. The number of occurrences will depend on the number of entries retained in

the Transaction Logs.

2564: Enh:Integrity Fix for SQL_FILE_IMAGE table

The SQL_FILE_IMAGE data is stored in the ^SQLFI global. If the indexes become corrupt, you can reindex

the data by invoking the INTEG^SQLFI tag.

2565: Bug:TRANSLATE function fails with integer replacement [MSE]

On MSE, the TRANSLATE function is corrected to function properly when used with a String expression

as in TRANSLATE(NAME,'A','9').

2569: Bug:TCP/IP session can become corrupted by spurious output

When running as a background process, a nul device is used to capture spurious output so that the

tcp/ip communication channel is not corrupted.

Documents

Table of Contentskbs.custhelp.com/ci/fattach/get/4840/0/filename/KBSQL...KB_SQL Version 5.3 Release Notes 4/13/2011 9:10 AM KB_SQL Version 5.3 Release Notes 4/13/2011 9:10 AM page