You've developed the greatest thing since sliced bread, but the Database Administration team won't let you hook it up to their database. From schema to security to space and performance issues, this is a high-level overview of what DBAs see as their most important challenges when integrating other people's code into their system. A fascinating look at how the other half works.

Luis Cazares (9/21/2012)
It would have been great to understand the difference between row-by-row programming and set based programming (or procedural language and declarative language). It would be important to notice when is it better to use one or the other.

Brandie Tarvin (9/24/2012)

---

I've never used object databases. Can you point me to some reference material? EDIT: Reference material regarding your reporting comment, that is.

3.15 Do Not Use Object-Oriented Design for an RDBMS
Rationale:
Many years ago, the INCITS H2 Database Standards Committee (née
ANSI X3H2 Database Standards Committee) had a meeting in Rapid
City, South Dakota. We had Mount Rushmore and Bjarne Stroustrup as
special attractions. Mr. Stroustrup did his slide show about Bell Labs
inventing C++ and OO programming for us, and we got to ask
questions.
One of the questions was how we should put OO stuff into SQL. His
answer was that Bell Labs, with all its talent, had tried four different
approaches to this problem and came to the conclusion that you should
not do it. OO was great for programming but deadly for data.