Benjamin Nevarez

Benjamin Nevarez is a database professional based in Los Angeles, California. He has more than 15 years of experience with relational databases and has been working with SQL Server since version 6.5. Benjamin has been the technical editor of the two latest Kalen Delaney’s books including “SQL Server 2008 Internals”. He holds a Master’s Degree in Computer Science and has been a speaker at several technology conferences, including the PASS Community Summit. you can read Benjamin’s blog at www.benjaminnevarez.com.

SQLServerCentral Article

Inside the SQL Server Query Optimizer

This book will take you from the fundamentals of Statistics, Cost Estimation, Index Selection, and the Execution Engine, and guide you through the inner workings of the Query Optimization process, and throws in a pragmatic look at Parameterization and Hints along the way.

4.67 (3)

You rated this post out of 5. Change rating

2017-02-06

27,103 reads

Blogs

A New Word: Fensiveness

By

fensiveness – n. a knee-jerk territorial reaction  when a friend displays a casual interest...

Microsoft Purview FAQ

By

I get many of the same questions about Microsoft Purview, so I wanted to...

Undercover Catalogue 0.4.5 Released – Database Module Bug Fix

By

Full documentation on the Undercover Catalogue can be found HERE We’ve spotted a bug in...

Read the latest Blogs

Forums

GIT Configuration and Automated Release for Azure Data Factory

By Sucharita Das

Comments posted to this topic are about the item GIT Configuration and Automated Release...

How to Add a New Shared Disk to a WSFC as a SQL Resource

By muhkam

Comments posted to this topic are about the item How to Add a New...

Gateway timeout when posting reply but...

By dmbaker

I posted a reply to a topic today and, after a minute or so,...

Visit the forum

Question of the Day

Disabling Indexes

I want to disable an index so that it doesn't use any resources and isn't maintained. I am planning to drop this, but don't want to do it now. The index is named LoggerNCI and was created on the dbo.Logger table, on the LogID column. What code disables this?

See possible answers