Porter, Mark
MPorter at acsalaska.com
Tue Jul 29 13:24:51 CDT 2003
I've noticed that some contractors can be very short sighted. They are there for a specific job, care only for that specific job, and do not take the long term goals of the company at heart. They can be very good at what they do, but tend to do it using their own methodologies. There are many ways to architect software, and standards exist to keep everyone in the organization on the same page. If the software they create is to be maintained by your organization, it has to be made to your standards. Mark -----Original Message----- From: Mark L. Breen [mailto:subs at solution-providers.ie] Sent: Tuesday, July 29, 2003 9:21 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer]Architecture/how to do it advice Hello David, I would agree with you entirely. It is a mindset firstly, if you do not have that mindset, you have trouble up ahead. Secondly, that is what sprocs are for, Thirdly, they probably could combine some of the sproc calls into lesser return journeys which is better. Fourth, what happens when the app builds up the volumes of data, it may be OK now. Fifth, if you let them away with it now, they start using cursors and all sorts or other things, Best aim for it to be right at the start at least. Then when it goes wrong, at least you are starting from a good position. Finally, the so called experts must either have some really good reason to develop their system that way, or else they are not experts. Keep your nerve, you may be surprised how much you do know, Mark ----- Original Message ----- From: "David Lewis" <DavidL at sierranevada.com> To: <dba-sqlserver at databaseadvisors.com> Sent: Tuesday, July 29, 2003 4:49 PM Subject: [dba-SQLServer]Architecture/how to do it advice > > This seems to be a good collection of people with wide experience, so I'd > like to ask a strategy type question. I don't have any certifications, but > am reasonably experienced in vb, access and now sql server 2000. Nothing on > too large a scale, but what I've built is a sophisticated app for a brewery > to track and evaluate production and r&d. I've done my reading and have > tried to incorporate what I understand to be good practices (good quality > code, copious sprocs, udfs where appropriate, good security...) > > I am in the middle of porting much of the reporting part of the app to the > web (an intranet) to make it more easily available to users. I have hired > an outside consultant to help with much of it. He is not a db guy, so is > most comfortable with opening connections as needed on an asp page, sending > a query string over the network, etc. We argue constantly about many > aspects of architecture, for example the use of sprocs (he doesn't see the > need for them, doesn't understand their advantages, knows only that he can't > see them) in spite of me trying to explain the advantages, some of which are > not relevant to our situation (we are unlikely to suffer an sql injection > attack). However I am of the opinion that forming good habits is essential, > because sooner or later it will become important that something be done the > 'right' way, and if it is a habit you won't have to stop and think about it. > > The real point of this message is: he described to me another project he is > working on for a major state agency that will be web based. As he described > it, each time a user opens the app there are 500 round trips across the > server, each to fire a separate stored procedure or execute an sql string. > Each time, for each user! This has been architected by people who at least > locally (and I also suspect on a statewide level) have reputations for being > expert, professional and experienced (oracle guys). I was stunned. So my > questions are: I don't have experience with lots of different companies, or > with meeting strict deadlines -- do I need to lighten up? I think some of > the reasons for their approach was that they had time constraints (you know, > never enough time to do it right...). > > I don't mean to start people off on rants (for or against). But should I be > sticking to my guns? D. Lewis > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com This transmittal may contain confidential information intended solely for the addressee. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, distribution or copying of this transmittal is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (collect at 907-564-1000) and ask to speak with the message sender. In addition, please immediately delete this message and all attachments. Thank you.