 | |
Re: Book about query processing / query optimization searched
comp.databases.theory comp.databases.theory
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: Book about query processing / query optimization searched -
10-04-2007
, 11:44 AM
|
I'm looking for a book that describes query-processing and query-optimization according to the current state of the art. Has anyone read the following title? "Principles of Database Query Processing for Advanced Applications" ISBN-10: 1558604340 http://www.amazon.com/dp/1558604340/ |
Except from the first few lines...
*In a relational database, data is organized into table format*
#2
| |||
| |||
|
|
Cimode schrieb: A total waste of time and money...(it does cost 67$ !!!) Why? Cause you will get a better value by people who do not continuously |
http://www.amazon.com/dp/0201485559?...BE2TV51AMAPF4&
Quote:
|
Except from the first few lines... *In a relational database, data is organized into table format* Do you think you can estimate the quality of a book by evaluating the first lines? I dunno but thanks to some people like F.PASCAL and a few others, I |
miles.
#3
| |||
| |||
|
|
Elcaro Nosille wrote: Cimode schrieb: A total waste of time and money...(it does cost 67$ !!!) Why? Except from the first few lines... *In a relational database, data is organized into table format* Do you think you can estimate the quality of a book by evaluating the first lines? If the first lines make sense, you might want or need to read more but if the first line is silly, odds are you don't. As Groucho Marx said when asked to write a jacket blurb for a supposedly humourous book: (something like) "from the moment I picked it up until I put it down I couldn't stop laughing. Some day I'm going to read it". Or when he simply asks a lady in a room with a cigar in his hand *Do |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Database Tuning by Dennis Shasha $ Philippe Bonnet (ISBN 1-55860-753-6) is a pretty good overview. But I would head for academic publications like TODS from ACM and look at articles. Cheap, fast storage and parallelism in the hardware is changing everything. --CELKO-- |
Just kidding. Butnot about the point. I don't follow hardware all that closely; then I
ran across a reference to an interview with Linus Torvalds, which I
read. In it, he referred to file systems and the looming presence of
solid state disks.
Which got me to thinking: if there's no rotational delay in the file
system, then what happens to the standard objection to the Relational
Database; joins are toooooo sloooow. And then, why not, finally, follow
the mantra: one fact, one place, one time?
Mayhaps this will shut up the knuckleheads.
#6
| |||
| |||
|
|
if there's no rotational delay in the file system, then what happens to the standard objection to the Relational Database; joins are toooooo sloooow. And then, why not, finally, follow the mantra: one fact, one place, one time? |
Look at WX 2 (nee White Cross), Teradata, SAND and Vertica for column
oriented RDBMS products.
In my next book, I carry things one step further. JOINs will become
cheaper than computations in the near future -- they are mostly
equality tests or simple comparisons. So more stuff will be done by
table look up in parallel hardware.
#7
| |||
| |||
|
|
--CELKO-- wrote: I suppose column-based representations are superior when joins never |
attract implementers, as usual. >>
A key fundamental issue...
Question is: how could a column-based physical relation or relation
operation representation be superior in *any* case to some other
representation. Another way to ask the question: could join
consumption of IO resources under a column based system be increasing
any otherwise than exponentially as the number of join operation
increases?
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.