Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Any interest in Oracle-related articles???

Any interest in Oracle-related articles???

Scheduled Pinned Locked Moved The Lounge
databasesql-serveroraclesysadminhelp
26 Posts 10 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Daniel Turini

    Mark Conger wrote: In their defense, most of them are ex-COBOL programmers. The worst people to get programming on SQL + OOP, IMHO. I often avoid COBOL programmers like hell, it's hard to change their mind. I only try it if they are 25 years old or less. And they usually don't mix well with other programmers, not because of COBOLers fault, but normally COBOLers are seen as vile even by VB programmers! Someday, maybe, I write a "Hiring staff: DO's and DONT's". I have lots of experience in it. Specially in the DONT's :) My latest article: SQL Server DO's and DONT's[^]

    M Offline
    M Offline
    Mark Conger
    wrote on last edited by
    #21

    Well, We have a bunch of COBOL proggies that have been doing this a long time (old HP3K system). You're right, they usually just don't get it most of the time. Mainly they need a best practices and tuning course. Mark

    1 Reply Last reply
    0
    • M Mark Conger

      That mentality is pretty common for 'oracle guys' (of whcih I'm one :) ). When you say Data Service layer, are you talking about business rules? how complex is it? If its fairly basic integrity enforcement type of stuff, use PL/SQL. However if its full blown logic, extract it out into another technology. PLSQL can do it but tends to bog down the more complex the package gets (this way lies Dynamic SQL :wtf:) If I'm not understanding what you are trying to do, let me know. Mark

      L Offline
      L Offline
      lejuan5150
      wrote on last edited by
      #22

      our environment includes a very large oracle database which we use microsoft technologies to access (ado, oo4o, .net oracle provider) ... we want to wrap oracle so all applications must access it through our data service layer (mainly to isolate them from oracle changes) ... as far as business rules, corporate business rules will be included in our data services, but application specific data rules will be outside the data services the following diagram outlines (in a very simple way) two approached we were discussing http://www.lejuan5150.com/lejuan5150/media/dataAccessTier.jpg[^] hope this clears things up a bit ... thanks for your time

      M 1 Reply Last reply
      0
      • M Mark Conger

        You must be using it after they got it working half way decently. I've heard its a bit of a resource pig, but what from Oracle isn't. I just wish all these different 'client's didnt require the normal SQL*Net client underneath. Mark

        C Offline
        C Offline
        Chris Meech
        wrote on last edited by
        #23

        There's no doubt that having to have the SQL*Net client installed, puts off a lot people. Perhaps I'm spoiled here at a bank where even the user's are on PC's with minimum 256M of memory along with 10G or 20G of hard drive space. Although when I first started at this project over 5 years ago, some of the code that I came upon was pretty atrocious from a resource point of view. InitInstance for a dialog opening a cursor to retrieve entire table(s) and lock them. Really silly stuff. Or the UI is designed to exactly match a table definition. I think version 7 of the library had some quirks but I've been on version 8 for about three years now and it's pretty solid. The whole database will be going to version 9 sometime next year. That migration should be fun. :) Chris Meech "what makes CP different is the people and sense of community, things people will only discover if they join up and join in." Christian Graus Nov 14, 2002.

        M 1 Reply Last reply
        0
        • C Chris Meech

          There's no doubt that having to have the SQL*Net client installed, puts off a lot people. Perhaps I'm spoiled here at a bank where even the user's are on PC's with minimum 256M of memory along with 10G or 20G of hard drive space. Although when I first started at this project over 5 years ago, some of the code that I came upon was pretty atrocious from a resource point of view. InitInstance for a dialog opening a cursor to retrieve entire table(s) and lock them. Really silly stuff. Or the UI is designed to exactly match a table definition. I think version 7 of the library had some quirks but I've been on version 8 for about three years now and it's pretty solid. The whole database will be going to version 9 sometime next year. That migration should be fun. :) Chris Meech "what makes CP different is the people and sense of community, things people will only discover if they join up and join in." Christian Graus Nov 14, 2002.

          M Offline
          M Offline
          Mark Conger
          wrote on last edited by
          #24

          V7 was not pretty. I worked alot with it in relation to the Oracle Applications product which used it for some external utilities in accounting. I skipped v8.0 and next saw it in v8i/8.1 It seemed more reliable then, just a pain to install :) v9.2 Db is not much different than v8i. the really nice stuff is when you start using RAC clustering :) I built up a couplle Linux boxes with this and was surprised how easy it was. Not lieke the old Parallel server days. Mark Mark

          1 Reply Last reply
          0
          • L lejuan5150

            our environment includes a very large oracle database which we use microsoft technologies to access (ado, oo4o, .net oracle provider) ... we want to wrap oracle so all applications must access it through our data service layer (mainly to isolate them from oracle changes) ... as far as business rules, corporate business rules will be included in our data services, but application specific data rules will be outside the data services the following diagram outlines (in a very simple way) two approached we were discussing http://www.lejuan5150.com/lejuan5150/media/dataAccessTier.jpg[^] hope this clears things up a bit ... thanks for your time

            M Offline
            M Offline
            Mark Conger
            wrote on last edited by
            #25

            hmm, ok.. So you want a central point for everyone to connect tup to so they can interop with the Oracle DB. Probably more liekly to do something liek COM+ for that or if you can set it up use a Web Service. Mark

            1 Reply Last reply
            0
            • M Mark Conger

              Ok, I'll start thinking about topics this weekend :) What does a DBA do? Well, I've been told that DBa stands for Does Bull$#!% Alot :P Seriously though, most RDBMS's don't maintain themselves without a little guidance. SQL Server kinda spoils ya; It's install and go. Everyone else you have to worry about memory settings, disk allocations, planning. Generally I spend one to two hours a morning reviewing logs and dumped trace information for the database engine. After that, I take care of any requests (You'd be amazed how many developers can't deal with adding a column to a table that already has data in it). I also spend alot of time looking at the database as a whole looking for badly coded SQL (which there usually is alot of) and places where I can tune the system via structural changes like partitioning. Mark

              G Offline
              G Offline
              Giles
              wrote on last edited by
              #26

              Mark Conger wrote: I also spend alot of time looking at the database as a whole looking for badly coded SQL (which there usually is alot of) Would be great to see some examples of boopers in SQL, and some tips.

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups