A Guide to SQL

Book came in perfect condition. Its a great entry level book to SQL. I went from 0 knowledge to a firm understanding. its a relatively easy read considering the topic

Thank you

I used this book for an intermediate SQL class. The topics covered in the first 7-8 chapters are things I had already learned from an intro to SQL class that used a Casteel book. While I didn’t learn too much from the first 3/4 of the book, it’s (mostly) all presented well and clearly. The material that was new to me were procedures and triggers. When it came time to do problem sets on procedures and triggers, I felt like I was shooting in the dark and this is why I took off a star. It would have been nice to clarify the explanations and/or give more detailed examples. Successfully executing my homework scripts took a LOT of trial and error.

This book is excellent for learning basic SQL. The chapters are easily read and understood and the lessons are helpful and well laid out.

After taking an intro to SQL class, I questioned a professor on his view of this book. He said that there are two types of Intro to SQL books, ones that are too easy, and ones that are too difficult. This one is too easy. The class structure probably should have been to read the first half in the first week, the second half in the second week, then move on to a different book. Oh well. It's well written, has idiot-proof examples and has one or two questions in each chapter that make you think. It's a very simple book aimed at the basics of SQL.

It was requested for the class. It is a great book

I understand that this book was created to be studied after you've read it's sister book Concepts of Database Management still at times it goes through content such as database normalization way to briefly, and then gives infuriatingly difficult exercise questions that can't be answered simply by "going over the chapter again".Part of an exercise question example: "[make or change a table] When a customer places an order, the sales rep who gets the commission on the order must be in the collection of sales reps who represent the customer". WHAT IS BEING ASKED HERE!?!?Much of the book uses three databases that are unrelatable, unless you were at some point in the manufacturing business or a tour guide.The order that content is gone over, and referenced back and forth is also frustrating, for example, Normalization, and Database Design Diagrams, are gone over before sql code for creating a database, in a book ABOUT SQL CODE!! For some reason these topics are gone over before SQL. Not including the preface the actual term "SQL" is literally not mention once before chapter 3, that's insane!!Advice to Reader: If buying the book is completely unavoidable, I suggest finding the eBook, it will make indexing a lot easier.Advice to author:Make databases that the reader can relate to. Since this is an intro level text book it may be the readers firs time looking at databases. Columns named STORHOUSE, and ON_HAND, add terminology that is not often used, to an already unfamiliar topic, and make it frankly boring. Instead creating a database from the menu of a fast food restaurant, that includes columns named, PRICE, CALORIES, PATTY_TYPE, make it instantly more realtable, and more engaging.

Received it fast, no problems at all.Looks good as new even tho its 'used'.