On Sat, 06 Jul 2002 15:27:47 -0500 "Richard Lynch" <[EMAIL PROTECTED]> wrote:
> Do you have *ANY* idea how quickly: > > "select * from MyTable" can be parsed and an execution plan selected?! > > It's CHUMP CHANGE in time. > > *ONLY* if your SQL is so incredibly complicated that you can't even > understand it will the parse/compile time of SQL be a factor in > performance. It is "CHUMP CHANGE" when you make a tinie web site with 2 users. Do the math. If you have a SQL statement that takes 250 milliseconds to parse and create an execution plan, then 250 * 1,000,000 page request per week (which is what the site I finished averages, the company I work for has 110,000 employees) = ??? This is second grade math. No matter how you look at it, 10 extra milliseconds here or there adds up when you work on a big site. The db's I work with are not simple "select foo from bar" queries. An enterprise db is usually pretty complex. My main reason for posting a reply was not to start a stupid flame war with you. It was from stopping you from filling the heads of new programmers on this list with bunk. Stored procedures are not junk! I wonder why they are the most requested feature for MySQL? Why would all the Big DB's (Oracle, DB2, PostgreSQL, SQL Server, etc.) support them if they had no benifit? The biggest benifit is SPEED, the second is the ability to encapsulate the underlying database structure. A DBA can change the db structure at will as long as the sproc returns the same columns. -- James Drabb JR - Programmer Analyst - Orlando, FL - [EMAIL PROTECTED] --------------------------------------------------------------------- -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
