When writing TSQL, it’s often useful to make your TSQL idempotent – a fancy word, which in the case of databases really just means: you can run the command again and again and it will make sure that you have the intended effect, without causing problems by being run more than once.
In this challenge, you get to take a crack at creating an Event Notification to track schema changes.
In this challenge, you get to take a crack at writing a DDL Trigger to track schema changes.
Flex your T-SQL skills: you’re challenged to write four different (but related) queries in this query writing challenge.
In this challenge, you are tasked with editing a stored procedure to gather data from multiple databases. What’s the most efficient way to do it? Try your hand at the challenge, then check out three different suggested solutions.
Ready to tune some TSQL? In this challenge, you’re given a database to restore. You’ll create two indexes and a constraint in the database– and you aren’t allowed to change those.
Your challenge is to identify which statement is slowing down our stored procedure the most, then tune the code to speed it up.
Your challenge is to de-duplicate the indexes on a table in a sample database. Can you predict which indexes are the safest ones to drop?
This challenge comes in three possible levels of difficulty: choose one or work through them all!
You’ve got a query that is just too slow!
A database administrator has changed Cost Threshold for Parallelism on the instance, and you’ve got a query that’s slowed down.
Sharpen your skills at fighting blocking and deadlocks.