Release Notes

From DBArtisan
Jump to: navigation, search

Go Up to What's New

Important Advisory Notes

  • If you want to run DBArtisan on Microsoft Windows 8.1, verify that third-party DBMS native drivers install properly. Consider using a JDBC connection.

Known Issues

Issue # Description DBMS

DBA-34304

Inherited Partitions on Index are not showing while creating index from table in Data Compression tab.

SQL Server

DBA-34302

Selection issues in schema migration.

DBA-34298

Schema migration does not work for few cases.

DBA-34296

Incorrect alter query generating in the cases of extended alter for In-memory and temporal tables.

SQL Server

DBA-34294

Remote Debugger Support.

SQL Server

DBA-34271

Filestream creation is not available in DBArtisan.

SQL Server

DBA-34270

Schema migration doesn't work if object not selected explicitly.

DBA-34223

[SQL Azure] Unable to create In-memory Tables in Azure.

SQL Azure

DBA-34222

[SQL Azure] Data Masking property is not showing in table columns in Azure.

SQL Azure

DBA-34221

[SQL Azure] Temporal properties tab is not showing while creating tables.

SQL Azure

DBA-34220

[SQL Azure] Unable to create Spatial Index in Azure.

SQL Azure

DBA-34219

[SQL Azure] Unable to create Secondary XML index in Azure.

SQL Azure

DBA-34218

[SQL Azure] Unable to create Primary XML index in Azure.

SQL Azure

DBA-34216

[SQL Azure] Columnstore index is not available in index types in Azure to create.

SQL Azure

DBA-34215

[SQL Azure] Data compression tab in Index is disabled in Azure.

SQL Azure

DBA-34214

[SQL Azure] Data compression tab for table is disabled in Azure.

SQL Azure

DBA-34197

Extract is different for Snapshot Database in DBArtisan and SSMS.

SQL Server

DBA-34184

[Postgres] unable to perform extract operation on roles.

Postgres

DBA-34157

"Table columns" button is not present in create index wizard in postgres".

Postgres

DBA-34149

Refresh issue in object population for indexes.

DBA-34141

"Showing exclusion constraint as exclusion key " in combo box on top when opened exclusion constraint in Postgres.

Postgres

DBA-34140

[postgres]Schema Publication - com.embarcadero.dboject.generic.framework.indexcolumnlmpl Error.

Postgres

DBA-34138

[postgres]Schema Publication - concurrentmodificationexception Error.

Postgres

DBA-34136

[postgres]Schema publication - Null Point Exception error.

Postgres

DBA-34135

[primary key] Does primary key editor should contain index name under attributes or not?

Postgres

DBA-34133

[views]Revoke cascading option is not available in permissions tab->revoke drop down.

Postgres

DBA-34055

With NOCHECK' property for constraints while creating new table.

SQL Server

DBA-34013

Full.At shutdown for Durability is not applicable for TEMP db-Sybase.

Sybase

  • The current version of DBArtisan does not support the MySQL ODBC client that shipped with previous versions of DBArtisan. If DBArtisan crashes after connecting to a MySQL data source:
  1. Close DBArtisan.
  2. Uninstall the older MySQL ODBC client.
  3. Restart DBArtisan 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, DBArtisan 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 DBArtisan, will result in procedures A2 and A3 being invalidated.
  • In some situations the Database Monitor may prompt to connect to an already connected datasource if auto-connect is not enabled for that datasource.
  • 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.
  • The SQL Server Agent failing problem is caused by the lack of permission to enumerate the status of the server service. To determine the status of the server, the user must have permission to check the status of the server service. If the user running DBArtisan at the client machine is a not a local user who can be authenticated at the server machine, the Server Agent jobs will fail.
    Workaround:
    • If the user that runs DBArtisan is not a domain user, create the same user with the same password on the server.
    • If the user is a domain user, make sure the user can login to the server.
  • 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 IDERA 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 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>"
  • The BCP (bulk copy) data movement option is disabled for cross-platform migration. In addition, to use the BCP in a Sybase-to-Sybase migration, the user must be logged in as System Administrator *or* the "select into/bulkcopy/pllsort" database option must be true on the target catalog. If this option is "false" on the target catalog, BCP will not appear as a data movement option for non-system users.
  • DBArtisan 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 DBArtisan 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 17.0.3

Issue # Description DBMS

DBA-34415

DBArtisan crashes when running a query with more than 50k lines

Sybase ASE

DBA-34414

Copyright is not updated across all DBPS products

All

DBA-34407

Error while pasting SQL

All

DBA-34400

Stored procedure not being displayed entirely

DB2

DBA-34398

In Data tab Table or View cannot be found

Oracle

DBA-34394

DBArtisan is crashing

SQL Server

DBA-34393

Extracting the DDL for a "Refresh Group" produces syntax which cannot be executed w/o modification

Oracle

DBA-34390

When Code Assist is enabled, program crashes

DB2 for LUW

DBA-34389

Foreign key constraint violation causes crash

Sybase ASE

DBA-34385

User cannot copy from SPID screen and paste into Notepad

Sybase ASE

DBA-34384

Sybase ASE 16.0 buffer cache not displayed

Sybase ASE

DBA-34383

Discover Datasources crashes

DB2 for LUW

DBA-34379

Duplicated query result with TIBCO ODBC driver

ODBC

DBA-34378

Error when logging into Sybase ASE

Sybase ASE

DBA-34375

Data cache sizes reported half of actual size

Sybase ASE

DBA-34370

Performance slow when editing query

Sybase ASE

DBA-34364

Found a bug in reorganizing a table in DB2 in DBArtisan

DB2 for LUW

DBA-34359

DBArtisan incorrectly displays table count

PostgreSQL

DBA-34355

Stored procedures and Trigger extracts are not complete

SQL Server

DBA-34353

Debug not working for Sybase

Sybase ASE / Sybase IQ

DBA-34340

Problem displaying column information for tables using case-sensitive collation

SQL Server

DBA-34328

PostgreSQL/Schema Migration/Schema Publication - Getting list of Schemas and/or Users process never ends

PostgreSQL

DBA-33608

Unable to change a user's login password in custom procedure

Sybase ASE

Bugs Fixed in Rapid SQL 17.0.3

Issue # Description DBMS

RAP-6155

Query runs in SQLPlus but not Rapid SQL

Oracle

RAP-6151

Bookmarks are showing under wrong DB platform

DB2 for LUW

RAP-6147

Rapid SQL debugger does not work

Sybase ASE

RAP-6145

Unable to retrieve BLOB datatype results

DB2 for z/OS

RAP-6144

Unable to connect to DB2 database

DB2 for LUW

RAP-6143

Receiving an error message when special character is in password

DB2 for LUW

RAP-6141

Debugging Procedures not working properly

Sybase ASE

RAP-6138

Describe function for table objects not working using Ctrl+D in ISQL window

All

RAP-6137

Scrolling with arrow key is jumpy

SQL Server

RAP-6134

Additions to Rapid SQL for Greenplum support

PostgreSQL

RAP-6133

Error establishing a debugger session with server

Sybase ASE

Bugs Fixed in DBArtisan 17.0.2

Issue # Description DBMS

DBA-34357

DBArtisan fails to enumerate the SQL Server Agent

SQL Server

DBA-34351

Truncate feature is grayed out if more than one table is selected

SQL Server

DBA-34350

Invalid column name error for missing indexes

SQL Server

DBA-34345

Registry-based catalog is not retaining configuration information

Oracle / Postgres / SQL Server

DBA-34347

Indexes not showing properly

SQL Server

DBA-34335

Unable to expand a database breach in the DBArtisan explorer tree

Oracle

DBA-34009, DBA-34331, DBA-34354

Keystrokes are missed when using version 16.6

SQL Server

DBA-33906

DBArtisan performance slows down with extended use

Sybase

Bugs Fixed in Rapid SQL 17.0.2

Issue # Description DBMS

RAP-6132

JDBC driver can't be disabled as default even when the native driver is installed

Postgres

RAP-6131

Passwords with semi-colons

DB2

Bugs Fixed in DBArtisan 17.0

Issue # Description DBMS

DBA-33996

Space value not showing accurately

SQL Server

DBA-33899

Getting 'Error :relation "information_schema.testit" does not exist' when selecting Data tab for views & Tables

Postgres

DBA-33897

Data in Columns tab not shown immediately after creation for Exclusion Constraint, Unique Keys and Primary Keys in PosygreSql.

Postgres

DBA-33902

Since SpyGlass Release: POSTGRESQL: ERROR: only input parameters can have default values.

Postgres

DBA-33102

Reorganization jobs scripts fail to be executed.

SQL Server / Oracle

DBA-33074

The script contains a drop Foreign key even though it contains Drop table.

SQL Server

DBA-33330

[DBMS Object Management] the ‘USE <database>’ statement is only put at the top of one extract window.

SQL Server / Sybase

DBA-33527

DBMS Object n does not appearManagement] The "ON FILEGROUP" option.

SQL Server

DBA-33570

[Schema Extraction] DB Extraction puts extra option require a license.

Sybase

DBA-33847

Top SQL windows all need double click launch into iSQL.

DBA-33846

Space analyst temp bar grows for no reason.

SQL Server

DBA-33852

Space analyst for objects/tables/indexes tab should refresh on entry.

Sybase

DBA-33949

Wizard calling wizard leaving open window.

Oracle

DBA-34012

Role Editor/ User Editor/ Missing space in Materialized View and Resource Consumer Group in Object Type drop down.

Oracle

DBA-34011

Error when trying to grant system permissions to a user.

DB2

DBA-33685

Latest PosgreSQL does not connect without errors.

Postgres

DBA-33938

Resource Consumer Groups/ No information about Resource Consumer Group in Roles/ Users editor.

Oracle

Bugs Fixed in Rapid SQL 17.0

Issue # Description DBMS

RAP-6107

Code analyst reports in log that it's talking to 2005 database.

RAP-6102

When running debugger on SQL Server DB Rapid SQL gives error.

Personal tools