What is T-SQL Tuesday?
T-SQL Tuesday is a monthly blog party hosted by a different blogger each month. This blog party was started by Adam Machanic (blog|twitter). You can take part by posting your own participating post that fits the topic of the month and follows the requirements below. Additionally, if you are interested in hosting a future T-SQL Tuesday, contact Adam Machanic on his blog.
This month’s topic
At the end of August, Allan Hirt (blog|twitter) tweeted:
I proceeded to flood Twitter with a bunch of things that IT has been messing up for years. At the end of my tweetstorm, I realized it would be a wonderful topic of T-SQL Tuesday.
Of course, because this is T-SQL Tuesday, let’s put a database-centric spin on Allan’s original tweet. For this month’s topic, I offer two fill-in-the-blank topics:
- In the <N> years I have been a database professional, we're still dealing with <some problem>
- In the <N> years I have been using SQL Server, we're still dealing with <some problem>
Some inspiration: Vectors for attacking this topic
You could write about bad habits we still haven’t kicked. There is plenty of misunderstood functionality that people still get wrong. And of course, Bobby Tables still lurks in some applications.
There are plenty of problems that aren’t specific to database professionals–should we be leading the charge to fix these problems? Everyone has stories from the hiring process. Everyone dreads paperwork.
And of course, there’s the SQL Server product itself–an enhancement request you’ve been pining for, or a bug that hasn’t been squashed.
(Just try to avoid kvetching too much. Remember to talk about how to solve the problem.)
How to Participate
- Your post must be published between 00:00 and 23:59 GMT Tuesday, 11 October, 2016.
- Your post must contain the T-SQL Tuesday logo from above and should link back to this blog post.
- Trackbacks should work. But, please do add a link to your post in the comments section below so everyone can see your work.
- Tweet about your post using the hash tag #TSQL2sDay.

