SQL Server Database Administration

Git Command Line Tutorial with SQL Change Automation for SSMS (video)

I’m really excited for Redgate’s new SQL Change Automation plugin for SQL Server Management Studio (SSMS). SQL Change Automation lets DBAs and developers use a migrations-first approach to create precise scripts to apply changes to your database. If you’re curious about what I mean by “migrations-first”, read more about this approach, and how it compares to a state-first approach here. I’ve been working with SQL Change Automation with Git for a while in Microsoft Visual Studio. Visual Studio contains a lot of integration by default with Git and Azure DevOps, so I’ve been using its graphical tools, for the most part. The new SQL Change Automation extension for SSMS works with the Version Control System (VCS) of your choice, but this initial release provides only “working folder” support That means that you set up your version control outside of SSMS, then point SQL Change Automation at your working folder. This…
Read More

SQL Server Management Studio is as Relevant as Ever

1 Comment
Sometimes you keep a classic around After almost fifteen years of heavy usage by developers and database administrators (DBAs), it might seem like Microsoft’s free tool, SQL Server Management Studio (SSMS), is about to go out of style. After all, SSMS is no longer the cool new kid on the block: Microsoft has shown consistent effort to develop their new tool, Azure Data Studio (the artist formerly known as SQL Operations Studio), since November 2017. Azure Data Studio is built on the modern foundation of Microsoft’s VS Code, whereas SQL Server Managed Studio is related to the legacy Visual Studio Shell. Based on this overview, it might seem like a new SQL Server DBA or developer should primarily learn Azure Data Studio, not SSMS. And it might similarly seem like vendors should focus on developing new tooling only for Azure Data Studio. But when you look into the details of…
Read More

How Developers and DBAs Collaborate in a DevOps World (video)

You’re a DBA, and your development team is all-in on doing DevOps, and they want to include the database. Should your DBA team limit the permissions or options for automation? Or should you instead re-think how your two teams work together? In this 40 minute episode, Kendra discusses DevOps team topologies, the changing role of DBA teams in DevOps, and the opportunities available in creating communities of practice around database development. Prefer to listen on the go? You can get this episode on iTunes, download the audio file, or find Dear SQL DBA in your favorite podcast app. Bookmarks of topics covered 00:30 – Our question, from a DBA 7:00 – Why bother with DevOps? 9:23 – Team topologies, aka rethinking how the teams work together. This discussion includes notes on where and when DBAs review changes and talk about architecture in a DevOps way of working. 21:20 – Changing…
Read More

What’s Unique About SQL Saturdays: Nearly Everyone Interacts with Other People

My friend and colleague, Kathi Kellenberger, taking questions in her SQL Saturday session on Machine Learning for beginners Today I was looped in on an email thread about the pros and cons of attending a specific event. One person on the thread asked if any of us had attended the event in the past, and whether or not event attendees were engaged with presenters and vendor representatives. My immediate thought was: of course the attendees were engaged, because the event is a SQL Saturday.  I’ve never been to a SQL Saturday where the attendees weren’t engaged. But, I realized that it’s a fair question. This level of interaction isn’t a given for events, much less tech events I’ve been to other tech events — from free events to very expensive ones — where attendees didn’t interact much with anyone else. Mostly people worked away on their laptops/phones/tablets quietly (maybe taking…
Read More

How to recognize the early stages of burnout, and my treatment plan

I recently realized that I’m in the early stages of burnout. This isn’t an unfamiliar place for me, but it is new for me to recognize the early signs of burnout in myself before it becomes a full-fledged disaster. This time, I’m thinking about how I got here, and making an explicit plan to change course. In the hopes of helping someone else out there, I thought some public journaling might be in order. How do you recognize if you’re in the early stages of burnout? I have recognized two symptoms which I identify as unusual for me. Together they indicate I’m heading towards burnout. Symptom 1: Lately, I get frustrated and angry by small things One warning sign of burnout is when small inconveniences start causing a disproportionately large emotional response. For example, on a recent weekend I was traveling for work. I was in the Detroit area, about…
Read More

Paying down technical debt

One of the cool things that I do as an Evangelist at Redgate is to periodically visit company headquarters in Cambridge. The other Evangelists and I get to meet with every software developer, product manager, and UX designer at Redgate over a series of meetings. That’s really cool. We talk about things that they’ve released lately, what they’re looking at doing in the near future, and we get to give feedback based on what we hear from the community and from folks in the sales process. We also get to share what we personally think should happen in these products now. As you might imagine, I have a wish list for features in a variety of different Redgate products Our products are great, and one of the things about great products is that users are always inspired to want to use them in new ways, so I never lack for…
Read More
Menu