- Paperback: 1680 pages
- Publisher: Wiley; 1 edition (August 31, 2009)
- Language: English
- ISBN-10: 0470257040
- ISBN-13: 978-0470257043
- Product Dimensions: 7.4 x 2 x 9.3 inches
- Shipping Weight: 5.4 pounds (View shipping rates and policies)
- Average Customer Review: 3.9 out of 5 stars See all reviews (22 customer reviews)
- Amazon Best Sellers Rank: #467,985 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.
Microsoft SQL Server 2008 Bible 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently Bought Together
Customers Who Bought This Item Also Bought
From the Back Cover
"Paul Nielsen brings his passion for SQL Server and his long years of experience with this product into every page of the SQL Server 2008 Bible."
—Kalen Delaney, SQL Server MVP
Get ready for SQL Server 2008
Whether you're a database developer, DBA, or BI Developer, SQL Server 2008 promises to change the way you deliver enterprise data solutions. Open this detailed, experience-based guide for clear explanations of the concepts balanced with real-world examples and best practices gleaned from years of field and consulting experience. SQL Server is an immense product — this book is your guide to the strategies and details that matter most.
Master the data architecture concepts that drive database technologies
Write elegant set-based queries that respond well to a comprehensive indexing strategy
Code an efficient and robust data abstraction layer with stored procedures
Learn the best way to connect to SQL Server with ADO or Microsoft Access
Use PowerShell and Policy-based Management to better administer your servers
Use Analysis Services, MDX, and Excel to analyze data trends
Optimize performance with data compression, resource governor, and partitioning
Companion Web Site
Please visit www.sqlserverbible.com to download all the sample databases and code, watch screencasts that walk through key features, sign up for the SQL Server Bible eNewsletter, find additional SQL Server utilities and samples, and find out about the authors' seminars and speaking schedules.
- Manage enterprise data servers with ease
- Develop scalable and flexible databases
- Analyze data with SQL Server's BI Suite
- The book you need to succeed!
Top Customer Reviews
This one is heavier than the other two - 1642 pages compared to 1293 and 890.
And the paper stock is better as well.
The tone is almost conversational in that Paul Nielsen comes up with likely scenarios to show the syntax of a command.
You can tell that a lot of his tips come from hindsight. Here's an example of a Best Practice tip found on page 263: "Use a join to pull data from two data sources that can be filtered or manipulated as a whole after the join. If the data must be manipulated prior to the join, then use a derived table subquery."
That piece of advice comes from someone who has had to tackle problems using both techniques.
And he's not afraid to tell you worst practices either. Page 547: "Any table design that requires sparse columns is a horrible design."
This is especially helpful if you're learning a new feature and want to know if it's worth the effort.
Don't think that this is an A-Z reference manual.
Chapter 53 is Mr. Nielsen's "AutoAudit", which is quite a nifty code generator to add auditing to your tables.
Small factual correction:
Chapter 18: Manipulating XML Data => XSD and XML Data Collections (page: 483):
"This schema defines a top-level element ˝Customer˝ with two attributes: CustomerID and
CustomerNumber. CustomerID attribute is set to mandatory by using the use attribute.
A restriction of minimum value and maximum value is applied on the customerID attribute. The
CustomerNumber attribute is set to optional by setting the use attribute to optional."
End quote from the book.
Actually attribute is called CustomerName, see definition in the schema:
<xs:attribute name="CustomerName" use="optional">
However, this is a very minor point, the first one for more than a hundred pages perused.