1 2 Previous Next 16 Replies Latest reply on Sep 19, 2018 12:56 PM by jflack

    Designer Vs. SQL Developer

    FC60

      Some months ago, I search informations about the old tool (Designer vs. SQL Developer ).

      Now the company wants to change Oracle Designer  to modeling database with a new tool.

      It's sufficient to use SQL Developer  Data Modeler or is better to buy Enterprise Architect or Power Architect or others software?

      Thanks for all suggestions

        • 1. Re: Designer Vs. SQL Developer
          EdStevens

          FC60 wrote:

           

          Some months ago, I search informations about the old tool (Designer vs. SQL Developer ).

          Now the company wants to change Oracle Designer to modeling database with a new tool.

          It's sufficient to use SQL Developer Data Modeler or is better to buy Enterprise Architect or Power Architect or others software?

          Thanks for all suggestions

          "Better", like beauty, is in the eye of the beholder.

          What criteria does YOUR organization use to define "Better"?  Exactly how do you expect to  use the selected tool?  Who will be using it (end users, DBAs, application developers?).

          • 2. Re: Designer Vs. SQL Developer
            FC60

            Thanks Ed,

             

            1. I'm developer and data architect - I create a logical model for a table, I modify a table, I rename, I delete (table or columns) and I use only Designer (Entity Relationship Diagrammer)
            2. I call the DBA - He creates the script(s) from Designer

             

            I know (they said to me) that with Designer they can to create some reports to have the also documentation on the attributes if we describes all our columns in the write way.

            • 3. Re: Designer Vs. SQL Developer

              It's sufficient to use SQL Developer Data Modeler or is better to buy Enterprise Architect or Power Architect or others software?

              Your org should do what many other companies do:

               

              1. write a requirements doc - it should include a list of all functionality you want in a product and a rating for each item of how desirable/necessary that item is

               

              2. acquire copies of both products - review the products and the documentation

               

              3. have people from each company, if possible, make a presentation for their product where you can ask questions.

               

              4. actually evaluate each product and have the evaluators mark each item in the requirements doc with a rating as to how each product actually performed as related to that requirement item.

               

              5. meet and discuss the results of the above process

               

              In other words - your org needs to make an INFORMED decision AFTER actually using each product.

              1 person found this helpful
              • 4. Re: Designer Vs. SQL Developer
                GregV

                Hi,

                 

                It depends how much you want to be able to do. I decided to use SQL Developer Data Modeler for my DB modeling because it's fairly easy to use and is free. It can hold both logical and physical models, so I can store (almost) all my application objects in a Design. I say almost because there are a few objet types missing: Scheduler objects (programs, jobs, etc.), materialized view logs, system triggers. The workaround is to embed them in a fake pl/sql unit but I wish there were a real support. Apart form that it's quite functional, with a SVN built-in plugin.

                You can create reports showing the tables and their columns, along with their descriptions.

                Since it's free there's no official support. You can use this community for help. You can submit bugs and ER through SRs but that seems to be a facade. Nothing really moves. I don't know how it works with the Feature Exchange place. I submitted a couple of things there, but there's no follow up. For example:

                 

                https://apex.oracle.com/pls/apex/f?p=43135:7:::NO:RP,7:P7_ID:44141

                 

                You'll notice there's a score of 10 for this one.

                1 person found this helpful
                • 5. Re: Designer Vs. SQL Developer
                  FC60

                  GregV,

                  For me SQL Developer Data Modeler it's sufficient, the DBAs have also Toad to manage the DBs.

                  As you say, it's free, but not supported? Sometime the supported sw are less supported than free tools. We pay Hitachi to support Pentaho, but the last two questions don't have answers...No comment...

                   

                  Finally, I have found an old DBA that knows Designer very well and he has said to me that one of things that we need to verify is if SQL Developer Data Modeler can create an "Alter table..." script when I add a column in my Data Modeler file.

                  Another thing is if I can share an entity between two schemas (always in Data Modeler).

                  Thanks.

                   

                  This community is great, sometime we find arrogant people , but my grandmother said: Do not look gift horses in the mouth!

                   

                  Thanks

                  • 6. Re: Designer Vs. SQL Developer
                    thatJeffSmith-Oracle

                    >>Since it's free there's no official support. You can use this community for help
                    NOT TRUE.

                     

                     

                     

                    If you have a database under contract with My Oracle Support, then SQL Developer SQL Developer Data Modeler, SQLcl, and ORDS are all covered. Same deal with APEX.

                    1 person found this helpful
                    • 7. Re: Designer Vs. SQL Developer
                      thatJeffSmith-Oracle

                      We have no plans to build a CLI for the Data Modeler. I've left the request open vs rejecting it for the moment.

                      1 person found this helpful
                      • 8. Re: Designer Vs. SQL Developer
                        thatJeffSmith-Oracle

                        Finally, I have found an old DBA that knows Designer very well and he has said to me that one of things that we need to verify is if SQL Developer Data Modeler can create an "Alter table..." script when I add a column in my Data Modeler file.

                        Another thing is if I can share an entity between two schemas (always in Data Modeler).

                        Thanks.

                         

                        Yes - alter scripts https://www.thatjeffsmith.com/archive/2012/03/diffs-and-alter-scripts-via-oracle-sql-developer-data-modeler/

                         

                         

                        and

                         

                        No - shared entitys, one table in two schemas.

                         

                        A table belongs to a single user in a model.

                         

                        You can have a linked objects between two models.

                        1 person found this helpful
                        • 9. Re: Designer Vs. SQL Developer

                          No - shared entitys, one table in two schemas.

                           

                          A table belongs to a single user in a model.

                           

                          You can have a linked objects between two models.

                          Presumably that will change somewhat if you plan to support the Application Container functionality of 12.2?

                          • 10. Re: Designer Vs. SQL Developer
                            thatJeffSmith-Oracle

                            I don't know of any multitenant support plans for the modeler - probably better a question for the modeler forum though

                            1 person found this helpful
                            • 11. Re: Designer Vs. SQL Developer
                              FC60

                              Thank you all for your answers, I resume and I forward to my project manager.

                              • 12. Re: Designer Vs. SQL Developer
                                GregV

                                thatJeffSmith-Oracle wrote:

                                 

                                 

                                If you have a database under contract with My Oracle Support, then SQL Developer SQL Developer Data Modeler, SQLcl, and ORDS are all covered. Same deal with APEX.

                                Yes, theorically. I submitted an SR about a bug regarding the Unit Test feature of SQL Developer. I even started a thread about it:

                                Unit Test: how to let input parameters of the procedure to test take their default values?

                                 

                                You said that time the fix was not likely to be implemented. Unfortunately I can't access the SR anymore since I moved to another company. I guess the SR died out. So yes there's support, but I think only critical issues are dealt with, and those issues are reported in this community first most probably.

                                Regarding the ER about having the CLI, that time a person from Oracle support called me and told me it would be implemented in the next version (that was about 2 years ago). Well, I know now he was just lying and wanted to close the SR.

                                1 person found this helpful
                                • 13. Re: Designer Vs. SQL Developer
                                  thatJeffSmith-Oracle

                                  I'm happy to look at any SR you want. We have a dedicated support team for these products and they take many cases a day.

                                   

                                  If someone told you a feature was coming in a particular time frame, that was not good. We don't promise features, we don't give release dates as a corporate policy.

                                   

                                  But I will tell you if i can whether it's likely a feature will happen or not. There are no plans for a CLI on the modeler today.

                                  • 14. Re: Designer Vs. SQL Developer
                                    FC60

                                    Hello Jeff,

                                    Probably SDDM will be our futur tool to data modeling. I'm searching info about "...You can have a linked objects between two models..." can you say to me if I can find something in you blog ThatJeffSmith? To have more information.

                                    Thanks

                                    1 2 Previous Next