Re: Fw: [SQL] and [index] mystery solved
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 38127
interpreted = N
texte = Thanks John!----- Original Message ----- From: John Peacock
To: WebCatalog Talk Sent: Thursday, August 23, 2001 11:42 AM Subject: Re: Fw: [SQL] and [index] mystery solved > Bob McPeak wrote: > > > > For a variety of reasons (CORRUPTION!!) we're migrating many of our dbs to > > SQL. Our trusty sys admin, Nick, has figured out a way to do a summary > > report in the sql context founditems. > > > > Any general feedback on migrating to sql would be greatly appreciated. > > > > Get yourself a book on SQL (for whatever flavor you are using). It is > trivial to do summaries in SQL: > > select min(field) as min_field, other_field > FROM table > WHERE criteria > GROUP BY other_field > > etc. It is also bad form to use select * ever, since that requires > the database to do an additional lookup to the schema tables to figure > out what fields are contained in that table. Always request only the > fields you are going to immediately use, to limit the amount of network > traffic dedicated to wasted data. > > When you move to a pure relational database, make sure that you > do all of your joins in SQL, rather than building them up in WebCat. > You can even create VIEW's in the backend database that encapsulate > your most common joins. Depending on the server, a VIEW will be > somewhat or a lot faster (since the query is already compiled and > optimized). > > Learn how to use indexes effiently for your database. Oracle, for > example, will not use an index unless you have all of the index > fields in the WHERE clause (you can also use query hints). There > are a lot of things that WebCatalog does for you that you will need > to do yourself with you use an SQL database backend. > > HTH > > John > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4720 Boston Way > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5747 > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://search.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Thanks John!----- Original Message ----- From: John Peacock To: WebCatalog Talk Sent: Thursday, August 23, 2001 11:42 AM Subject: Re: Fw: [SQL] and [index] mystery solved > Bob McPeak wrote: > > > > For a variety of reasons (CORRUPTION!!) we're migrating many of our dbs to > > SQL. Our trusty sys admin, Nick, has figured out a way to do a summary > > report in the sql context founditems. > > > > Any general feedback on migrating to sql would be greatly appreciated. > > > > Get yourself a book on SQL (for whatever flavor you are using). It is > trivial to do summaries in SQL: > > select min(field) as min_field, other_field > FROM table > WHERE criteria > GROUP BY other_field > > etc. It is also bad form to use select * ever, since that requires > the database to do an additional lookup to the schema tables to figure > out what fields are contained in that table. Always request only the > fields you are going to immediately use, to limit the amount of network > traffic dedicated to wasted data. > > When you move to a pure relational database, make sure that you > do all of your joins in SQL, rather than building them up in WebCat. > You can even create VIEW's in the backend database that encapsulate > your most common joins. Depending on the server, a VIEW will be > somewhat or a lot faster (since the query is already compiled and > optimized). > > Learn how to use indexes effiently for your database. Oracle, for > example, will not use an index unless you have all of the index > fields in the WHERE clause (you can also use query hints). There > are a lot of things that WebCatalog does for you that you will need > to do yourself with you use an SQL database backend. > > HTH > > John > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4720 Boston Way > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5747 > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://search.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Bob McPeak
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] Amazon EC2 (2009)
serial number (1998)
Undeliverable Mail (1997)
Variable Prices (1998)
RE: Loss in form (1998)
Exclamation point (1997)
Nesting FoundItem Context (1997)
UPDATE PROBLEM (1997)
Search multiple fields (1997)
Browser Reloads and AddlineItem (1997)
select multiple (1997)
Custom Shipping Charges (1997)
Car Database (2002)
multiple databases (1997)
Showif dates... (2002)
email server and webdna (2006)
WebMerchant? (1998)
New public beta available (1997)
PSC recommends what date format yr 2000??? (1997)
WebCatalog2 Feature Feedback (1996)