There are two slightly different ways of representing non-existing spatial data, the "empty geometry" concept and database NULL. You can read about the subtle differences between them here. If you're using a spatial index, either of these types have the ability to cause query perforamance problems. Let's take, as an example, a table with 10000 rows, all of […]
Bob Beauchemin
SQL Server Blog
Be careful with EMPTY/NULL values and spatial indexes
Posted on: September 22, 2009 12:35 pm
See you in Berlin at TechEd 2009 Europe
Posted on: September 16, 2009 10:00 am
I've found out that a few of my talks have been accepted for TechEd 2009 Europe, which will take place this year in Berlin, Germany, on Nov 9-13. I'll be doing some SQL Server performance-related talks. If you're in Berlin, stop by and say hi, it will be nice to see everybody again.
A “What’s New” at the Portland SQL Server User Group
Posted on: September 10, 2009 2:10 pm
I'm speaking at the Portland SQL Server User Group meeting this month about What's New in the SQL Server World. I'll be talking about upcoming new features in SQL Server 2008 R2 and upcoming features and products (like SQL Server Azure and Entity Framework 4.0) that could affect the way that you work with SQL […]
Temporary table lifetime and SQLCLR stored procedures
Posted on: September 1, 2009 11:45 am
People are sometimes concerned with the lifetime of temporary tables they create in CLR code. As an example, if I use a parameterized statement in .NET code, the SqlClient provider wraps the statement in exec sp_executesql. If the statement batch includes something like "CREATE TABLE #temp1" as part of the batch, the table #temp1 is no longer visible when the […]
