Release Notes

From RapidSQL
Jump to: navigation, search

Go Up to What's New

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.

Team Server 2016 Installation and Configuration

Team Server 2016 or later must be installed and configured in order to get its Datasource and Credential Synchronization in Rapid SQL.

You can find all the information for installing Team Server 2016 and later in Install and Configure Team Server 2016.

Team Server URL must be also configured in DBArtisan. For that, add the Team Server URL in Tools > Options... > Team Server.

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:
  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 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 Rapid SQL 16.6.1

There are no Rapid SQL bugs fixed in this release.

Bugs Fixed in Rapid SQL 16.6

Issue # Description DBMS


[SQL Editor][Code Complete] Auto Complete feature fails to function properly, nothing appears after period

Sybase ASE


Proc Missing Defines Test gives an error message




Bugs Fixed in Rapid SQL 2016+ (16.5)

Issue # Description DBMS


Login Dialog Crash


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

SQL Server

Bugs Fixed in Rapid SQL 2016 Patch (16.0.1)

Issue # Description DBMS


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

SQL Server


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

SQL Server


[Crash] Sybase IQ customer crashes

Sybase IQ

Bugs Fixed in Rapid SQL 2016 (16.0.0)

Issue # Description DBMS


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



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



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

Personal tools