Voice of the DBA

Tag: syndicated

  • A Cloud Dependency Failure from Amazon

    I went to sleep while reading a Kindle book on my phone. I know because my hand dropped and the phone knocked me in the forehead. I set it on the nightstand and went to sleep again.

    I woke up and was planning on reading for a few minutes before starting my Monday. When I opened the Kindle app, it asked me to log in. When I did, Amazon said my account was locked and I needed to check an email. I did, and found one from Amazon.co.uk questioning a purchase I made and asking for me to very an order number and the last 2 digits of a card to charge.

    I wasn’t sure what to do, but since my wife was complaining about her Audible account, I knew I needed to do something.

    I didn’t like the email for multiple security reasons, including not giving me a way to verify the email online. Checking Amazon’s help page said I should have a link in the email to a form. Even when I called the Amazon help line, they said I should have a link when I logged in to do so. I didn’t on either the .com or .co.uk sites, but Amazon Customer Service eventually unlocked my account.

    I wrote about Dependencies in today’s editorial, inspired by this story and the Reddit story linked in there about losing access to Claude. That’s scrary, especially in this new automated world where AI agents might be examining activity and undertake this type of action to prevent other issues. It’s an overreaching type of judgment that starts to expose the dangers of a highly interconnected world.

    I get Amazon might want to ensure my purchase was legitimate and perhaps prevent future orders, but also locking my content away (books, movies, audio, etc.) because of a shopping issue seems extreme.

    It’s certainly my issue, and I’m not sure how I untangle things for the future, but it does make me think about limiting dependencies a bit more in the future. Or at least understanding the dangers of too much on one service.

    Whether that’s the books I read or the services my company gets from any one vendor.

  • A Redgate Data Modeler Gotcha with Relationships

    This happened to me recently after being busy with non-data modeling tasks for a few weeks. I went to add a relationship and was confused about the behavior. Read on to see what happened and what I did.

    This is part of a series on Redgate Data Modeler.

    Adding a Relationship

    I opened one of my models and saw something like this. Note that the Article and ArticleTag entities aren’t related.

    2026-04_0220

    I decided to add a relationship. This is a Many to Many, so I clicked on that icon in the toolbar.

    2026-04_0221

    I then clicked on the Article entity and saw this. It’s a self-referencing relationship.

    2026-04_0222

    What??? I assumed I’d click one entity, then the other. I tried grabbing various elements of the relationship to move them, but nothing worked. I could move them around within the relationship, but not to another entity.

    2026-04_0223

    I deleted and added this a few times before I decided to check the docs. On this page for relationships, I found my mistake. There is this quote: “If you’ve already selected the tool, simply drag from one entity to another.”

    Aha.

    If I click the toolbar relationship icon, and then drag from one to the other, it works.

    2026-04_0224

    I suspect this is an artifact of the web controls, but it was weird for me to not be able to alter the relationship targets. Even in the right properties pane, I can’t change this.

    2026-04_0225

    Summary

    A simple thing, but not quite as intuitive as I’d like. However, one needs to learn to use tools, which means reading docs or using Claude/ChatGPT andfingers crossed

    This is a reminder to drag relationships in your Redgate Data Modeler models and don’t get away from modeling for weeks, like I did.

    Give Redgate Data Modeler a try and see if it helps you and your team get a handle on your database.

    Video Walkthrough

    Here’s a short video of my working with Redgate Data Modeler and changing cardinality.

  • Advice I Like: Celebrate Success

    “On the way to a grand goal, celebrate the smallest victories as if each one were the final goal. That way, no matter where it ends, you are victorious.” – from Excellent Advice for Living

    I believe in celebrating small things. I am a big “smell the roses” and “celebrate your success” even if the bigger part of the success feels like a failure. If I deliver a good demo in a talk, or one of my players makes a good hit/pass/etc., let’s celebrate that. If the rest of the talk wasn’t smooth and people are confused, or we kept hitting the ball in the net, that’s a bit of a failure and something to work on.

    There’s always a bright side and a dim side. One is likely larger, but both are there.

    I think if we look at something in black and white terms, and reduce it to success or failure, then you create a psychology that you win or something wasn’t worth doing. The sports teams, the musicians, the friends I have, my kids, we aren’t defined by whether we win every time. We can’t be the best all the time.

    Even the best of the best isn’t the best most of the time. Tom Brady (7 rings) and Michael Jordan (6 rings) might be considered the best at what they did. However, they played more years (Brady 23, Jordan 15). Were they failures those other years?

    The Beatles had 19 #1 albums, the most of all time. However, they released more. They had lots of #1 songs, but plenty that didn’t get to #1. Were those not worth doing?

    Celebrate your success. You might write a great query, but ultimately there are plenty others that don’t perform well or some might even return the wrong results. Hopefully you’ll fix and improve those, but celebrate the things that go well.

    Work on those that don’t and turn them into victories later.

     

    I’ve been posting New Words on Fridays from a book I was reading, however, a friend thought they were a little depressing. They should be as they are obscure sorrows. I like them because they make me think.

    To counter-balance those, I’m adding in thoughts on advice, mostly from Kevin Kelley’s book. You can read all these posts under the advice tag.

  • SWAG Saves the Day

    PASS Summit East is in one week.

    I was on the road last week in the UK and then Houston for the Houston AI-lytics event. I had been a little under the weather all week, and when I arrived in Houston, I decided to stay in the hotel and rest. Plus the 6:00 arrival was midnight for my body.

    I walked next door and got some takeout and then grabbed a beer from the hotel store to relax and get to sleep early. Unfortunately, the bottle needed an opened. Fortunately, I was prepared.

    2026-04_line0036

    This little opener is a piece of swag I got from Redgate years ago and I’ve kept it in my bag for just such occasions. No walking back to the desk, no disappointment, just a handy item that let me relax and get to sleep by 8.

    I don’t know what swag Redgate or others will have next week at the PASS Summit East 2026 in Chicago, but if you don’t go, you won’t know. Register for the event, book a flight, come join me.

    Sure, you might get some just-in-time training from a precon that lets you learn about PostgreSQL from Grant and Pat or how to secure your estate from Andreas. Did you know Andreas did this job for Microsoft for years, architecting security features?

    There are lots of sessions where you might get inspired by a demo or get a question answered about your environment. Those are great, but who knows what SWAG you’ll find. You might get a handy tool you didn’t expect that saves your day, or night.

    Send yourself. Send a colleague.

    Send someone today to learn a few things, connect with others, and collect some swag. Register for the PASS Summit East and join me in Chicago next week.