Please correct me if I'm wrong, but isn't it bad parctice to place multiple applications in the sam db. My SA wants me to use the same db for all of the apps I develop and then just name the tables accordingly. Can someone please give more insight on why this is bad, and my chances for doing it right the first time will be better. Thanks.There is no one rule to judge this. It all depends on the nature of your application. Are all of them data centric applications? Do they have large batch jobs running in the DB server all the time? Are they just providing UI for users to enter data? If all your applications don't justify to have their own database, I don't think your SA is so far away off on this.|||It also keeps the number of frivolous(sp?) databases down so there isn't a new database every week that needs to be added to the maintenance and backup jobs.
When one of your applications grows into large enough of a project, you'll be able to twist some PHB's arm and get it it's own real database.|||Thanks, I guess I was wrong. I'm always paranoid about nesting muliple objects under one source when multiple people have access. I assumed that the chance for naming errors were very high. Thanks again.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment