Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: iain on October 16, 2002, 06:08:32 am

Title: Corporate Edition
Post by: iain on October 16, 2002, 06:08:32 am

The 'Corporate Edition' is mentioned throughout version 3.5 can you tell me what the pricing model is for this and also whether support for Oracle repository is available

Title: Re: Corporate Edition
Post by: kelly_sumrall on October 16, 2002, 09:18:17 am

I think the Corporate Edition will be $20.00 USD more than the Professional version.  As far as Oracle, I'm sure it will be available.

Title: Re: Corporate Edition
Post by: Gary Wong on October 17, 2002, 09:05:57 pm

Actually, if you mean Oracle Repository (as in Designer CASE tool) then the answer is probably no.    The underlying metamodel in the Oracle Repository is quite complex and it would be a huge undertaking for EA to 'talk with' the Repository.

Gary

Title: Re: Corporate Edition
Post by: Marek Brezina on October 22, 2002, 01:50:06 am

I have problem with creating database for EA. When creating tables an error message appears:
Warning! The maximum key length is 900 bytes. The index 'aaaaat_objectproblems_PK' has maximum length of 1024 bytes. For some combination of large values, the insert/update operation will fail.
Thanks Marek

Title: Re: Corporate Edition
Post by: Marek Brezina on October 23, 2002, 04:41:40 am

I solved the problem, I changed type nvarchar on varchar, but another appeared when imported model from xml, "Operand type clash: int is incompatible with ntext"

Title: Re: Corporate Edition
Post by: gsparks on October 28, 2002, 04:14:11 am

Hi All,

The Corporate Edition is being released shortly and will sell for 179$ per license as opposed to 149$ for the Professional, a difference of 30$. The Coporate Edition will connect to a MySQL or a SQL Server based repository. Support for Oracle, DB2 and PostgreSQL is planned.

We will offer a 20$ Professional to Corporate upgrade for the month of November to allow existing users a chance to upgrade at a discount.

The issues regarding the error messages on creating SQL Server tables has been resolved as has the "Operand type clash" issue...thanks for the feedback on these Marek.

Geoff Sparks