Skip to main content

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

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
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
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.
Tom said…
I wonder what Oracle does if they realize people aren't going to buy it for that.
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
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.
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."
Roel said…
@Erik : SQL Developer itself is free. The Data Modeler is a separate product that is not free.
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
Matthias said…
Too expensive for us :(
Guess we'll keep on using Visual Case.
http://www.visualcase.com/
i like this
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

Popular posts from this blog

Fix Interactive Report headers issue when using a Region Display Selector

When you have multiple Interactive Reports (IR) on your page and use a Region Display Selector to mimic tabs, you might notice some weird behaviour in the IR headings if you switch tabs. The headings are not positioned correctly and you get an extra empty row under the headings. It just looks weird and ugly. But if you resize your browser window, it all looks fine again (until you switch to another tab..) So can we fix this by creating a Dynamic Action that mimics that "browser window resize" event? Yes we can! Create a Dynamic Action that fires on Click of the jQuery selector li.apex-rds-item a . That should fire a JavaScript snippet :  apex.event.trigger(this.triggeringElement, "apexwindowresized"); So now a click on a tab not only switches from one IR to another but also fires that event that will "autofix" the IR headers. A simple solution for an annoying problem. This applies to APEX 5.0, I assume it will be solved in 5.1.

How to create neatly formatted Excel documents using PL/SQL?

If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...