Rapid SQL Home | Rapid SQL Documentation
| IDERA Technical Support | www.idera.com
ReadMe
Last Published: October 12, 2016. Any updates to these notes will be available
at www.idera.com/support/productdocuments.
Thank
you for using IDERA Rapid SQL, the integrated development environment for IBM
DB2, Microsoft SQL Server, MySQL, Oracle, PostgreSQL, Sybase and Teradata
database systems. Rapid SQL is your fast path to higher productivity whether
you're programming in SQL, PL/SQL, Transact-SQL or HTML. Before you use Rapid
SQL, please read the following information.
What's New in Rapid SQL
Single Java Directory for Multiple IDERA
Products
Error Reporting for Troubleshooting
Performance and Exception Handling Improvements
Updated Database Explorer Schema Object Types
Support Newer Partitioning Options
Requirements
32-bit versus 64-bit Application Considerations
and Restrictions
DBMS Support and Connectivity
Dedicated Support Connectivity Options
Generic JDBC/ODBC Connectivity
Specifically-tested JDBC/ODBC Connectivity
Products: Apache Hive/Hadoop
DBMS Versions No Longer Supported
Release Notes
Team
Server 2016 Installation and Configuration
Additional Resources
What's New in
Rapid SQL
This release begins a rollout of rebranding this product from
Embarcadero to IDERA. Note that these changes include a new license agreement,
installation and data directories, icons, file names, registry settings, and
more. For more information about IDERA and IDERA products, see www.idera.com.
Simplified licensing now offers a single Rapid
SQL license for single and multiplatform environments. Standard and
Professional editions now are simply Rapid SQL.
Single Java Directory for
Multiple IDERA Products
Users
who have multiple IDERA products including DBArtisan
and Rapid SQL previously had multiple installations of the Java directory under
the installation home directory even when the Java versions were the same. With
this release, the Java directory is streamlined, using a common files
sub-directory with one installation of Java. Version-specific sub-directories
exist when necessary. Only
available for SQL Server.
Rapid SQL now uses AES 256 encryption when saving or storing
database connection passwords.
Error Reporting for
Troubleshooting
Rapid SQL includes new technical support features that help when
you have an issue or when the system crashes. Use the IDERA Error Report to
create a zip file containing important details about your installation, such as
IDERA product information, hardware metrics such as CPU, RAM, disk size, and
free space, and necessary database information. If your application crashes and
is inoperable, the IDERA Error Report zip file is automatically created and can
be found in the appdata log directory.
Performance and Exception
Handling Improvements
Performance improvements throughout the product should improve
response time and decrease the time necessary to launch new windows and tabs.
In addition, when an exception occurs, it is more visible to the user that the
tool is still operable, but that an error has occurred.
While working in the SQL Editor to construct SQL commands, users
no longer have to prefix a table name if they're working with tables in another
schema.
Updated Database Explorer Schema
Object Types
Database Explorer is updated to include or reflect changes to the
following schema object types:
·
Audit Policies
·
Context
·
Dimensions
·
Policies
·
Policy Groups
·
Queues
·
Queue Tables
·
Refresh Groups
·
Resource Consumer Groups
·
Resource Plans
·
Unified Audit Policies
Support Newer Partitioning
Options
This product now supports the full set of partitioning options
available for all current versions of Oracle.
Before
using Rapid SQL, please verify that your environment meets the requirements
listed below:
NOTE: Users
need full registry privileges during the installation and access to the keys
under HKEY_CURRENT_USER in the registry after installation.
Rapid
SQL requires Microsoft Internet Explorer 11 or later.
IDERA recommends the following minimum hardware requirements:
Rapid SQL supports the following operating systems:
XP
Support Notes - Windows XP has two user security groups: Users and Power Users.
Microsoft intentionally does not grant members of the Users Group the authority
to install applications or make global changes to the system. Restricted Users
are members of the Users Group. Standard users belong to the Power Users Group.
Microsoft grants members of the Power Users Group the authority to install
programs. You must be a member of the Administrators Group in order to install
and use IDERA applications. Because Restricted Users are members of the Users
Group, they cannot install and run IDERA applications.
Use
the Group Membership tab to determine your group and review the
Microsoft security guidelines. On the Control Panel, open User
Accounts. On the Users tab, select a user and then click the Properties
button. Click the Group Membership tab.
Vista
and Windows 7 Support Notes - Windows Vista UAC and Windows 7 provide
two user types: Standard users and Administrators. Rapid SQL can be installed
or uninstalled by an administrator or by a standard user using an administrator
token. Standard users can run Rapid SQL. For the purpose of running Rapid SQL,
default standard user token privileges should not be modified. Modifying
standard user token privileges can result in licensing issues which will
prevent Rapid SQL from operating properly.
32-BIT VERSUS 64-BIT APPLICATION
CONSIDERATIONS AND RESTRICTIONS
If
you install the 64-bit version of Rapid SQL and you are using custom drivers,
you must be using 64-bit versions of those drivers when using the 64-bit
version of Rapid SQL. Similarly, 32-bit versions of custom drivers must be used
with the 32-bit Rapid SQL installation.
For
version control integration, if you install the 64-bit version of Rapid SQL,
you can work with either a 32-bit or 64-bit MSSCCI provider. The feature is
controlled from the Options Editor's Version Control tab (File >
Options > General > Version Control).
Dedicated Support Connectivity
Options
Rapid
SQL provides dedicated connectivity to a specific version range of IBM DB2 for
Linux, UNIX, and Windows, IBM DB2 for z/OS, InterBase/Firebird, Microsoft SQL
Server, MySQL, Oracle, PostgreSQL, Sybase, and Teradata databases.
The
following connectivity options are provided:
The
following table provides a summary of resources/requirements for connectivity
to dedicated DBMS platforms. For each platform, it lists supported versions,
the client software, driver, or client/driver combination that must be
installed if using native IDERA clients, and the third-party, Type 4 JDBC
drivers packaged with Rapid SQL.
|
DBMS Platform |
Supported Versions |
Client (or
driver/client combination) Required for use with Native IDERA Drivers |
Packaged JDBC Driver |
Source & License |
|
Apache Hive (Technical
Preview) * |
0.13.1 |
Simba Hive ODBC Driver
( v1.4.13.1013) |
Apache Software
Foundation - Apache Hive JDBC v0.13.1 |
|
|
Firebird |
Firebird 2.0 |
Firebird ODBC Driver |
Jaybird JDBC Driver |
|
|
IBM DB2 for z/OS |
v8, v9, and v10 |
DB2 UDB Client for
Windows 8.0 or later |
IBM Data Server Driver
for JDBC |
|
|
IBM DB2 for LUW |
Versions 9.0 - 10.0 |
IBM DB2 LUW Client for
Windows 8.0 or later |
IBM Data Server Driver
for JDBC |
|
|
InterBase |
InterBase 2007 |
InterBase ODBC Driver |
Interbase JDBC Driver |
|
|
Microsoft SQL Server |
2005 (All editions including 2005 Express Edition
for 32-bit x86 and 64-bit Itanium & x86-64) |
Microsoft SQL Server
Client Library |
jTDS Type 4 JDBC Driver for Microsoft SQL Server |
|
|
MySQL |
4.x |
MySQL Connector/ODBC
Driver 5.2.x Driver - MySQL
Connector/ODBC driver 3.51.x Driver |
MySQL Connector/J JDBC
Driver |
|
|
Oracle |
Oracle 9i, 10g,
11g, and 12c |
Oracle SQL*Net Client |
Oracle JDBC Thin
Driver |
|
|
PostgreSQL |
9.3 minimum |
PostgreSQL ODBC Driver
(latest version recommended) |
PostgreSQL JDBC Driver |
|
|
Sybase ASE |
Sybase 15.7 -
Sybase 16 |
Sybase Open Client |
jTDS Type 4 JDBC Driver for Microsoft SQL Server |
|
|
Sybase IQ |
12.7 - 15.4, 16 |
SQL Anywhere ODBC
drivers for Sybase IQ 12.7 |
Sybase jConnect JDBC Driver for Sybase IQ |
|
|
Teradata (Technical
Preview) * |
13.10, 14.0, 14.10, and 15.0 |
Teradata ODBC driver
for Windows (version 15
recommended) |
Teradata JDBC Driver |
|
Generic JDBC/ODBC Connectivity
Generic
JDBC/ODBC connectivity to non-dedicated DBMS systems or non-database datasources is also provided. Rapid SQL can connect to a datasource using a customer-provided, third-party JDBC
version 4.0 or ODBC version 3.0 driver. Minimal Rapid
SQL functionality is provided, including a basic Explorer tree and SQL
querying.
Specifically-Tested JDBC/ODBC
Connectivity Products: Apache Hive/Hadoop
Rapid
SQL has been successfully tested against Apache Hive/Hadoop datasources
using the Hortonworks ODBC driver. Similarly, Cloudera Impala datasources have
been tested using the Cloudera JDBC driver. In both
cases, SQL querying and a Datasource Navigator tree
are available.
DBMS Versions No Longer Supported
As
of this release, Rapid SQL is no longer being tested against Sybase ASE
versions before 15.7.
Release Notes
Team
Server 2016 Installation and Configuration
Team Server 2016 must be installed and configured
in order to get its Datasource and
Credential Syncronization in Rapid SQL.
You can find all the information for installing Team Server 2016
in Install
and Configure Team Server 2016.
Team Server URL must be also configured in Rapid SQL. For that, add the Team Server URL in Tools > Options... >
Team Server.
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.
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: //support.microsoft.com/en-us/kb/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.
§ To bind the IDERA Sybase Debugger:
sp_tempdb "bind" , "ap", "Sybase Debugger", "DB",
"<tempdb name>"
§ To bind the user:
sp_tempdb "bind", "lg",
"<login id>", "DB", "<tempdb name>"
Customer-reported bugs fixed for the Rapid SQL 2016+ (16.5)
release:
|
Issue # |
Description |
DBMS |
|
RAP-6086 |
Login Dialog crash. |
|
|
RAP-6048 |
[Data Source
Navigator] Occasional crashes when expanding databases node from the datasource navigator. |
SQL Server |
|
DBA-33446 |
[Data Cache] After
Preview statements are in the wrong order. |
Sybase ASE |
|
DBA-33390 |
[BNF] CBufferedOutputRouter crash. |
|
|
DBA-33331 |
PCLender
crash. |
SQL Server |
|
DBA-32998 |
[Sybase][Parsers]
Batch delimiter ‘go’ on its own is treated as procedure instead of empty
statement. |
Sybase ASE |
|
DBA-32608 |
[Oracle][Extract Role]
Extracting DDL a role, the users assigned to the role are no longer included. |
Oracle |
|
DBA-31248 |
[Crash Report] DBArtisan crashes while outputting sql
results. |
All |
|
DBA-30756 |
[DBMS Actions] Cannot
create insert statements from a particular table. |
Sybase ASE |
|
DBA-30248 |
Error establishing a
debugger session with the server. |
DB2 for LUW |
|
DBA-18630 |
Extraction issue – XML
INLINE LENGTH and compression not recognized. |
DB2 for LUW |
Customer-reported bugs fixed for the Rapid SQL 2016.0.1 release:
|
Issue # |
Description |
DBMS |
|
RAP-6050 |
[JDBC][Procedures] Smallint being treated as bit datatype.
|
SQL Server |
|
RAP-6048 |
[Data Source
Navigator] Occasional 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 |
DBA-33150 [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 misleading. |
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 appropriate unique
index. |
Oracle |
|
Customer-reported bugs fixed for the Rapid SQL 2016 release: |
||
|
Issue # |
Description |
DBMS |
|
RAP-5970 |
Customer case 00430700
- The application 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 the application: JAWS incorrectly reads the drop-down options that have separators.
|
|
|
DBA-32830 |
Not consistently
opening SQL files from location set in Directories option for "User SQL
Scripts". |
|
|
DBA-32585 |
Lapsed time clock at
the bottom of a Query/Results tab frame no longer works. |
Oracle |
|
DBA-32474 |
[File Execution
Facility] After row 43, Dates are being returned as zeros. |
All |
|
DBA-32472 |
[Regression][DMBS
Actions] Hide time portion of DATE datatype if zero
option suppresses the time portion for all rows, even if they have non-zero
times. |
Oracle |
|
DBA-31935 |
[Schema Extraction]
When extracting or compiling Function, the comments are missing from
Function. |
Oracle |
|
DBA-30919 |
[DBMS Actions] Ability
to name output file. |
All |
|
DBA-22901 |
Request support for
Excel 2007. |
All |
|
DBA-22732 |
[Editor results] Request
for support for the option to save the result in Excel binary format,
extension xlsb. |
All |
|
DBA-4638 |
Wrong database device
size is displayed in Explorer window. |
Sybase ASE |
Additional
Resources
All IDERA products include a 14-day trial period. To continue
using the product without interruption, we recommend that you license it as
soon as possible. For information on licensing your product, refer to the Installation
Guide. If you have not yet purchased this product, contact [email protected].
IDERA Product Support
The IDERA Web site is an excellent source for additional product
information, including white papers, articles, discussion forums, and the IDERA
Knowledge Base. Visit www.idera.com/support,
or click any of the links below, to find:
If you have a valid maintenance contract with IDERA, the Technical
Support team is available to assist you with any problems you have with our
applications. Our maintenance contract also entitles registered users of IDERA
products to download free software upgrades during the active contract period.
Evaluators receive free technical support for the term of their evaluation (14
days).
We encourage you to open technical support cases via the Customer Support Center. For
additional information about IDERA Technical Support, visit the Support section of our Web site.
To download evaluations of other IDERA products or to learn more
about our company and our products visit us at www.idera.com.