The SQL Server 6.5 Performance Optimization and Tuning Handbook
Conditions
A read copy that remains in clean condition.
Formats
Conditions
A read copy that remains in clean condition.
Conditions
A read copy that remains in clean condition.
Formats
Conditions
A read copy that remains in clean condition.
This book completely demystifies a number of SQL tuning concepts. This book provides a superb overview of the various performance topics, and then drills down deep enough into the concepts to give you the insights necessary to tackle thorny performance problems with multiple causes. This is still a very valuable book for SQL 7.0--the majority of the concepts are still with us.
This book is one of many I have read on SQL Server 6.5. It is clear & very well written. It highlights key points and goes into the right amount of detail. It is a must-read for anyone designing, deploying, or administering a SQL SERVER 6.5 database.
After you have spent 8-80 hours trying random combo's on the Server Configuration panel trying to guess what you should do, buy this book and score a direct hit! Microsoft should bundle this book with SQL Server. If a little more detail were provided on the internal data structures of SQL Server one could write a bulk loader that bypassed SQL Server entirely (I know its been done by others) and load 10 X as fast. (hint-hint) This is the closest thing to a K & R for MS SQL Server I've ever seen. I really like the brevity of this book. Every word counts! Very, very good job Ken!
The techniques described in this book are effective and well thought out. Even if performance optimization is not your main goal, this book is well worth reading. The book delivers in-depth information on indexing, locking, the optimizer and many other topics in a very readable format. Ideal for those with some knowledge of SQL Server who want to dig deeper.
Had response problems with current database setup and SQL statements. The chapters on Indexing and Optimizing really work. Ex. A simple query on two tables took 2.5 minutes. After applying some of the suggestions, the query took a little over 2 seconds...