Abbey Books

useless book for datawarehousing

Aimed at all levels of users, administrators and architects, "Oracle Data Warehousing" offers basics, project management, and technical tutorials.

The lightly referenced, verbose, chapters span: what is a data warehouse; things to consider; building the team; managing the data warehouse project; moving the data into the warehouse; Oracle's data warehousing features; data mining; datamarts; metadata; RAID; keeping your data safe; Oracle Express & OLAP Solutions; data mining tools; datamart tools; index and tuning issues.

Strengths revolve around the attractive use of heading, lists, charts, screen-shots, and code examples, and the topical relevance to business of data warehousing.

Weaknesses include: the 45% excess words for content, typos; simplistic business examples; a seeming Oracle advert focus; need for business success anecdotes; a need for more science/ rigor about machine learning and artificial intelligence; and a need for more about wider industry trends/tools.

Overall this needed better editing, more business content, and more rigor to be considered worthwhile.

OK, if you work with Oracle there are some things, that will help you. Otherwise, if you search for more practical or even theoretical books, then look better for Ralph Kimball. This guy is the best in this field.

The Dodge and Gorman book is much, much better than this one. Also - buy a copy of Ralph Kimballs Data Warehouse Toolkit - its applies to DW and DM's. Another good book is Kimball's Data Warehouse Lifecycle book, but the Toolkit book is more concise.

I found it to have a good explanation of general data warehousing terms and concepts, but not enought depht in terms of planning and designing for a data warehouse. I wouldn't recommend buying it.

I have been to Gethsemani many times...know the monks and know that this book is trash. It is poorly edited, poorly put together. Fr.Timothy's section is the only saving part. Don't waste your money...the book does not do justice to this holy place.

Loved the book! Clearly illustrates that humanity and monastic life co-exist. I have been to Gethsemani on many occasions, met several of the Monks there, interracted with them at prayer, meals, and in social settings. These are men of prayer and contemplation, and are also human beings with a gifted outlook on life and a sense of humor. It is very rare for one to see the lighter side of what lies beyond the cloistered walls and monastic enclosures of a life of prayer. Don't hesitate to buy the book, it is a fun and enlightening read and then plan a visit to Gethsemani.

Don't think this could have been published if not for the Gethsemani name. A great folly and waste of paper.

It is ashame that this book was even published. It is full of typo errors. The stories, etc. don't connect. Anyone who knows or have been to the Abbey know that this book does injustice to this sacred place. Fr.Timothy's eulogies are the only redeeming part of the book.

This is a spinoff of the long-running ULTIMA series of computer games. Unfortunately, it doesn't tie close enough with Ultima mythology to please fans, while at the same time not explaining things well enough for newcomers.

The main characters are all pretty unlikable. One unsympathetic protagonist is fine; four or five turns the book into an exercise in masochism.

There's really very little adventuring. Most of the text is devoted to the same argument rehashed multiple times, or to long, repetitive slogs through the muddy countryside, or to calming the panicky horse yet again.

Avoid this; I don't recommend it.

What I would refer to as a househusband, this book refers to as a "full-time househusband." Basically, this book is concerned about sociology and how the dynamics of housework affects wives, husbands, and children. What I would call househusbands are a study of the employment market. It concerns how do men perform the opposite of the stereotypical role of "male breadwinner." There's a Spanish phrase that says, "No one knows what goes on within four walls." It means that people can't really tell what you do in private, they just learn from what you say or do in public. I think many "full-time househusbands" face stigma for not having a job, but if a husband does most of the cooking or cleaning in the family, I doubt if other people would know or care. A man without a job may face shocked faces, but a man who chooses to clean a lot will face much indifference about his cleaning tendencies.

The author excluded all men of color and foreign-born men from his survey. The title of the book suggests that it speaks for all husbands. It really should have been called "White, Native-Born Househusbands." Why mislead readers to think you are speaking for a whole group when you are only discussing a slice of a group? The author quickly says, "Minority men perform househusbanding for different reasons than white men" and then he drops the subject. I really think the author didn't want to address the rampant employment discrimination that men of color face which may push them to focus on the home. Instead of realizing how including men of color and foreign-born men could enrich the discussion, the author dismisses these two important groups. I am very close to saying this is a prejudiced book based upon the exclusion.

The book not only asks how men respond to housework, but it also asks how housework affects or changes men. This two-sided analysis is important, or at least thorough.

I wonder if this book may be dated. To begin, the numbers of men of color and immigrant men are rising, so the author's focus group now makes up less of the population. Still, fewer couples are marrying, states are going after deadbeat dads more effectively, and the number of openly gay couples is rising. This book may have an old 1970s or early 1980s vibe that just doesn't matter in this new millennium.

the poems were great but the pictures are rather distracting
and have nothing to do with love what-so-ever

When I purchased this book (incidentally, it's a paperback), I believed that it would be a history of Stewart and Hyder. Actually, it is more of a church history of Stewart and Hyder. It was interesting to browse through since I had visited this area, but I was more interested in the town history rather than religious activity in the area.

It's a paperback book, the cover is a color aerial view of Hyder and Stewart, there are some black and white photos in the book.

Persuasion is a fantastic book which everyone should buy separately from Northanger Abbey and Emma. It is about a girl named Anne, the middle, neglected child in her very dysfunctional family, who is persuaded by next door neighbor and close friend not to marry Captain Wentworth, the man of her dreams. About ten years later, Wentworth comes back from was and they reevaluate their relationship. This is a book about second chances, love, and finding one's true identity. I really enjoyed this book, but Emma and Northanger Abbey were so boring they put me to sleep. They do not contain the same truthfulness that Persuasion does and the plots aren't very interesting.

This book is basically unreadable. Impenetrable metaphysical terminology is used in dense, convoluted sentences to convey abstruse theories of meaning (at least I think that's what it is) in such a way as to be completely and utterly opaque. Half the time I didn't know what the guy was talking about, and I have a degree in this stuff and belong to Mensa. If you're interested in Turner, you'd do better to look elsewhere.

Some good reproductions though, and if you're just interested in the pictures, the price is right. Hence the two stars; the text would be zero, since it's useless.

get it from interlibrary loan instead. I love Abbey's non-fiction writing but this book would have benefited greatly from a harsh editor that had the guts to say, simply, NO! No, we will not publish this inane collection of lame quips and quotes Mr Abbey, because it does not deserve to sit on the same shelf or even in the same room as your other work.

Do you know all those great ideas and one-liners that come to you late at night that seem so witty and smart and true, but just dont hold up under the harsh light of the next day? This book is full of those. Argghh, ED, my freakin eyes hurt! :)

I am an absolute beginner in Oracle, and I was looking for a book that will show me step-by-step how to create and administer an Oracle database. This book will give you a little idea how to administer an Oracle database alright, but it is assuming you already have a database to administer!... Gladly, I just borrowed this book. Now I understand why the guy who lent it wasn't very happy with his purchase.

I am totaly novice in Oracle DBA programing. When I bought this book I thought it would be a good place to start. Well, I was completely dissapointed. This book is neither for beginers nor for some who knows basic DBA programming. Today I returned it to the bookstore.

All I can say is this book is great to get a person up to speed with Oracle products. The portion of the book explaining all the parts that make up the Oracle package and the installation are worth the price alone.

This book is great for total beginners who have little to no experience with networks and databases. If you are looking for a general reference book, the book will be sufficient for basic stuff. For more complicated things like writing subqueries, inner joins, outer joins, stored procedures, creating data models and database administration, you should get a dedicated book. For professionals who want a good general reference book, a general purpose database administration book is a better bet. If you're used to GUI database administration, then get a good PLSQL book instead. There's no substitute for detailed knowledge and expertise with SQL and command line.

I'm an Biz/IT consultant trying to pick up Oracle 8i from scratch. I think the so-called "beginner" aspect stems from the fact that it tries to explain very basic IT terminologies such as Intranet, Internet, client, server, TCP/IP etc at the beginning of each chapter. I find most of the explanations quite appauling though.

I think the author should devote more time illustrating data modeling terminologies such as tablespace, schema, dropping of database, mounting etc... I find no explanations to these.

The author also spend much time blowing whistle for Oracle and write about Oracle being the database of the future, and what powerful features it has. Lots of big words used, but no examples nor illustration of how they can be done. It's frustrating to waste time reading these.

In conclusion, I find that this is a very huge book with little substance and poor organization. I've read it for days but don't seem to gain much from it. I'm looking for another book to buy, that explains why I'm in here.