Voice of the DBA

Tag: tools

Moving On After a Technology Fail

Recently my smartwatch broke. I was coaching volleyball and demonstrating something to a few kids when a ball hit the case of my watch just right and broke a corner there the watch band attaches. I’ve been playing and coaching with my watch in this way for many years and never had an issue, but apparently there was enough material fatigue that this time something snapped. I was very sad as this was my ten-year gift from Redgate, which I’ve loved, used, and cherished for 7 years now.

I wonder if there’s a 20-year gift …

In any case, I lived for a day before I realized I really depend on my smartwatch. I quickly realized that I constantly look at my watch to check the time, run a stopwatch at volleyball, track my heart rate and exercise for health, and most importantly, wake me up with a vibration in the morning. Before I had this I set an audible alarm, which my wife hated. At the time the case broke I was very busy, and after a quick set of searches and very minimal evaluation, I just bought a Garmin Venu 2Sq as a replacement. It was inexpensive, but appeared to do most of what I wanted. If I decided I didn’t like it, I wasn’t out a lot of money.

I contacted Garmin, but they said they wouldn’t repair or replace cases. Maybe they assume technology that is more than 5 years old is too prone to failure and not worth fixing? Maybe they just want to sell new products and not support old ones? I get all that, but this age of disposable digital tech is a bit annoying and mildly upsetting to me. I constantly fix old things on the ranch and I like keeping devices going as long as possible. Why not make cases replaceable? I feel the same way about a few devices that have embedded and built in cords. One of my Google cameras had a cord failure when a cat chewed it and the entire device is not junk because I can’t repair this tiny cable and Google won’t. But I’m getting distracted here.

This new watch is very different. Less buttons, more touch screen, and a different type of OS. I am having to learn how to use a new tool, which is both exciting and annoying. I am less productive in some ways as I learn a new tool, and I’m sure I’m missing things because I just want the tool to work rather than invest the time to learn about (potential) ways to use it. I know that there might be plenty of features I learn about that I’m uninterested in using, and I’ll have wasted time.

I see this often in technology. Many of us get used to working with tools in a certain way, and we learn to be productive. We get comfortable, develop habits, and work around annoyances. If the tool changes, or we are forced to use a new one, often we don’t like the change. We may feel lost and not see the advantages of a new tool.

I see this all the time as I work with customers. Sometimes I can see better ways they can accomplish tasks, and sometimes I see the cost of change is too high. Even a more efficient way of working can’t overcome a loss of productivity for a long period of time if too much change is required. Leaning on existing tools, skills, and habits can be efficient and comfortable. Going through the hassles of change can be worth the effort. Like most things in the database world, the devil is in the details and the answer to the value of changes is it depends. Sometimes a new tool is valuable and sometimes it is not worth the effort.

Almost a month into a new watch, I’m unsure of whether I like it or not, but in the short term, I’m too busy to spend time looking for a new tool. Unfortunately, that’s the state of the world often for many of us. We live with good enough.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

Note, podcasts are only available for a limited time online.

February 21, 2025
The End of Azure Data Studio

I don’t know how many of you will be disappointed or impacted by this, but Azure Data Studio (ADS) is being retired, as of 6 Feb, 2025. It will be supported for a little over a year, until 28 Feb, 2026. On one hand I’m not surprised, and on the other, I’m a little shocked by this.

I have written a number of articles on ADS, and shown how things work, as well as pointed out a number of things that don’t work well in the product or its extensions. These pieces have gotten a number of reads, and people have commented on them, so I wonder if there are a lot of you that are upset by this. Is this going to change the way you work? I will say that it will lightly change my work, as I do use ADS to connect to PostgreSQL, but not so much for SQL Server.

I have tried to use ADS, but I just don’t like it. I don’t have a good reason, as it does a lot of what I need from a query tool. I think the port of the query and result experience from a real app like SSMS or Enterprise Manager or even isql/w is just a worse experience. I don’t like the ADS interface and it’s annoying to me.

I suspect that many others feel the same way (other views from Deb and Kevin). They don’t like the ADS experience and prefer SSMS or some other tool. I know there’s been no shortage of complaints over the years about, and finally MS has listened. From first trying to get everyone to leave SSMS to forcing people to install ADS alongside SSMS and now to finally retiring the tool. I think it’s a good decision as people don’t want to lose SSMS and it’s hard to maintain two tools.

We will still have VS Code, which I use often for other purposes. I haven’t spent much time with the mssql extension, but I need to as it’s been updated as of a few months ago and supposedly works better now. We’ll see.

In the meantime, I won’t mourn ADS. It was a tool that had potential. I liked the idea of notebooks, I liked the fast startup. I just wish it were better implemented as a run-a-query-and-get-results application. I wish we had a cross platform editor that was simple and fast, but not one based on VSCode. One that’s written to just manage queries. Maybe they’ll rewrite isql/w in a modern way and port it to Linux.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

Note, podcasts are only available for a limited time online.

February 12, 2025
Connection String Confusion in SSMS
Recently I was trying to use a connection string to connect in SSMS. There are some tools that have a connection string available as an output, including some Redgate tools. ADS lets me paste in a connection string. Can I do this in Management Studio (SSMS).

Yes, but be careful.

Getting a Connection String

There are lots of ways to get a connection string. You can build one, or use a site like https://www.connectionstrings.com/sql-server/ I tend to get them for applications, as I work more with app developers.

In any case, I’ll use this as my string:
```
Server=Aristotle;Database=Sandbox;Trusted_Connection=True;
```
If I open SSMs, I get a connection dialog like this one. I see the server, but if I wanted a specific database, I’d have to go to the second tab.

I could also go to the last tab, the Additional Connection Properties, and paste my string in there.

I press Connect and that works great.

If I open a new Query Window, I’m connected to the Sandbox database.

The Problem

Let’s change the connection. I’ll press the icon to the left of the database name in the image above. Then I’ll go to the second tab and pick a database. In this case, I’ve selected the Westwind database.

If I click Connect, I see this:

The connection string in the individual parameters overrides the selection here. If this were a day later, I might remember I’d put a string in the Additional Connection Parameters. I rarely use this and when this happened, I couldn’t figure out why this wasn’t working.

I thought this also happened with changing the main dialog and the server name, but this appears fixed. At least on SSMS 20.1, the additional connection parameters are linked with any saved systems I have on the first tab, so if I change servers in the drop down, the additional connection parameters link to the last entry for that server.

On my laptop, which has 20.2, I’ll enter this as a connection string in the last tab:

In this case, I have multiple container instances running on different ports. This instance is on port 41433. On the main tab of the connection dialog, I see this:

What happens when I press Connect? I get to this server:

The default port is SQL Server 2022, but the additional connection properties overrode the front screen in this case.

Summary

I’ve never had this problem in 30+ years of SQL Server work until this summer. However, it’s the first time I’ve really been focused on using connection strings more often than just entering values in the dialog. I only noticed this as I had a deployment going to one instance, but SSMS kept connecting to the other one and I didn’t realize this.

I think it’s OK to have conflicting values in locations, but it wasn’t clear to me that these values override others. This is documented on the MSLearn site, but it’s easy to miss this.

Hence this blog.
September 25, 2024
How Often Do You Update SSMS?

I got a message recently that SSM S19.3 is out. I am wary of major versions, especially with a few add-in tools, but I have tended to try and update SSMS regularly when it patches, which is about once a quarter. As I checked my desktop, I saw I was still on 19.1 (my laptop was 19.2), so I downloaded and updated both machines.

I wonder what the rest of you do. I know many of you have corporate rules and restrictions and you may not be able to update regularly, but in many places, I’ve worked, once software was installed, I could update it. Are you doing the same thing out there? Let us know in the comments, or better yet, include the version you are running.

Some of you might use VS Code or Azure Data Studio as well, which have more of a nag screen to update. I find myself updating ADS/VS Code more often, though not with every version. I tend to prefer software working and am less interested in gambling on potential issues unless there is a bug I need fixed.

My work at Redgate brings me into contact with lots of customers, and I find a number of them view software like I do. They prefer working versions over the latest and greatest. In fact, we’ve added options to many of our products so people who want the latest have a frequent updates channel. Others can get notified less often; we even have a 7/14/28 day switch in Flyway Desktop.

I tend to prefer updating a week or so after most releases, though depending on how busy I am, I might end up a week or two after the next release. I want to see if there are reports of issues or problems before I upgrade. However, even that is more often than what I hear from many others. Lots of people want to upgrade every few months, often quarterly, to minimize any disruptions to daily work.

Are you the same? I’m interested in SSMS, but what about other tools as well? Is this the same for patches of Windows/SQL Server? Do you upgrade some software more or less often? Let me know today with a comment in the discussion.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

February 2, 2024