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:
In the roughly 25 years of I have been in IT, we're still dealing with the same problems.
— Allan Hirt (@SQLHA) August 30, 2016
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>
Whatever your problem, this month is a chance to give your stump speech, and raise some awareness about it. Perhaps we can even make some progress in fixing some of these problems.
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.
Awesome topic Andy! Thanks for hosting. Here’s mine: https://sqlstudies.com/2016/10/11/if-backups-are-taken-in-silence-can-a-recovery-still-take-place/
Systems Monitoring Systems – http://itsalljustelectrons.blogspot.com/2016/10/systems-monitoring-systems.html
Delivering databases (DLM) – http://workingwithdevs.com/t-sql-tuesday-still-terrible-at-delivering-databases/
Thanks for hosting this month; you can find my contribution at https://chrisyatessql.wordpress.com/2016/10/11/t-sql-tuesday-83-were-still-dealing-with-the-same-problems/
Thanks for hosting this month! Here’s mine: https://sqlatspeed.com/2016/10/11/t-sql-tuesday-83-cant-we-all-just-get-along/
Thanks for hosting this month! You can find my post here: http://blog.sqlterritory.com/2016/10/11/in-the-8-years-i-have-been-using-sql-server-were-still-dealing-with-lack-of-cooperation/
Hmm… my comment doesn’t seem to have been picked up properly, only the trackback. Anyway, thanks for hosting. http://sqlblog.com/blogs/rob_farley/archive/2016/10/11/passwords-a-secret-you-have-no-right-to-share.aspx
Sorry, Rob– There was a problem with comments being gobbled up by WordPress this morning. Your first comment must have been breakfast for my blog.
Thanks for taking part!
Thanks for hosting. My contribution: “Can’t we get this sorted?” http://scribnasium.com/2016/10/cant-we-get-this-sorted/
T-SQL Tuesday #83: Resource Governor CAP_CPU_PERCENT: It just runs faster? http://sqlsoldier.net/wp/sqlserver/tsql2sday83resourcegovernorcpu_cap
My pingback didn’t work so I’ll have to leave it as a comment. Why leave well enough alone? https://therestisjustcode.wordpress.com/2016/10/11/t-sql-tuesday-83-why-leave-well-enough-alone/
As a C# developer who is well liked by the DBAs that I work with because I 1) seek out and respect their input and 2) take the time to deep dive into SQL Server, my comment is “In the 15 years I have been using SQL Server (22 years total developer experience), we’re still dealing with developers who don’t understand good database design.” I know, I know, I am a “traitor” for “siding with DBAs”. Sometimes the truth hurts! 🙂