Welcome to T-SQL Tuesday for August 2017!
T-SQL Tuesday is a chance for you to join in the SQL Server community and write a blog post on a suggested topic. You can use this as a way to start a new blog, dust off a blog you haven’t used in a while, or make it part of regular blogging: your choice!
I would love for you to participate. The whole SQL Server community would. Please, join us!
Every now and again, I need use a global temporary table for some testing or demo code.
Each time I do, I stumble a little bit when it comes to checking for the existence of the global temp table, in order to make my code re-runnable.
Last week I answered a set of fun interview questions from Mohammad Darab. One question that he asked really jumped out at me:
What are you most proud of doing/accomplishing for the SQL Server community so far in your career?
I recently got a table partitioning question from a reader:
We now need to load some historical data into the table for 2013 so I want to alter the function and schema to add monthly partitions for this. But I can’t work out how to do this using SPLIT? Every example and tutorial I’ve looked at shows how to add new partitions onto the end of a range, not split one in the middle.
You’re designing table partitioning, or you want to make a change to an existing partition function. It’s critical to understand the difference between how “left” and “right” partition functions behave, but the documentation is a bit confusing on this topic.
Table Partitioning in SQL Server has a bit of a learning curve. It’s tricky to just figure out how much data you have and where the data is stored.
Table partitioning seems simple, but there’s a lot of complexity in designing and managing it if you decide to use filegroups and splitting.
When you first implement partitioning in this scenario, you decide where you’re going to keep “out of bound” data when you create your partition scheme. Be careful when you make that decision, because it may not be easy to change later.
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.