Summary

Today you got some background information on SQL. You read the section called “Who Uses SQL?” and either put the book back on the shelf or decided to forge ahead. You got connected and sent a query. If you’re reading this book without the benefit of being able to run the examples, you can still read through the book; you just may have a harder time grasping the information. Programming books are tough to understand unless you have a computer that enables you to play with all the examples.

Tomorrow, I’ll talk a lot more about the features of ISQL/w, how to use it effectively, and how to view different stuff coming back from the server. This is enough for today, though. (Background information always tires me out.) If you have some juice left over, go on to Day 2. It’s pretty long, but it’s also very introductory, so it’s a fast read.

Q&A

Q I don’t have a Microsoft server available, and I don’t feel like tying up a phone line at home to work through all the examples on your Web server. Can’t I just use Access or something?

A Although Access uses SQL to interact with its data, it uses a dialect that is different from Transact-SQL. This book is about T-SQL, and although you might be able to run some of the examples on Access (or another program), you will eventually run into stuff that doesn’t work in that world. The other issue is that the pubs database does not exist in Access, so you’ll have no sample data on which to practice.

Q I’m new to programming, but I need to learn SQL. Is this book for me?

A Absolutely. I’ve included a lot of notes and sidebars for people who have never programmed before. Programmers can skip over these, but folks like you will get all the help you need.

Q Why is SQL pronounced “sequel?”

A SQL is a descendant of IBM’s “SEQUEL” language. The pronunciation came from this early name.