Release Notes for Rapid SQL 2016 Patch

From RapidSQL
Jump to: navigation, search

Go Up to What's New in Rapid SQL 2016

Important Advisory Notes

  • If you want to run Rapid SQL on Microsoft Windows 8.1, verify that third-party DBMS native drivers install properly. Consider using a JDBC connection.
  • Performance IQ has been removed.

Known Issues

  • The current version of Rapid SQL does not support the MySQL ODBC client that shipped with previous versions of Rapid SQL. If Rapid SQL crashes after connecting to a MySQL data source:
  1. Close Rapid SQL.
  2. Uninstall the older MySQL ODBC client.
  3. Restart Rapid SQL and try connecting to a MySQL datasource. You are prompted to install the MySQL client drivers.
  4. Follow the installation instructions to install the new driver.
  • Note that when debugging a procedure against an Oracle data source, Rapid SQL performs a compilation before debugging. During a compilation, Oracle invalidates referencing objects. For example, if procedures A2 and A3 both reference procedure A1, debugging procedure A1 in Rapid SQL, will result in procedures A2 and A3 being invalidated.
  • For servers running on Sybase version 12.5.3a, the CREATE ENCRYPTION KEY and DECRYPT permissions do not display properly--they'll be shown as null. See Sybase's document CR392544 ("sp_helpprotect does not show privileges related to encryption keys."). This has been fixed in ASE version 12.5.3a/ESD#1 (now available as a download) and ASE version 12.5.4.
  • When you are using the Debugger:
  • The Debugger windows (Variables, Watch, CallStack, Dependency) cannot be undocked. This behavior is deliberate and is true only for the Debugger windows. The Output window can be undocked.
  • When running Windows XP SP2, SQL Server 2000 SP4 is required on both the client and the server.
  • When running the Debugger on SQL Server 2005 CLIENTS:
  1. Verify that the file ssdebugps.dll is registered on the client machine. This file is REQUIRED for debugging and Microsoft only installs it on the server machine and not as a part of a client-only install.
  2. Follow the instructions under the "Configure DCOM on the computer that is running Visual Studio .NET" heading from Microsoft to reconfigure the DCOM settings on your client machine: http://support.microsoft.com/default.aspx?kbid=833977.
  3. On the Default Properties tab of the My Computer dialog box, make sure the Default Authentication Level is set to None and that the Default Impersonation Level is set to Impersonate.
  • When using the Embarcadero Sybase debugger against a Sybase database with multiple temporary databases (supported in Sybase ASE 12.5.0.3 and above), either the user or the debugger application must be bound to a specific temporary database.
  • To bind the Embarcadero Sybase Debugger:
sp_tempdb "bind" , "ap", "Sybase Debugger", "DB", "<tempdb name>"
  • To bind the user:
sp_tempdb "bind", "lg", "<login id>", "DB", "<tempdb name>"
  • Rapid SQL is currently unable to create table names, column names, and check constraint names longer than 18 characters on an OS390 mainframe database.
  • On SQL Server 2005, the Browser component is disabled by default. With this service disabled, in Rapid SQL you cannot reference SQL Server instances by name, only by port number. If you want the ability to reference SQL Server instances by name, you must enable this service on the server.

Bug Fixes

Bugs Fixed in DBArtisan 2016 Patch (16.0.1)

Issue # Description DBMS

RAP-6050

[JDBC][Procedures] Smallint being treated as bit datatype

SQL Server

RAP-6048

[Data Source Navigator] Occassional crashes when expanding databases node from the datasource navigator

SQL Server

RAP-6027

[Crash] Sybase IQ customer crashes

Sybase IQ

DBA-33166

Case Number 00455434: Invalid column name 'systemwide password expiration'

Sybase ASE

DBA-33159

[Enhancement] Change fillfactor default value to prevent space consumption and performance issues on index rebuild

SQL Server

DBA-33154

[BCBSVT] [SQL Editor] Application crashes during SQL Editor session

DB2 for LUW

DBA-33152

DBA-33150 [Enhancement] Improve the exception handling in case of driver blowing up

Oracle

DBA-33151

DBA-33150 [ISQL] Nomura crashes

Oracle

DBA-33150

Find a solution to the random crashes experienced by customers

All

DBA-33141

[DBMS Object Management] Crash and inoperative state with views

DB2 for LUW

DBA-33108

Oracle 11g and higher already has a PLAN_TABLE installed

Oracle

DBA-33095

Provide support for SQL*PLUS script commands

Oracle

DBA-33076

[Analysts] Unable to run an analysis report

SQL Server

DBA-33068

[Enhancement][Functions]Some objects do leave out the schema name in the CREATE

SQL Server

DBA-33033

Customer case 00443195: Schedule of Capacity Analyst does not work on machines with Windows in Spanish

SQL Server

DBA-32999

[DBMS Object Management] Database option "allow incremental dumps" is not shown for Sybase 15.7 SP130

Sybase ASE

DBA-32987

[Edit Data] Copy-Paste from Edit Data grid returns weird characters

SQL Server

DBA-32967

[Schema extraction/publication] Can't execute schema extraction and schema publication with some DBMS

SQL Server

DBA-32960

In Edit Data, the DELETE of a row is not actually performed in the table

SQL Server

DBA-32959

[Enhancement]Migrate Database object is missleading

Sybase ASE

DBA-32945

[DBMS Object Management] Can't exchange a table partition

Oracle

DBA-32943

Unable to kill sessions from the Lock tab in Database monitoring

Sybase ASE

DBA-32935

Analyst update error on Oracle datasources ORA-01031: insufficient privileges

Oracle

DBA-32713

[Utilities] No records are migrated with migrated feature

Sybase ASE

DBA-32698

[ISQL] Crashes in Isql when running multiple scripts

All

DBA-31366

[DBMS Actions] Tables based on materialized views do not get extracted with the appropiate unique index

Oracle

Bugs Fixed in Rapid SQL 2016 (16.0.0)

Issue # Description DBMS

RAP-5970

Customer case 00430700 - Rapid SQL generates a corrupt xlsx file when importing results to Excel

Oracle

RAP-5865

[Tools] Ability to save a .csv file from results where all the fields are enclosed in double quotes.

Oracle

RAP-5742

508 compliance for Rapid SQL: JAWS incorrectly reads the drop-down options that have seperators