Technical Article

Changes to SQL Server 2012 Execution Plans

I’ve been working with execution plans quite a lot in SQL Server 2012. There are a number of changes, most of them associated with new or different functionality. I had not noticed anything really fundamental until recently. I’ve become a huge proponent of always checking the properties of the SELECT statement. There’s so much useful information in there about what’s happened with the plan generation in the optimizer (not low level stuff, but the big picture items) that you should always be checking it first as a fundamental part of your plan examinations.

Blogs

Accept the no and move on

By

Here is a short emotional intelligence (EI) post for today, courtesy of Seth Godin....

Don’t Fight with AI

By

I was recently trying to handle a simple task with a few AI tools...

Narrow Task Decomposition in AI Pipeline Agents

By

A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...

Read the latest Blogs

Forums

jdbc auth failing to sql from sap's cloud middleware CPI

By stan

hi , our business partner is asking s4 sap api's for receivable info and...

Searching for my own posts

By pietlinden

I have a really stupid question... Is there an easy way to search for...

How to Work with On-Premises AI Models to Generate T-SQL Code

By Daniel Calbimonte

Comments posted to this topic are about the item How to Work with On-Premises...

Visit the forum

Question of the Day

Escaping Strings

The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?

See possible answers