- Paperback: 592 pages
- Publisher: Addison-Wesley Professional; 1st edition (March 4, 2000)
- Language: English
- ISBN-10: 0201615762
- ISBN-13: 978-0201615760
- Product Dimensions: 7.4 x 1.2 x 9.1 inches
- Shipping Weight: 2.1 pounds (View shipping rates and policies)
- Average Customer Review: 230 customer reviews
- Amazon Best Sellers Rank: #455,579 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
The Guru's Guide to Transact-SQL 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
Frequently bought together
Customers who bought this item also bought
From the Inside Flap
This is a coder's book. It's intended to help developers build applications that make use of Transact-SQL. It's not about database administration or design. It's not about end-user or GUI application development. It's not even about server or database performance tuning. It's about developing the best Transact-SQL code possible, regardless of the application.
When I began writing this book, I had these design goals in mind:
Be very generous with code samples--don't just tell readers how to do something, show them. Include complete code samples within the chapter texts so that the book can be read through without requiring a computer or CD-ROM. Use modern coding techniques, with specific emphases on ANSI compliance and current version features and enhancements. Construct chapters so that they're self-contained--so that they rely as little as possible on objects created in other chapters. Provide real-world code samples that have intrinsic value apart from the book. Avoid rehashing what's already covered extensively in the SQL Server Books Online. Highlight aspects of Transact-SQL that differentiate it from other SQL dialects; don't just write another ANSI SQL book. Avoid excessive screenshots and other types of filler mechanisms often seen in computer books. Proceed from the simple to the complex within each chapter and throughout the book. Provide an easygoing, relaxed commentary with a de-emphasis on formality. Be the reader's indulgent, amiable tutor. Attempt to communicate in writing the way that people speak.
You'll have to judge for yourself whether these goals have been met, but my hope is that, regardless of the degree of success, the effort will at least be evident. About the Sample Databases
This book uses SQL Server's Northwind and pubs sample databases extensively. You'll nearly always be able to determine which database a particular example uses from the surrounding commentary or from the code itself. The pubs database is used more often than Northwind, so, when it's not otherwise specified or when in doubt, use pubs.
Usually, modifications to these databases are made within transactions so that they can be reversed; however, for safety's sake, you should probably drop and recreate them after each chapter in which they're modified. The scripts to rebuild them (instnwnd.sql and instpubs.sql) can be found in the \Install subdirectory under the root SQL Server folder. Results Abridged
If I have a pet peeve about computer books, it's the shameless use of space-filling devices to lengthen them--the dirty little secret of the computer publishing industry. Many technical books these days overflow with gratuitous helpings of screenshots, charts, diagrams, outlines, sidebars, icons, line art, etc. There are people who assign more value to a book that's heavy, and many authors and publishers have been all too happy to accommodate them. They seem to take the old saying that "a picture is worth a thousand words" literally--in some cases turning out books that are little more than picture books.
I think there's a point at which comprehensiveness gives way to corpulence, a time when exhaustiveness becomes exhausting. In this book, I've tried to strike a balance between being thorough and being space-efficient. To that end, I've often truncated or clipped query result sets, especially those too wide to fit on a page and those of excessive length (I always point this out). On occasion I also list them using reduced font sizes. I don't include screenshots unless doing so benefits the discussion at hand materially (only one chapter contains any screenshots). This is in keeping with my design goal of being complete without being overwrought. Nearly 600 SQL scripts are used in this book, and they are all included in the chapters that reference them. Hopefully none of the abridgements will detract from the book's overall usefulness or value. On Formality
Another of my pet peeves is formality for the sake of formality. An artist once observed that "it's harder to draw a good curved line than a straight one." What he meant was that it's in some ways more difficult to do something well for which there is no exact or stringent standard than to do something that's governed by explicit rules and stuffy precedents. All you have to do to draw a straight line is pick up a straightedge. The rules that govern formal writing, particularly that of the academic variety, make writing certain kinds of books easier because they convert much of the subjective nature of writing into something more objective. They're like training wheels on the would-be author's bicycle. Writing goes from being a creative process to a mechanical one. Cross all the T's, dot all the I's, and you're halfway there. Obviously, this relieves the author of many of the decisions that shape creative writing. It also turns otherwise good pieces of work into dreary, textbook-like dissertations that are about as interesting as the telephone book White Pages.
So, I reject the notion that formal writing is better writing, that it is a higher standard and is the ideal for which all technical writers should strive. Instead, I come from the Mark Twain school of thought--I "eschew surplusage"--and I believe that, so long as common methods of speech do not become overly banal (a subjective distinction, I freely admit), the ultimate goal of the technical writer should be to write the way that readers speak. It is the way people--even technical people--are most accustomed to communicating and the way they are the most able to learn and share ideas. I did not invent this way of thinking; it's simply the way most of my favorite authors--Mark Twain, Dean Koontz, Joe Celko, Ernest Hemingway, Robert Heinlein, Andrew Miller, Oscar Wilde, P. J. O'Rourke, Patricia O'Connor--write. Though it is far more difficult to structure and write a narrative that flows naturally and reads easily, it's worth the effort if the ideas the writer seeks to convey are understood as they were intended.
So, throughout this book, you'll see a number of the rules and pseudo rules of formal writing stretched, skirted, bent, and sometimes outright broken. This is intentional. Sometimes I split infinitives, begin sentences with conjunctions, and end them with prepositions. Sometimes record is used interchangeably with row; sometimes field takes the place of column; and I never, ever treat data as a plural word. I saw some software recently that displayed a message to the effect "the data are being loaded," and I literally laughed out loud. The distinction between the plural data and its obscure singular form datum is not maintained in spoken language and hasn't really ever been (except, perhaps, in ancient Rome). It has also been deprecated by numerous writing guides and many authors. You will have to look very hard for an author who treats data as a plural word (I can think of only one off the top of my head, the irascible Ted Codd). The tendency for technical communication to become self-important or ostentatious has always baffled me: why stoop to pretension? Why trade the fluid conveyance of ideas between people for nonsense that confuses some and reads like petty one-upmanship to others? Acknowledgments
I'd like to thank my wife, who not only makes it possible for me to write books but also makes it worthwhile. The book you see before you is as much hers as it is mine. I'd like to thank Neil Coy, who made a real programmer of me many years ago. Under Neil's tutelage, I learned software craftsmanship from a master. Joe Celko, the dean of the SQL language, has been a good friend and a valuable source of information throughout this project. Kudos to John Sarapata and Thomas Holaday for helping me come up with a title for the book (I'll keep Sybase for Dummies in mind for future use, John). Thanks to the book's technical reviewers, particularly Wayne Snyder, Gianluca Hotz, Paul Olivieri, and Ron Talmage. Heartfelt thanks to John Gmuender, Joe Gallagher, Mike Massing, and Danny Thorpe for their equanimity and for keeping me sane through the recent storm. Congratulations and genuine appreciation to the superb team at Addison-Wesley--Michael Slaughter, Marisa Meltzer, J. Carter Shanklin, and others too numerous to list. Special thanks to Nancy Cara-Sager, a friend, technical reviewer, and copyeditor who's been with me through several books and a couple of publishers now. Her tireless attention to detail has saved me from embarrassing myself more times than I can count.
From the Back Cover
Since its introduction over a decade ago, the Microsoft SQL Server query language, Transact-SQL, has become increasingly popular and more powerful. The current version sports such advanced features as OLE Automation support, cross-platform querying facilities, and full-text search management.
This book is the consummate guide to Microsoft Transact-SQL. From data type nuances to complex statistical computations to the bevy of undocumented features in the language, The Guru's Guide to Transact-SQL imparts the knowledge you need to become a virtuoso of the language as quickly as possible.
In this book, you will find the information, explanations, and advice you need to master Transact-SQL and develop the best possible Transact-SQL code. Some 600 code examples not only illustrate important concepts and best practices, but also provide working Transact-SQL code that can be incorporated into your own real-world DBMS applications.
Your journey begins with an introduction explaining language fundamentals such as database and table creation, inserting and updating data, queries, joins, data presentation, and managing transactions. Moving on to more advanced topics, the journey continues with in-depth coverage of:
- Transact-SQL performance tuning using tools such as Query Analyzer and Performance Monitor
- Nuances of the various T-SQL data types
- Complex statistical calculations such as medians, modes, and sliding aggregates
- Run, sequence, and series identification and interrogation
- Advanced Data Definition Language (DDL) and Data Management Language (DML) techniques
- Stored procedure and trigger best practices and coding methods
- Transaction management
- Optimal cursor use and caveats to look out for
- Full-text search
- Hierarchies and arrays
- Administrative Transact-SQL
- OLE Automation
- More than 100 undocumented commands and language features, including numerous unpublished DBCC command verbs, trace flags, stored procedures, and functions
Comprehensive, written in understandable terms, and full of practical information and examples, The Guru's Guide to Transact-SQL is an indispensable reference for anyone working with this database development language. The accompanying CD-ROM includes the complete set of code examples found in the book as well as a SQL programming environment that will speed the development of your own top-notch Transact-SQL code.
Try the Kindle edition and experience these great reading features:
230 customer reviews
Review this product
Read reviews that mention
Showing 1-4 of 230 reviews
There was a problem filtering reviews right now. Please try again later.
The book is stuffed with little tidbits and fills in LOTS of blanks. Within the first few pages I learned that a blank time in a timedate field evaluates to midnight, and that can cause problems:
"The following example uses the BETWEEN operator to return orders occuring between October 1990 and May 1995, Inclusively. I've included the time with the second of the two dates because without it, the time would default to midnight (SQL Server datetime columns always store both the date and time; an omitted time defaults to midnight), making the query noninclusive. Without specification of the time portion, the query would return only orders placed up through the first millisecond of May 31.
SELECT ordernumber, orderdate, amount FROM orders Where orderdate BETWEEN '10/01/90' AND '05/31/95 23:59:59.999'"
Note the clarity of the writing and the clear capitalization scheme used. Moreover, this is important stuff. I never would've guessed that SQL Server is that dumb, and it's really necessary to know . For all I know, they may have fixed this on 7.0, but I still have clients on 6.5).
Obviously from this example you can see that you don't have to be an aspiring guru yourself to get a lot out of it. Don't let the title scare you off: it's fine for beginners and will get you way beyond beginner's level quickly.
It will take you as far as you want to go, if you put in the time and effort.
I consider it a must on any SQL bookshelf (now, if only they'd update to include OLAP, DTS etc.).
The Guru's Guide is basically structured around SQL syntax. It starts with introductory chapters on Transact-SQL, both DDL and DML. Chapters 6 onwards cover SQL in more detail. Many examples accompany the text. And the further you get into the book, the beefier it gets. Advance topics like cursors and transactions are covered well.
Stored Procedures and Triggers are only glanced over in this book - these topics are left for the more advanced Guru's Guide to Stored Procedures. But some administrative issues are covered, and covered well. System procedures are discussed, and you can find code for the useful ones that are NOT supplied by the vendors. Talking about which, another topic of interest is the undocumented features T-SQL. The things that are there, but the vendors did not want you to know about it.
Database design and performance tuning are topics sorely needed by many application programmers, in my experience, and I recommend these chapters to anyone who needs grounding in these areas. Other programming issues like full-text searching is covered, and there is a neat replacement procedure for Soundex to be found. Many bits and pieces make a good reading of the book worthwhile.
All the code are included on a CD-ROM. If you are a Sybase user, do not expect the bonus SQL editor (on the CD-ROM) to work for you. You'll get a message saying "this demo version can only connect to MS SQL Server". Should you visit the website to look for the non-demo version, you'll find a version tied even closer to Microsoft. It won't even install without MS SQL Server present. I thought that this was unfortunate.
This book covers so much that I find it hard to summarise it in a few paragraphs. It is obviously recommended for MS SQL server professionals - there are enough glowing reviews on this page. Do I recommend it for Sybase users? Well yes, maybe. If you accept that MS SQL Server and Sybase Adaptive Server have grown apart over the years and that there are many incompatibilities between the two. So while you can use the Guru's guide for ideas, hints and tips and techniques, it will not serve as an exact reference manual. But I think you'll find much of value. This is one of the better database and SQL books I have seen.
I have also purchased the follow up Guru SQL book, which is more advanced than the present book. What would also be nice is a book on SQL algorithms or patterns. Maybe Ken Henderson can do a follow-up that provides sample solutions to common SQL problems. And how about a book that covers the differences between to MS SQL Server and Sybase Adaptive Server?
Equally as amazing is the usefulness of the sample code. I don't know about you, but sample code from most of the books I've found tends to be more academic than practical. In other words, though it helps explain some important point, it's not code you could or would use in the real wrold. That's not true with this book. Everything - from the fulltext search examples, to the Automation and Administrative code - is good stuff. I used lots of it in my job as-is. So, you get a double value here. You get a great book, and along with it, a great T-SQL code library. They ought to sell the CD separately.
Last but not least - I love the T-SQL editor that's included with the book. It's a freebie tool (they're not hawking a product here) that's much more powerful and easy to use than Query Analyzer. So, you get a triple value.
All told, this is one heckuva book (and software package). Knowing what I know now, if I was told I had to get rid of all my SQL Server books except one, this is the one I'd keep.