In this 4th post of the ‘A Join A Day’ series we are going to take a detailed look at the cross join statement. The cross join is probably the simplest of all join commands, but it still has its surprises. Read on, to find out more.
It is T-SQL Tuesday time again. For T-SQL Tuesday #37 I would like to ask you to join me in a month of joins.
This post looks at the inner join T-SQL command. After reading you will be able to use it and explain how it handles data and how to identify it in an execution plan.
In December 2012 I am going to publish one post per day about SQL Server Joins. With topics ranging from fundamentals to internals there should be something interesting in there for everyone.
The 5 Key Points for Effective T-SQL Unit Testing presentation covers topics like framework selection, test-case selection, separation of concerns and some T-SQL unit testing specific topics. [more…]
How long does a temp table live? Who can see and access it? What other types of temporary objects exist? What is a temp table Eclipse? This article will take an in-depth look at temporary objects and answer questions like the ones above.
Renaming a Windows server hosting a SQL Server installation is fairly straight forward. Most of the changes necessary for SQL Server to continue to work happen automatically the next time SQL Server restarts. However there is one notable exception…
Announcing the Agile Database Development Training tour, following the SQL In The City training events. [more…]
In this session we are going to take a deep dive into the columnstore index feature introduced in SQL Server 2012. We will compare columnstore with b-tree indexes and see why a columnstore index is not really an index at all.
After attending you will be able to identify queries that will benefit from columnar storage. You will be able to explain how the data in a columnstore index is stored on disk and which access mechanisms are available to SQL Server. You will be able to see whether a query is running in row mode or is utilizing the new batch mode and explain the difference between the two.
In this talk we will also cover the gaps that were left in the current implementation, scheduled to be filled in a future version of SQL Server.
Row-Overflow data storage is a mechanism that was introduce in SQL Server 2005. It allows for more flexibility when designing tables as it makes it possible to store more than 8060 byte in a single row. This article shows how this mechanism is working under the covers.