Showing all blog entries tagged with "ElevateDB"

ElevateDB 2.26 Build 4 Released

---

Posted by Tim Young on Wed, Sep 13 2017

ElevateDB 2.26 Build 4 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

This build contains a couple of important bug fixes, which are detailed here.

---

Tags: ElevateDB, New Builds

Permanent Link • 0 Comments

ElevateDB 2.26 Build 3 Released

---

Posted by Tim Young on Tue, Aug 15 2017

ElevateDB 2.26 Build 3 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

This build contains one important bug fix, which is detailed here.

In addition, in this build the VCL product DCUs for Delphi 10.2 Tokyo are now compiled with Delphi 10.2 Tokyo Update 1.

---

Tags: ElevateDB, New Builds

Permanent Link • 0 Comments

ElevateDB 2.26 Build 2 Released

---

Posted by Tim Young on Tue, Jul 4 2017

ElevateDB 2.26 Build 2 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

This build contains two important bug fixes, which are detailed here.

---

Tags: ElevateDB, New Builds

Permanent Link • 0 Comments

ElevateDB 2.26 Released

---

Posted by Tim Young on Mon, Jun 26 2017

ElevateDB 2.26 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

The complete list of breaking changes and new features is below.

2.26 Breaking Changes

---

The following are breaking changes in 2.26:

• The following incident report:
  
  Incident Report #4528 - Altering a Table Results in an Incorrect Table Structure Checksum
  
  deals with an issue with incorrect checksum calculations during table alterations. This bug can affect your ability to restore backups when restoring only table files without also restoring the database catalog. However, please keep in mind that the table structure checksums are only re-computed when a table is altered in some way, and under normal operation are simply just stored and compared to ensure that the physical table files match the table structure for the table in the database catalog.



• There is a new JOININDEXTHRESHHOLD keyword available for the SQL SELECT statement. This keyword controls how ElevateDB handles optimized (indexed) WHERE conditions on tables that are the target of INNER JOINs. For more general information, please see the How ElevateDB Selects the Rows section in the Optimizer topic in the SQL manual.
  
  Previously, ElevateDB would simply use any available, usable index and build a bitmap that represented the set of rows, irrespective of how many rows were selected. This works fine when there are no joins, but can be problematic when the number of rows selected is large and the table is also the target of an INNER JOIN. In such cases, the INNER JOIN condition's bitmap must constantly be assigned/ANDed with the WHERE condition's bitmap and, because the join condition's bitmap typically represents a much smaller set of rows than the WHERE condition, this process of reconciling the bitmaps becomes computationally expensive and a drag on performance.
  
  The value provided with JOININDEXTHRESHHOLD clause is an integer value representing a percentage of rows that, when exceeded, causes ElevateDB to treat such WHERE conditions as un-optimized row scans instead of index scans. This eliminates the computationally expensive bitmap operations and drastically improves the performance of the SELECT statement. The default value for the JOININDEXTHRESHHOLD is 75. This means that a WHERE condition must select at least 75% of the rows in a table is also the target of an INNER JOIN condition in order to be converted into a row scan.

2.26 New Features

---

The following are the new features in 2.26:

• There is a new NO BACKUP FILES clause included with the ALTER TABLE, CREATE INDEX, CREATE TEXT INDEX, ALTER INDEX, ALTER TEXT INDEX, DROP INDEX, and OPTIMIZE TABLE SQL statements. This clause allows you to stop ElevateDB from retaining backup files (*.old) for physical table files after the execution of the SQL statement completes.
  
  
   The NO BACKUP FILES clause does not apply to physical backup files created for the database catalog, which are always created and retained. Also, if the application executing the SQL statement is killed for any reason, it is still possible for these backup files to be present and not removed.



• There is a new FROM PUBLISHED UPDATES clause included with the CREATE TABLE statement. This clause allows you to create a table (permanent or temporary) that includes all pending published updates for all, or some, of the tables in the database.



• Query execution can now be cancelled while ElevateDB is executing un-optimized WHERE conditions on tables. Previously, ElevateDB would need to wait until such conditions were executed before it could cancel the query execution, and could only cancel query execution while executing joins and building the result set. This design was used for performance reasons, but it resulted in situations where runaway un-optimized queries could never be killed without killing the application itself.

In addition, this release contains several bug fixes, which are detailed here.

---

Tags: ElevateDB, New Releases

Permanent Link • 0 Comments

Advantage Database Migration Promotion

---

Posted by Sam Young on Fri, Apr 14 2017

ElevateDB 2.25 now includes migration support for Advantage Database databases. In conjunction with this new migration support, we are also offering a 30% discount for existing Advantage Database customers on the purchase of any ElevateDB VCL or DAC product.

To order ElevateDB, complete the following steps (please be sure that you are logged in to the web site with your user login information):

• Visit the ElevateDB product page


• Select your development environment from the list at the bottom of the page


• Click on the Order Now link in the upper right area of the product information page


• Add the desired product to your order, and select special offer code ADVANTAGE to apply your discount when adding the product to your order.

This discount will be in effect until June 30, 2017.

Please contact me if you have any questions about this promotion.

---

Tags: ElevateDB, Promotions

Permanent Link • 0 Comments

ElevateDB 2.25 Released with RAD Studio 10.2 Tokyo Support and Advantage Database Migration Support

---

Posted by Tim Young on Fri, Apr 14 2017

ElevateDB 2.25 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

ElevateDB 2.25 now includes support for Embarcadero RAD Studio 10.2 Tokyo (Delphi 10.2 32/64-bit, and C++Builder 10.2 32/64-bit). Currently, this support for Windows only, but will be expanded over the next two months to include MacOS, followed by support for the next-generation compiler and Linux, Android, and iOS.

Included with the ElevateDB Additional Software and Utilities download is a new Advantage Database migrator that can migrate any Advantage Database 9.x or higher database to an ElevateDB database. Please see Migrating a Database topic in the SQL manual for more information.

The ElevateDB 2.25 .NET Data Adapter now includes Visual Studio 2017 IDE integration support.

The ElevateDB 2.25 PHP Extension now includes support for 64-bit PHP 5.6 environments (Windows-only).

The complete list of breaking changes and new features is below.

2.25 Breaking Changes

---

The following are breaking changes in 2.25:

• ElevateDB no longer logs row lock errors in the logged events for a given configuration. Such errors are a normal part of multi-user database usage and tended to "pollute" the logged events, making it harder to find actual errors.



• The TEDBEngine TempTablesPath and TEDBSession LocalTempTablesPath properties have been moved from being published to public, so you may see a missing property error when loading forms in the IDE that contain the TEDBEngine or TEDBSession properties. These properties are typically only useful at run-time, and setting them at design-time could cause run-time errors if their values did not work properly with the target operating system's configuration.

2.25 New Features

---

The following are the new features in 2.25:

• The ElevateDB Server now supports global request/response tracing for analyzing performance issues or finding the source of bugs in client applications. The core TEDBEngine component supports tracing via its ServerTrace property and OnServerTrace event. The compiled ElevateDB Server that is provided with ElevateDB uses this functionality to implement logging of all traced events. You can find out more information on the built-in tracing in the Starting and Configuring the ElevateDB Server topic in the ElevateDB SQL Manual.



• The performance of string comparisons using the default ANSI and UNI collations has been improved.



• The TEDBSession TEDBSession RecordLockProtocol, RecordLockRetryCount, and RecordLockWaitTime properties can now be modified when a session is connected. Previously, these properties could only be modified before a session was connected.

In addition, this release contains several bug fixes, which are detailed here.

---

Tags: ElevateDB, New Releases

Permanent Link • 0 Comments

Previous Entries: 1-6 7-12 13-18 19-24 25-30 31-36 37-42 43-48 49-54 55-60 61-66 67-72 73-78 79-84 85-90 91-96 97-102 103-108 109-114 115-120 121-126 127-128