General discussion

  • Creator
    Topic
  • #2314004

    MySQL vs Oracle

    Locked

    by jcoffey ·

    I am not an IT person, so when people begin talking about platforms and such I get lost. I currently have a consultant developing a web portal database in MySQL for a client of ours. The company I am developing it for has an Oracle platform. They are insisting we convert this to Oracle right away. The problem is that we are under a tight deadline. My consultant is not conversant in Oracle and it will really slow the project down. This is not a huge database by any means. It will be tracking results against certain performance criteria. (Less than 500 performance criteria). We are proposing that we complete the development in MySQL and then convert to Oracle at a later date? What risks do we run by taking this approach. I am certain that the change to Oracle will slow down the project by several months because internal staff responsible for Oracle will be caught up in other priorities. Can you help

All Comments

  • Author
    Replies
    • #3539563

      MySQL vs Oracle

      by madestroitsolutions ·

      In reply to MySQL vs Oracle

      My good friend, you ask a lot for 75 points….. lol, but it’s ok….

      First of all, it shouldnt matter much what database you are using on the web portal, unless of course you want to share information between them. MYSQL is pretty kewl, fast andsimple to use, ans most importantly, ITS FREE. Oracle is much more robust and full of features, but it costs a fortune. Which one do you use? If you already have Oracle, then why not use it? On the other hand, if its a small database, and it will not incur in heavy traffic, or complex data movement, why complicate your life trying to switch it to Oracle?…

      Under the developing point of view, I can probably guess that these people probably don’t know anything about MYSQL, which is why they want to turn it to Oracle. On the other hand, it is always advisable to keep everything in a single format, so if you use Oracle as a backend, you want use Oracle as the front end of the website too.

      To make a long story short, if these databases will work independently of each other, then it’s up to you (I would change it to Oracle though, just in case I decide to do something in the future). However, if the databases need to share information, then you must definitely change it to Oracle to keep everything together and in the same page.

      If your consultant is not conversant in Oracle, then find someone who is. There are a lot of people out there these days you know?….

      Hope that helps

      Good Luck!

      • #3373564

        MySQL vs Oracle

        by jcoffey ·

        In reply to MySQL vs Oracle

        Thanks for your help….we now have a better understanding of what we are dealing with. Your info has been very usefuly. Thanks,

    • #3525548

      MySQL vs Oracle

      by williams_funmi ·

      In reply to MySQL vs Oracle

      No use killing a mosquito with a sledge hammer. every technology has a life span of at most between Four to Six years before a review, if you can define or project your clients’ data and application growth for the next four years plot it against thegrowth of Oracle and MySQL you will be faced with the reality of (i) security (ii) support (iii) cost of maintenance (iv) acceptablity.

      No use having a product you can not have around in a couple of months or need to spend huge sum to maintain orprovide support for or have to buy endless list of add-in for security.

      If you see at the end of the tunnel a bigger opportunity for growth then go Oracle, it should be seamless to plug and play, whatever you have developed be it asp, XML, web portal, C anything into Oracle, most likely the problem you may encounter would have been documented and support would be readily available, nothing is as so scary as having a 24/7 database crisis without reliable support available. (You just do not want to be in the line of fire)

      Bottom line you need to find out the true cost implication of this option(s) and sit with your client both of you should face the truth, no use been penny wise pound foolish, and address it squarely, because if he (your client) goes out of business because of wrong choice, sooner or later than you think the effect of your error will surely catch-up with you.

      So you can sincerely and truly answer the basic long term, budget and implementation question. that will go along way i.e. data-conversion issue, performance and support, Harware and license requirement plus other hidden or silent cost.

      You may also get freelance support personnel or contract this aspect out to Oracle, I do believe they would have in-house interm that would jump at this option(nto too sure but it is worth a try).

      • #3373563

        MySQL vs Oracle

        by jcoffey ·

        In reply to MySQL vs Oracle

        Thanks for your help. Your response helped us to understand more what we were dealing with. Thanks again,

    • #3373562

      MySQL vs Oracle

      by jcoffey ·

      In reply to MySQL vs Oracle

      This question was closed by the author

Viewing 2 reply threads