Forgot your password?
typodupeerror
Databases Programming Software Businesses IT

Oracle To Offer A Free Database 370

Posted by Zonk
from the nice-if-true dept.
An anonymous reader writes "ZDNet News reports that Oracle is likely to announce a free version of its Oracle 10g Database. Oracle Database 10g Express Edition will be free for development and production use, and could even be distributed with other products. What does this mean for the future of MySQL and PostgreSQL?" From the article: "By introducing a free entry-level product, Oracle intends to get more developers and students familiar with its namesake database, Mendelsohn said. Those customers, Oracle hopes, will eventually upgrade to a higher-end version."
This discussion has been archived. No new comments can be posted.

Oracle To Offer A Free Database

Comments Filter:
  • Nice TRY (Score:0, Interesting)

    by LogicallyGenius (916669) <{ni.oc.oohay} {ta} {1-tuaR_attaduruG}> on Monday October 31, 2005 @08:34AM (#13914065)
    But, I will go for Open source and free of any license; so which should I go for ?
  • SQL For Fun? (Score:5, Interesting)

    by Goo.cc (687626) * on Monday October 31, 2005 @08:34AM (#13914070)
    I've been meaning to ask this for a while on Slashdot, but how many people here use a SQL database as part of a hobby or for fun?

    I currently have PostgeSQL running on my Tiger box. I initially installed it just to experiment with SQL and database normalization, but now I keep my comic book inventory on it. (I know that this is like swatting a fly with a nuclear weapon but I enjoy using PostgreSQL and it is FREE software.)

    As for Oracle's announcement, I think that it can be a good thing, provided you are willing to live with their restrictions and only need support for Linux (x86?) and Windows.
  • hopefully.. (Score:2, Interesting)

    by icecow (764255) on Monday October 31, 2005 @08:35AM (#13914072)
    'hopefully' is code for 'by then they somewhat locked in'
  • Restrictions? (Score:2, Interesting)

    by mysticwhiskey (569750) <mystic_whiskey&hotmail,com> on Monday October 31, 2005 @08:36AM (#13914076)
    I guess it all depends on the restrictions applied to the "free" version. Is it crippled in any way? Does distribution of the free version require certain conditions (ie development criteria, use of application, etc)?

    The article states hardware restrictions of "one processor, with 4GB of disk memory and 1GB of memory", so this may automatically disqualify applications of a certain scale.

  • Weak passwords? (Score:2, Interesting)

    by bigtallmofo (695287) on Monday October 31, 2005 @08:43AM (#13914113)
    Will the free version of Oracle be subject ot the same weak Oracle password encryption [com.com] scheme that the commercial version is?

    I've duplicated a number of techniques in the SANS article [sans.org] to make me leery of password security on my Oracle machines.
  • by spectrokid (660550) on Monday October 31, 2005 @08:45AM (#13914118) Homepage
    Actually their new plug in for Visual Studio is not bad at all. Personally I think it is better then JDevelloper, provided you don't code Java, of course. The main thing I have against Oracle is that I can't make e.g. an Access file which works out of the box on every computer. You always need to get the drivers set up properly first, and you can't do that without (local) administrator rights. That is where MS (obviously) can shamelessly profit from their monopoly.
  • by backslashdot (95548) on Monday October 31, 2005 @08:45AM (#13914126)
    I am choosing Oracle over MySQL. Why? Because SCO is still refusing to sheild MySQL users from lawsuits that directly result from this deal with SCO. Note: I am not asking to be protected from whacko frivolous lawsuits, I am asking that MySQL protect us from a lawsuit by SCO that results from SCO making the allegation that MySQL placed commercial SCO code in MySQL in violation of _this_ agreement.

    If MySQL is super confident that this deal cannot possibly result in any lawsuit to us, they can easily indemnify us from SCO lawsuits.

    According to SCO's press release ( http://ir.sco.com/ReleaseDetail.cfm?ReleaseID=1720 37 [sco.com] ):

    "The SCO Group, Inc. ("SCO") (Nasdaq: SCOX), a leading provider of UNIX(R) software technology for distributed, embedded and network-based systems, today announced that it has entered into an agreement with MySQL AB to jointly deliver a certified, COMMERCIAL version of the popular MySQL database for SCO OpenServer 6"

    Clearly there is wiggle room for them to file a delusional lawsuit styled after the IBM lawsuit claiming that MySQL used SCO resources and knowledge to "improve the GPL version". Stop laughing, this is what they are saying about linux. And when that goes down in flames, they'll need another whacko lawsuit to pump their stock up one last desperate time so the execs can completely sell off their remaining shares.

    Once more, if MySQL is super confident that this deal cannot possibly result in any lawsuit to us, they can should have no problem sheilding us from SCO lawsuits.
  • by Daniel Dvorkin (106857) * on Monday October 31, 2005 @08:52AM (#13914162) Homepage Journal
    Sounds to me like the difference is that you're allowed to use this new edition for (limited) production use as well. Now, I'm sure there are a ton of small shops currently using the free, "non-production" edition for production apps, but of course they're not really supposed to; this gives them a legal route. But I still think the deliberately crippled nature of the product makes it unattractive relative to the open source contenders, in terms that even PHB's will understand: "Boss, if we go with 'free' Oracle, we're going to run into that disk space limit pretty fast, and then we'll have to pay $$$."
  • by ticklejw (453382) on Monday October 31, 2005 @09:01AM (#13914204) Homepage
    You couldn't pay me to use Oracle. I'm not sure what they expect to gain by this, but it certainly isn't my respect. If they want to generate more interest, they can make a product that works and doesn't require you to hire an Oracle-certified specialist to maintain all the little quirks and problems.

    Go ahead, -1 flamebait or troll or whatever, I just really don't like their database software, and especially now that MySQL has the features that it does in version 5 and from what I hear PostgreSQL has been keeping up, there's no reason to pay half a million dollars for something sub-par. There's also no reason to pay free for the limited, restricted edition only to have to use your half million to upgrade when you outgrow the restrictions.

    Yet another example of where Free software wins.
  • by KiloByte (825081) on Monday October 31, 2005 @09:11AM (#13914251)
    The problem with Oracle is, it doesn't scale at all. It is meant to do grid computing, but can't really do anything smaller.

    How often do you need to use a cluster for your data? If you are a major organization, then you will, but the majority of installations are pretty small. Firewall/website logs. Customer data. And so on.

    I have once developed a workshift-tracking application for a company with around 200 employees. A couple of years later, the total data takes 17MB. Why would you use Oracle if MySQL works faster and takes 1% of the resources? A minimal installation of Oracle 10g takes ~800MB of memory, and will take over ten hours to install on a machine with 512MB ram, on the other hand, on my firewall (486, 32MB ram) MySQL can handle Apache logs (only about 200k hits, though) taking a split second for any reasonable query.

    Oracle works better for clusters.
    MySQL works better for a single machine.

    MySQL is a lot faster. Oracle takes distributed processing a lot better.
    But uhm, where does a crippled version fit in the picture?
  • by ShootThemLater (5074) on Monday October 31, 2005 @09:27AM (#13914367)

    I'm just thinking of the overhead of Oracle, which may not be that suited to an embedded application. Of course, if this free version has lower hardware requirements, then yes that would be appropriate. However in this case I doubt that this would be suitable for say, mobile devices.


    I agree, it has a significant overhead - particularly in memory and disk footprint. I should clarify though - when I referred to mobile use, I was thinking of users with reasonably high end laptops who need to use a database-dependent application while offline. So while in the office, they could connect to a main server running 'proper' Oracle with live data, and when on the road, they could use a personal installation with the XE server and cached data. The advantage for the vendor is that they can use the same database for both.
  • SQL Express (Score:3, Interesting)

    by MajorDick (735308) on Monday October 31, 2005 @09:28AM (#13914372)
    these requirments are nearly Identical to SQLExpress, the renamed MSDE from MS.

    But on a windows system WOW is it handy for building apps with embeeded db , (1000 times better than Access, both in performance reliablity and coding for it.)
    Hopefully Oragle will make it that easy for Unix/Linux?Solaris development.
  • by doedel (852791) on Monday October 31, 2005 @09:31AM (#13914388)
    Well, it doesn't affect them at all. And not Mr. Mendelsohn got that wrong but TFA and our /. poster.

    You could download and test Oracle's DBs for free for quite a while - but only now you can use them for free in a production environment. That's clearly aimed at MS' offerings like MSDE and SQL Server Express and not at MySQL or PostgreSQL.

    Also Oracle is an enterprise DB and MySQL, PostgreSQL or even MS SQL Server can not be compared to it in that regard. This also means you need trained staff to administer it - forget about just downloading and using it. Tried to get a demo of Oracle's XML Publisher working - I know what I'm talking about ;-).

    So if your shop is already using Oracle's DBs this is a nice offer for the occasional small project. But for everyone else, just stay with what you know and love - whether it's MySQL, PostgreSQL, MS SQL Server or something else.

  • by electroniceric (468976) on Monday October 31, 2005 @11:28AM (#13915180)
    Oracle also has a number of certifications that make it very attractive in certain industries like defense, healthcare, etc. I work in the medical field, and a free 4GB-max "validated" Oracle database is a huge boon to a wide variety of medical ISV's. Given that's it free to redistribute, the OSS/proprietary thing kind of takes a backseat for a lot of these ISVs.

    By the same token, I also don't think it's going to drive sales in the way they think it will. Databases are slowly but surely going commodity, at least at the lower end of the market, and this merely reinforces that trend. And along with that, there's an increasingly robust set of tools to obviate the differences between these database for most uses that don't demand extreme peformance, from Hibernate and ORM packages to ADODB and other database-independence layers in PHP to .NET's layered data architecture.

    As a Postgres user, I'm hopeful that Sun's proclaimed interest in Postgres will result in this kind of "validation". However, given Sun's reputedly somewhat lackadaisical commitment to staffing OOo, I'm not holding my breath. With Postgres' extensibility and extremely high-caliber core developer base, I think a strong commitment to validation by Sun could make it a real contender in the medium enterprise space. Validate it, clean up a few features (notably auto-vacuum and passable auto-tuning, maybe some multi-master replication), throw in a simple deployment for ORM or database indirection, and you've effectively moved that commoditization up one layer from the small website developer level.

    In the long run, I don't see how this gets Oracle out of the need to transition its core revenue off of its database licenses.
  • by Eivind Eklund (5161) on Monday October 31, 2005 @12:49PM (#13915870) Journal
    MySQL doesn't work. It is up and running five minutes; significant difference.

    Yes, I work day to day with MySQL, due to the cost of migration. No, I don't feel good about routinely having to deal with corruption in production databases. It's not acceptable. Yes, it also happens with InnoDB.

    Eivind.

  • by stanmann (602645) on Monday October 31, 2005 @01:01PM (#13916026) Journal
    So how does Sybase work if you want to do a point in time restore to halfway between to backups? I've been looking for the answer to that question for quite a while. What if you need to rollback to just before a certain committed transaction?
  • Re:It Could Backfire (Score:5, Interesting)

    by oni (41625) on Monday October 31, 2005 @04:09PM (#13917525) Homepage
    What I've seen a lot of are databases designed by programmers - good programmers too, these guys weren't slouches. They didn't have any formal training in databases or maybe they hadn't paid attention. Programmers tend to approach database design by thinking, "what data structures do I need to get out of this?" Someone more experienced in database design approaches the problem by thinking, "what relationships are here and how do I model them?"

    Here's a real-world example. A web-based application that I was hired to extend and maintain included a system for users to exchange the lesson plans they created on the site with other users. In doing this, the users built up something like a buddy list. "These are the people that I often share with." Or you can think of it as being like an address book.

    With me so far? OK, the programmer (who was very sharp - probably better at this than I am) approached the database thinking, "what data do I need from this thing," and decided that what he needed was a comma delimited list of userIDs. So he physically stored the buddy list in the database in like a char(500) as a comma delimited list.

    That was actually great for what he was doing. He was just showing a user their buddy list. Unfortunately, that isn't normalized. So, there is a question you can ask which can't be answered by the data. That question is, "how many people have userID 50 as one of their buddies?"

    See, the correct way of doing this is to have a many-to-many relationship which you implement with a table containing just two columns, userID and BuddyID. So if I'm user 12 and users 13,14, and 15 are my buddies, I have three rows in that table:

    UserID BuddyID
    12 13
    12 14
    12 15

    Now if I need to ask, "how many people have userID 50 as one of their buddies" I can do select count(*) from X where BuddyID = 50

    BTW, I actually fixed this one not by normalizing but with a hack. I appended 0 to the front and back of the buddy list, then I could do select count(*) from user where buddylist like '%,50,%' But hacks aren't how I make my living. I'd prefer to do things the right way. What my boss wanted was, every time you look at this page it shows you who has you set as a buddy. Kind of like what Slashdot does with the "fans" page. If it was normalized, that would be a scan of an indexed column. It would be lighting fast. so fast the page would practically load before you even clicked the link. But doing a "like" on a big char field is slow.

    There are I'm sure still other questions that the un-normalized database cannot answer. Also there are problems with deleting users and, the big one, overflowing that char(500). "How many buddies can a person have?" I was asked. "It depends" I said. If all my buddies are low number IDs, I can have a lot. If my buddies are high number IDs, I can have fewer. It's all just huge mess! Of course, it worked according to the original specification though.

    I have a lot of respect for the guy who wrote it. And I'm not tooting my own horn either. I've have other people look at databases I've designed and just torn them to pieces. This is just one example where I just happen to know that he did it the wrong way.

  • Re:It Could Backfire (Score:2, Interesting)

    by kpharmer (452893) on Monday October 31, 2005 @04:19PM (#13917601)
    > All the things you mention are normal everyday DBA issues, not-specific to Oracle.
    right

    > The issues you're referring to are mostly problems for the development DBA, and that's where all the smarts are necessary.

    This might be part of the confusion: don't separate production vs development dba roles. You're right - that a production dba role can be very simple. So why even bother with it? Unless you've got complex security requirements for it, you are far better off without that role.

    So then, back to the dba role. Yep, you need to be able to write complex sql, design a data model, tune the database, select the hardware, and plan and administer a data recovery procedure. And yes, it is a hard job.

Premature optimization is the root of all evil. -- D.E. Knuth

Working...