All, Thanks for the comments. It does appear that I am attempting to solve an easy the most difficult way possible. I'm going to go away now and spend some time with my handy dandy SQL book....
Thanks again! Jerry Jalenak Development Manager, Web Publishing LabOne, Inc. 10101 Renner Blvd. Lenexa, KS 66219 (913) 577-1496 [EMAIL PROTECTED] > -----Original Message----- > From: Vic Cekvenich [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 06, 2003 9:32 AM > To: [EMAIL PROTECTED] > Subject: Re: [OT - Design] Needing Fast Access to 300,000 Records > > > > [EMAIL PROTECTED] wrote: > > > retrieving all the records because just in case the client > may need them does not look very efficient approach to me. > > One never designs for all the exceptions of what might be, > that would be > a bad design. > One designs for the likely case only, at least good designers do. > The old 80/20 rule. > > (Unlikely excetiopns you deal with by doing exception procesing) > But you design for the rule, else you are fighting your design. > > > .V > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > This transmission (and any information attached to it) may be confidential and is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient or the person responsible for delivering the transmission to the intended recipient, be advised that you have received this transmission in error and that any use, dissemination, forwarding, printing, or copying of this information is strictly prohibited. If you have received this transmission in error, please immediately notify LabOne at the following email address: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
