T-SQL Tuesday 171 – Most Recent Ticket Closed

What would you say…you do here?

This month’s T-SQL Tuesday invite comes from Brent Ozar who wants to get a glimpse into what we’ve been doing lately. Rather than cherry picking and choosing the most impactful fix or query optimization, the invite asks to write about the last ticket we closed, regardless of whether or not it’s related to T-SQL or your average workload. As Brent includes, “database jobs cause us to do all kinds of oddball things through the day.”

To see the full invite, click the T-SQL Tuesday logo.

Most Recent Ticket

I opened Jira, searched my closed projects, and the latest closed ticket was configuring non-prod and prod databases for a new client install. Besides one database getting populated with some additional test data, both setups are about the same. Each environment needs the databases created and referenced in the appropriate locations. They also need users and the necessary security rights.

After completing the configuration, it’s always a good idea to test logging in through the application and also verify backups are running as expected. Once the setup is complete, it’s time for other teams to begin working with the clients.

For this particular solution, I have this work pop up on my calendar every couple months or so, and it’s usually doable within an hour or two. It’s not too tough to fit into the schedule.

In Order

This client setup was around the time new solution updates were being released. That reminded me of a very old issue worth mentioning that can be a “gotcha” if you ever roll out a release in groups (meaning a couple clients get the release first, then more clients a week later, then the remaining clients a week after that). If you’re basing new databases on some type of model/starter database, take note of when that database is updated during the release cycle compared to when it is used for a new client configuration.

Consider that a release is being deployed to three production groups, and the model/starter database isn’t updated until after all groups are updated. If only clients in the first production group have been updated but a new client is scheduled to get setup in that group, make sure the process is adjusted appropriately. Otherwise, you could complete a release with all client databases on version 2.0 except for that new client installed with the old version 1.0.

Thanks for reading!