"Dan Byers" <goofygraffix_at_geemail_dot_com> wrote in message
news:web.47b1d8a8e388923da8d0b25a0@news.povray.org...
> "Gail Shaw" <initialsurname@sentech sa dot com> wrote:

> In their defense, a lot of the code is for generating SQL on-the-fly for
viewing
> certain windows, screens, whatever, based on the user selecting certain
options
> in whichever screen they're using.

No defense. SQL code embedded in the app means that changes to the DB
structure are near-impossible, and if the code isn't performing properly, a
DBA can't do anything

> BTW we're talking about a telco billing
> application with over 300 tables

> They do use a large number of stored procs for
> the real heavy-lifting (I counted almost 700).

Is that all? I count in one of my DBs and I've got close on 1000 tables and
3000 procs. Couple hundred views as well. This is for an app with fully
customisable searches, screens where the users can customise what columns
they see, from what tables, if they don't like the default

Post a reply to this message