Skip to main content

Oracle SQL Developer Data Modeler available - but not for free....

By
Almost covered by yesterdays FMW 11g stampede, the production version of SQL Developer Data Modeler is available on OTN.
As expected (see this and this last years blog entry) this is not a free tool like SQL Developer or JDeveloper. It is a for-cost option of SQL Developer, and requires a separate license. And what are the license costs (as of yesterdays Pricing List): $3000 + $660 per year per Named User.
It looks really good. The functionality is about the same as the modeling part of good old Oracle Designer (it can even import the definitions from a Designer Repository). The full Internet Developer Suite costs $5800 + support per user. But then you get the all Designer functionality + Oracle Forms + Oracle Reports...
Is it worth the $3000? I don't have an opinion on that yet, do you?

Comments

Tobias Arnhold said…
Hi Roel,

$3000 + $660 per year! In my eyes it's to expensive.

Tobias
12:47 pm
Byte64 said…
Cough! Cough!
Three thousand bucks??!?!

It sounds a little bit too expensive, at least for my current needs of data modeling.

Thanks for pointing that out Roel!
Flavio
2:34 pm
Paul B said…
I've been using it for quite a while now and it's pretty good, but not $3000 plus dollars good.

I think I will just carry on using the early adopter release which you can use for free, as it was pretty stable.
3:44 pm
Tom said…
I wonder what Oracle does if they realize people aren't going to buy it for that.
4:14 pm
Chris said…
Hi!

That's a lot of money, but we were forewarned. Anyway, I hope nobody at Oracle gets the idea of selling overpriced add-ons to APEX instead of integrating them into the product.

Chris
8:10 pm
Raymond said…
Have a look at http://www.polderij.nl/happyfish/ it's 99 euro (windows only). I looked at a number of Mac and Windows ERD tools , but Happy Fish made me very happy. I used over the years all the big ones, Oracle Designer, Erwin, and my personal favourite ER/Studio. But for personal use all way expensive.
12:03 am
Erik Ykema said…
For me the information is confusing. The link you mention says indeed $3000 etc. However how do you interpret this (http://www.oracle.com/technology/products/database/datamodeler/html/datamodelerfaq.html#free):
"Is SQL Developer still free?

Oracle SQL Developer Data Modeler is independent of SQL Developer and has no impact on the release cycle or installation of Oracle SQL Developer.

Yes, Oracle SQL Developer is still free."
12:06 pm
Roel said…
@Erik : SQL Developer itself is free. The Data Modeler is a separate product that is not free.
12:20 pm
Unknown said…
the term-based licensing is available to data modeler similar to other Oracle tools. 660$ is for support / year to get updates, etc. Purchasing support is not a requirement but an option. If you believe you don't need support, you can go with term-based licenses (for 1 year for example). In addition to the term-based licenses, the GSA prices are much cheaper if your company is qualified for GSA.
R/ Zaf
10:46 pm
Matthias said…
Too expensive for us :(
Guess we'll keep on using Visual Case.
http://www.visualcase.com/
3:12 pm
www.oracledba.in said…
i like this
3:26 pm
Unknown said…
Google finds this blog on first page - so some updates:

http://www.oracle.com/technetwork/developer-tools/datamodeler/pricing-faq-101047.html

starting September 2010 Oracle SQL Developer Data Modeler became free software (now I am impressed :) )

hoppo
2:06 pm
Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good o...
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for ...
Post a Comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...
Post a Comment
Read more