I've used views in some places and always came to regret it from a performance standpoint. views are usually useful when you do complex join/queries. this is also when there is the potential for a performance bottleneck. using views should be done quite sparingly. writing staight sql just gives me more control and performance.
Sincerely, Leon Oosterwijk Dave Ramsey Inc. [EMAIL PROTECTED] > -----Original Message----- > From: Raster, Tim [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 17, 2003 1:26 PM > To: SQL > Subject: To View or not to View? > > > In SQL 7 and 2000, what is the feeling of using Views to represent data > joined by between 2-5 tables, and using that view in the place of > complicated inner join clauses in a query? On the one hand, code is > much cleaner because you join against a single View instead of many > joined tables. On the other hand, I've read that query engines may join > all the data in those tables together before it does anything, which > makes it slow due to joining data it doesn't need. My tables are large > in some cases. > > Thoughts? Thanks! > > > Tim Raster > Vice President - Information Systems > PracticeMatch, Inc > 55 Westport Plaza Drive, Suite 755 > Saint Louis, MO 63303 > 800-489-1440 x4114 > 314-878-1440 x4114 > [EMAIL PROTECTED] > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=6 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=6 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
