Moving On After a Technology Fail

Posted on February 21, 2025 by way0utwest

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.

Posted in Editorial | Tagged , | 1 Comment

A New Word: Tangency

Posted on February 21, 2025 by way0utwest

tangency– n.  a fleeting glimpse of what might have been.

I tend to live in the real world as it is, not too dreamy or wishful that things were different. I tend to accept things as they are.

I don’t see a lot of tangency, as I am more appreciative of where I am, knowing that if things had been different in my past, I’d be in a different place.

I’m happy now, so I’m happy with the path I walked.

However, I do see some tangency when I coach. Not for me, but for the kids, because I know that having some success breeds more desire and confidence. I want these young ladies to grow up strong and able to make the life they want.

There are moments when I see the indecision or the lack of reaction or the mistake. Once in awhile there’s a split second where you think you’ve won, only to have the referee let you know you haven’t. To me, that’s a fleeting glimpse of what might have been.

From the Dictionary of Obscure Sorrows

Posted in Blog | Tagged , | Comments Off on A New Word: Tangency

Making a PostgreSQL Backup in a Container

Posted on February 19, 2025 by way0utwest

I needed to back up a PostgreSQL database as a part of the repro for an issue I had. I hadn’t ever made a backup of PostgreSQL, so this was a learning exercise for me. Plus, a container made it slightly more complex than SQL Server. This post shows what I did.

In looking over the documentation and in searches, everyone seems to use pg_dump to make a backup. This looks hokey and immature to me, essentially a command line tool to script things out.

There is also a file level backup and a PITR backup strategy,  but those are more complex for my use case.

So, how do I run pg_dump?

I found this article, which is helpful, but contains a lot of stuff. Essentially, I need to connect to my container and run from there. I’ll use the exec with the it switch from Docker to do this.

So, first I run this to get a shell inside the container.

docker container exec -it pgdev /bin/bash

The image below shows me connected to the container with a bash shell.

2025-02_0286

Now I can run pg_dump. I’ll use this command, which connects to the db with a user and sends a database backup to the /usr location.

pg_dump -U postgres -Fc bb_fullrestore > /usr/bbfull.dmp

Once this is done, I can go check. First, I’ll ls this folder and I see my file.

2025-02_0287

Summary

As technology advances and I use containers more, I’m hesitant to keep installing stuff on my machine that I don’t need to. I’d rather have scripts. Trying to just get pg_dump installed is a pain, so this post shows how you can access this in a container and create a backup.

If you’ve mapped your folders in a container to your local machine, then you can easily find this file and most it elsewhere for a restore.

Posted in Blog | Tagged , , | Comments Off on Making a PostgreSQL Backup in a Container

Is Ransomware Fading?

Posted on February 19, 2025 by way0utwest

There were less ransomware payments in the second half of 2024, according to research from cryptocurrency tracing firms. There were certainly some high profile attacks, but this matches with my impressions from talking with lots of fellow data professionals around the world. This article talks about the trend, and speculates that law enforcement actions may have had some effect.

My guess is that this is likely a temporary decrease as there are no shortage of criminals and so many tools are available on the Internet, especially the dark web. The idea of writing a piece of software to encrypt files isn’t complex, and we’ve had people writing viruses for years. I suspect there are no shortage of smaller criminal organizations and individuals that will step in to continue attacks in the future. Whether that will be a lot of attacks or a few, I don’t know.

One of the other problems is that so many organizations are loathe to disclose they’ve been hacked if they don’t have to do so. Lots of them would prefer to just pay a ransom and get back to work. I don’t know how many IT pros agree with that, though often the employees just want to get past the attack as quickly as possible and restore their systems. I know that they often worry about future attacks, but I also wonder if many IT pros know how to check their systems to be sure the malicious software is gone.

Securing your environment is hard, especially when most users (and IT people) want convenience. Many infrastructure people want to log in with a single account and get things done. Or they want an easy way to switch accounts when necessary, which isn’t always convenient. Some of us are used to the runas command, but I’ve met many people who aren’t.

I do like that much of the world is moving to using managed identities or service accounts for processes, known accounts for CI/CD that can handle deploying code while each of us just approves the deployment with our own credentials rather than directly moving bits. I am glad to see more and more people without rights to log into production, only to submit batches to a system to run and get results sent back. All of those are good things which can prevent an infection from a website or email from spreading to production systems.

However, we still have lots of interconnections between systems for important data stored outside of relational systems. Even storage explorer type access for Delta/parquet files can be a problem if you have that. Databases are safer from ransomware, assuming you can lock down all OS/file system access. Maybe we ought to store more data in databases, even those crazy Excel/Word/etc. documents as binary files.

I’m OK with that, as long as we have a separate instance for those files. I have no desire to see more binary files stored in my OLTP database, or even on the same instance.

Steve Jones

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

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

Posted in Editorial | Tagged | Comments Off on Is Ransomware Fading?