Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 10 of 27 total |
Moving Forward with ElevateDB 2.0 |
Fri, Feb 15 2008 6:36 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | I expect ElevateDB 2.0 to be ready by the end of March, and will, as of now,
include the following features and improvements. Please note that this list is subject to possible change. ..NET and Visual Studio ---------------------- - Better Visual Studio design-time integration, including DDL operations such as altering tables, procedures, executing scripts, etc. Functionality ------------- - Replication for the ElevateDB Server using a publish/subscribe model - Messaging layer for general messaging notifications and broadcasts with the ElevateDB Server - Procedures and functions at the session level for use with all databases - Integrated procedure, function, and script debugging - Query optimizer has ability to optimize conditions using multi-column indexes - Customizable transaction timeouts for specifying how long a transaction waits for the applicable locks - Defaulting configuration paths to blank ("") and issuing an error if the configuration path is blank, along with design-time editor for selection - INCLUDING CONSTRAINTS, INDEXES, and TRIGGERS clauses for CREATE TABLE..AS statement - TABLES clause will be optional for BACKUP DATABASE and RESTORE DATABASE statements - Option to exclude specific sessions from the ElevateDB Server license count - Ability to retrieve execution plans for EXECUTE and EXECUTE IMMEDIATE statements - Script parameters are populated after the SQL is specified, without requiring a prepare operation first - ROW and ARRAY types - Error messages for ambiguous column references in joined SELECT statements - Ability to specify the precision for the values returned by the CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP functions - Ability to rename database objects - Ability to copy database objects - Ability to specify the buffering settings for query result sets - Ability to lock databases exclusively and have all database DDL operations buffered until database is closed - Option to log any error messages during an IMPORT TABLE instead of raising an exception immediately - Allow parameters for CREATE TABLE AS statements - Option for specifying that query result sets less than a certain size should be buffered in memory completely and not generate a temporary table - Ability to mark tables, views, and procedures as read-only at the catalog level - Ability to log custom information, warning, or error events into the ElevateDB log manager - New LIST aggregate function for concatenating values within a group or for the entire query - Ability to generate sensitive results sets for SELECT statements with sub-queries in the SELECT column list - SET PROGRESS, SET STATUS MESSAGE, and SET LOG MESSAGE SQL/PSM statements for scripts, procedures, etc. along with an ABORT statement and ABORTED function for allowing end users to abort scripts, procedures, etc. during progress updates ElevateDB Manager ----------------- - Individual object reverse-engineering - Ability to save and restore the current session view - Improved key handling in the SQL editor for word selection, etc. - Selectable sorts for database objects, creation order or alphabetical by object name - Unprepare option for statements and scripts - Templates for SQL statements and scripts Further Enhancements -------------------- In addition to the above-mentioned items, there will also be quite a few smaller improvements included that are directly from user enhancement requests, but are just a bit too specifc to detail here. A lot of these items concern minor cosmetic issues with the ElevateDB Manager, for example. Cost ---- The ElevateDB 2.0 upgrade for ElevateDB 1.0 customers will cost $99 for STD and STD-SRC products, and $129 for CS and CS-SRC products. The upgrade period will be 90 days, after which the upgrade pricing for 1.0 will revert to a simple 10% discount for existing ElevateDB 1.0 customers. We will also be issuing bug fixes and updates for ElevateDB 1.0 up until the end of the 90-day period, after which the ElevateDB 1.0 code base will be frozen. This is, of course, provided that ElevateDB 1.0 is stable enough to warrant suspending bug fixes, which we feel will be possible by that time. There will be no format changes or any technical effort required to move to ElevateDB 2.0 from 1.0, apart from a simple re-compile. Moving Forward -------------- In general, we will be issuing a major upgrade to ElevateDB every year around this time (the anniversary of the first ElevateDB release), and the terms of the upgrade will be very similar each year. However, there will be an exception when we introduce the ElevateDB Enterprise Server later this year. Check in to the newsgroups or the web site on a regular basis to find out more information as it becomes available. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Feb 15 2008 7:45 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
I liked what I was reading then I found this horrible section headed "cost" Roy Lambert |
Fri, Feb 15 2008 8:44 AM | Permanent Link |
"Harry de Boer" | >>.... end of March
The 10th of April is my birthday...don't make it any later! What a present that will be. Keep up the good work Tim. Regards, Harry "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht news:9BF16794-0CBD-4AFF-8EEB-205803FB6095@news.elevatesoft.com... > I expect ElevateDB 2.0 to be ready by the end of March, and will, as of now, > include the following features and improvements. Please note that this > list is subject to possible change. > > .NET and Visual Studio > ---------------------- > > - Better Visual Studio design-time integration, including DDL operations > such as altering tables, procedures, executing scripts, etc. > > Functionality > ------------- > > - Replication for the ElevateDB Server using a publish/subscribe model > > - Messaging layer for general messaging notifications and broadcasts with > the ElevateDB Server > > - Procedures and functions at the session level for use with all databases > > - Integrated procedure, function, and script debugging > > - Query optimizer has ability to optimize conditions using multi-column > indexes > > - Customizable transaction timeouts for specifying how long a transaction > waits for the applicable locks > > - Defaulting configuration paths to blank ("") and issuing an error if the > configuration path is blank, along with design-time editor for selection > > - INCLUDING CONSTRAINTS, INDEXES, and TRIGGERS clauses for CREATE TABLE..AS > statement > > - TABLES clause will be optional for BACKUP DATABASE and RESTORE DATABASE > statements > > - Option to exclude specific sessions from the ElevateDB Server license > count > > - Ability to retrieve execution plans for EXECUTE and EXECUTE IMMEDIATE > statements > > - Script parameters are populated after the SQL is specified, without > requiring a prepare operation first > > - ROW and ARRAY types > > - Error messages for ambiguous column references in joined SELECT statements > > - Ability to specify the precision for the values returned by the > CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP functions > > - Ability to rename database objects > > - Ability to copy database objects > > - Ability to specify the buffering settings for query result sets > > - Ability to lock databases exclusively and have all database DDL operations > buffered until database is closed > > - Option to log any error messages during an IMPORT TABLE instead of raising > an exception immediately > > - Allow parameters for CREATE TABLE AS statements > > - Option for specifying that query result sets less than a certain size > should be buffered in memory completely and not generate a temporary table > > - Ability to mark tables, views, and procedures as read-only at the catalog > level > > - Ability to log custom information, warning, or error events into the > ElevateDB log manager > > - New LIST aggregate function for concatenating values within a group or for > the entire query > > - Ability to generate sensitive results sets for SELECT statements with > sub-queries in the SELECT column list > > - SET PROGRESS, SET STATUS MESSAGE, and SET LOG MESSAGE SQL/PSM statements > for scripts, procedures, etc. along with an ABORT statement and ABORTED > function for allowing end users to abort scripts, procedures, etc. during > progress updates > > > ElevateDB Manager > ----------------- > > - Individual object reverse-engineering > > - Ability to save and restore the current session view > > - Improved key handling in the SQL editor for word selection, etc. > > - Selectable sorts for database objects, creation order or alphabetical by > object name > > - Unprepare option for statements and scripts > > - Templates for SQL statements and scripts > > Further Enhancements > -------------------- > > In addition to the above-mentioned items, there will also be quite a few > smaller improvements included that are directly from user enhancement > requests, but are just a bit too specifc to detail here. A lot of these > items concern minor cosmetic issues with the ElevateDB Manager, for example. > > Cost > ---- > > The ElevateDB 2.0 upgrade for ElevateDB 1.0 customers will cost $99 for STD > and STD-SRC products, and $129 for CS and CS-SRC products. The upgrade > period will be 90 days, after which the upgrade pricing for 1.0 will revert > to a simple 10% discount for existing ElevateDB 1.0 customers. We will also > be issuing bug fixes and updates for ElevateDB 1.0 up until the end of the > 90-day period, after which the ElevateDB 1.0 code base will be frozen. This > is, of course, provided that ElevateDB 1.0 is stable enough to warrant > suspending bug fixes, which we feel will be possible by that time. There > will be no format changes or any technical effort required to move to > ElevateDB 2.0 from 1.0, apart from a simple re-compile. > > Moving Forward > -------------- > > In general, we will be issuing a major upgrade to ElevateDB every year > around this time (the anniversary of the first ElevateDB release), and the > terms of the upgrade will be very similar each year. However, there will be > an exception when we introduce the ElevateDB Enterprise Server later this > year. Check in to the newsgroups or the web site on a regular basis to find > out more information as it becomes available. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > > |
Fri, Feb 15 2008 8:52 AM | Permanent Link |
Dan Rootham | Harry,
<< The 10th of April is my birthday...don't make it any later! What a present that will be. >> It's my birthday today, so the v1.08 release will do fine.... Cheers, Dan |
Fri, Feb 15 2008 9:13 AM | Permanent Link |
"Jose Eduardo Helminsky" | Dan
> It's my birthday today, so the v1.08 release will do fine.... Then "Happy birthday to you" Eduardo |
Fri, Feb 15 2008 9:58 AM | Permanent Link |
"Harry de Boer" | Dan,
Aren't we lucky quys Harry "Dan Rootham" <roothamd@yahoo.co.uk> schreef in bericht news:CFE36A10-B066-4F67-B400-7E59759B7D75@news.elevatesoft.com... > Harry, > > << The 10th of April is my birthday...don't make it any later! What a present > that will be. >> > > It's my birthday today, so the v1.08 release will do fine.... > > Cheers, > Dan > |
Fri, Feb 15 2008 11:16 AM | Permanent Link |
Scott Woods | Tim - can you provide more details on this?
- Replication for the ElevateDB Server using a publish/subscribe model |
Fri, Feb 15 2008 11:57 AM | Permanent Link |
Scott Woods | Wow Harry - in addition to using Elevate DB we share the same birthday.
>>.... end of March The 10th of April is my birthday...don't make it any later! What a present that will be. Keep up the good work Tim. Regards, Harry |
Fri, Feb 15 2008 12:06 PM | Permanent Link |
"Hershcu S" | Tim
Will the CachedUpdates issue included on this version? Sorin |
Fri, Feb 15 2008 2:46 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Scott,
<< - Replication for the ElevateDB Server using a publish/subscribe model >> It will basically allow any remote session to subscribe to an ElevateDB Server database (or subset of tables in a database) that has first been published by the ElevateDB Server, and then synchronize with that same ElevateDB Server at an interval determined solely by the remote session. -- Tim Young Elevate Software www.elevatesoft.com |
Page 1 of 3 | Next Page » | |
Jump to Page: 1 2 3 |
This web page was last updated on Thursday, July 4, 2024 at 07:01 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |