SQLServerCentral Editorial

Now you ODBC me now you don't

Phil Factor reflects on Microsoft's "handbrake turn" on OLE DB; Denali's successor will have to have all this plumbing ripped out to replace it with the older ODBC technology. It's a surprising move but makes a lot of sense, given the ubiquity of ODBC drivers for relational data access.

External Article

The SQL Server Query Optimizer

To understand how to write SQL code for SQL Server that performs well, it is important to appreciate how the query optimizer works. Ben Nevarez explains the essentials, in a broad sweep through a complex subject, in an article taken from his new book 'Inside the SQL Server Query Optimizer'.

Blogs

The Book of Redgate: Get the right stuff done

By

Another of our values: The facing page has this quote: “We admire people who...

Runing tSQLt Tests with Claude

By

Running tSQLt unit tests is great from Visual Studio but my development workflow...

Getting Your Data GenAI-Ready: The Next Stage of Data Maturity

By

I remember a meeting where a client’s CEO leaned in and asked me, “So,...

Read the latest Blogs

Forums

Introduction of OPTIMIZE_FOR_SEQUENTIAL_KEY = ON

By saum70

Hi, We have low latency high volume system. I have a table having 3...

The Long Name

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Long Name

Eight Minutes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Eight Minutes

Visit the forum

Question of the Day

The Long Name

I run this code to create a table:Create table with unicode nameWhen I check the length, I get these results:Table with length of name shown as 132 charactersA table name is limited to 128 characters. How does this work?

See possible answers