T-SQL Tuesday #183 Roundup

I hosted this month’s T-SQL Tuesday party with my invitation asking about tracking permissions. I didn’t get my own post completed in time, but I’ll add it in the next week sometimes.

In any case, here’s a roundup of the posts I saw. If I missed any, ping me and I’ll add you.

As usual, Rob Farley is first to respond. Since he’s in AUS and I can’t my New Zealand friends to participate, I’m always glad to see his post appear late on a Monday my time. His post looks at how he does health checks for clients, examining the permissions for logins. He doesn’t care if it’s a SQL login or not, but it should be a controlled login of some sort. He has other thoughts, and it’s a good look at the things you should consider when managing security with an eye on the reality of how people acesss data. Read this one.

Shane O’Neil has some PowerShell for us. He works with AGs and separate instances, so he needs to ensure the correct logins are on each replic.

Hugo Kornelis talks about how hard it is to get an overview of permissions. He says there is no permission heaven, but he has some suggestions on how to set up permissions.

Deb the DBA gives us a few things to think about in a large organization. A nice overview of what to consider and how to talk to others.

Rob writes about the importance of visibility in managing permissions.

A relatively quiet month for T-SQL Tuesday (including me). If you are reading this, then I hope you are planning on participating next month. Let us know your thoughts on a topic. If you don’t have a blog, here is how to start.

If you have a blog, where are you? Share some thoughts? Take 15-20 minutes and help pay it forward by helping others.

Posted in Blog | Tagged , | Comments Off on T-SQL Tuesday #183 Roundup

A Little Brainstorming with an AI

I was asked to do some a little thinking and brainstorming recently. Rather than send some emails or get on a call, I decided to ask my local AI a few things. This talks about the responses and reactions from my local DeepSeek AI..

This is part of a series of experiments with AI systems.

Requests for Feedback

I’m a part a research group that is trying to learn how to work better with others inside or outside of an organization. As a part of this, I was asked for some questions we might use to survey people on how they work as a baseline.

I was a little stumped on where to start. I had some ideas, but everything sounds to vague or too specific and I felt as though I couldn’t find a good place to start. So, I decided to ask my AI.

I have a DeepSeek model running in a container, so I opened my browser and asked this question: What are some questions I can ask employees to understand if they collaborate well with others?

The response was interesting. DeepSeek tries to give you some insight into how it approaches the problem. The initial responses showed a little stream-of-consciousness that reminded me of someone thinking out loud. Here’s the first part:

Okay, so I need to figure out how to determine what questions to ask when employees work together. I’m not really sure where to start, but maybe I should break it down step by step.

First, I think about why we’re asking these questions. If it’s to understand collaboration, then we want to know if the team is working well together, communicating effectively, or if there are areas they’re struggling with. So, what kinds of questions would help us assess that?

I remember reading somewhere about gathering feedback from employees. Maybe those are good ones because they can show how each person feels about the group’s work. But how exactly do I phrase that? Like, “How have you felt about the team’s performance so far?” or something along those lines.

Then there’s communication style. If an employee doesn’t contribute much in the moment, maybe asking them to describe what went on before they spoke would help identify if their approach is effective or not. It sounds a bit direct, but it might reveal issues like being quiet when someone speaks up later.

Collaboration skills are another area. I think it’s important that employees know how to work with others, so asking specific questions about group processes and roles could be useful. Maybe something like, “What do we use for planning meetings?” or, “How often do you give feedback within a week?”

From there it had more explanation and then it said “consider the following structured approach:” and it gave me a set of bullets, which you can see some of in the image below.

2025-02_0298

This wasn’t quite what I was looking for, but it did get me thinking and helped me send a list of possible questions to the group to consider. This was as helpful as if I’d have called someone, but way quicker and I didn’t interrupt anyone else.

I was genuinely pleased by the way this went.

A Recommendation Letter

I had an author ask me for a recommendation letter. This has happened in the past and I’ve written a few of them, but I always struggle to get one written that sounds professional and not like I’m a clown of a DBA/Editor who wears Hawaiian shirts to professional events.

Again, I decided to ask DeepSeek to outline one, giving it the title of an article. It had a few suggestions and then gave me a draft. My prompt was: draft a reference letter for XXX YYY for the article: ipsem lorum ipse lore.

First I got the thinking, making sure I was considering the aspects of the article, should I point out some technical things in my recommendation. It also thinks about including the impact of the article as well. Next, I got a draft with some “insert name” and “insert date” places.

I then added another prompt noting this was for SQL Server Central, which is a respected and long-lived (24 years now) publication well read in the industry. DeepSeek then adjusted its thinking, noting that we want to include info about SSC, how we review articles, etc.  This was the end of the thinking, which I really liked. It’s the type of thing a human might say to let me know what they’re going to do:

2025-02_0299

The draft letter is still a little off, with too much praise for me. This is a good article, but it’s not amazing. In any case, this gave me a decent first draft I could edit and then send off to the author.

It’s not that I couldn’t have done this, but this draft saved me some time and allowed me to clarify my own thinking about what I actually wanted to write.

I think this is slightly better or worse than if I’d asked a human to help give me a draft. Some people might have given me a slightly better draft, some worse, but I’d still be adjusting the tone and editing the content. I know because I’ve used humans for this exact task before.

This was interesting to me to play with an LLM and look for help. On balance, this didn’t take long and I think I did get some help from an AI. It didn’t do my work, but it helped.

Posted in Blog | Tagged , , | Comments Off on A Little Brainstorming with an AI

Republish: The Change Failure Rate

It’s President’s Day in the US and I have a day off, where I’m coaching volleyball up in Greeley, CO. And slightly worrying what maintenance might be waiting for my back at the ranch.

You get to re-read (and re-comment) on The Change Failure Rate. Interested to see if people view the world differently after a few years.

Posted in Editorial | Tagged | Comments Off on Republish: The Change Failure Rate

Choosing to not drive the Tesla

I started a short thread on Twitter/X and Bluesky recently after leaving the Tesla at home recently. A few people asked me about it, so I decided to do a short update, as this is my computer on wheels.

This is part of a series that covers my experience with a Tesla Model Y.

A Busy Weekend

A few weeks ago, we traveled to Greeley, CO to coach in a tournament. My wife and I coach two teams this year with our daughter and it’s very busy. This particular weekend, we were coaching the afternoons on Saturday and Sunday and Monday morning in Greeley. The catch was our second team had a Sunday morning tournament in Golden.

We had booked a hotel in Greeley and decided to take two cars as we knew the Sunday morning event might run long and we needed to be back in Greeley. Our schedule of places, times, and drives was:

  • Saturday 11am – practice (17 miles from home)
  • Saturday 2pm – Greeley (72 miles from the gym)
  • Sunday 7am – Golden (64 mi drive from hotel)
  • Sunday 2pm – Greeley (64 mi from Golden)
  • Monday 3pm – Leave Greeley for home (83 miles)

Around this, there likely are a few short trips of a few miles. Dinner, etc., so these are estimates.

The other caveat on this weekend was the weather was predicted to be in single digits (in the F scale) overnight. Either positive or negative, but cold. The highs were 11F Sat, 15F Sun, and 8F Mon.

Planning the Trip

We already knew we needed two cars, so the question was: is the Tesla one of the two cars?

Some snow was expected, and I didn’t worry, but my wife had a bad experience heading to the mountains one weekend in heavy, wet snow and the Tesla defroster didn’t work well. Neither did the wipers.

That was a minor concern for me, especially as I learned how to get hot air rather than the default cool air for the front defroster.

The bigger issue was time. In trying to get up to Greeley, we would be tight on time. I’d be asking to go over 200 miles without a charge in very cold weather, across 2 nights.

Or we’d be looking to stay up late one night to charge at the Loveland supercharger, which is a 20 minute (each way) drive from Greeley. There are some chargers in Greeley on a map, but when we tried them last year we found:

  • 1 didn’t work
  • 1 was very slow (level 1 slow)
  • 2 were busy

These were separate locations in the town, where businesses had set up fast charging. This isn’t a knock on Greeley, it’s just the reality of EV charging in some places. This is an unfamiliar place and I don’t trust most charge stations owned by various companies.

At least not when time is a factor.

The Final Decision

I didn’t want to be stressed about charging, so we decided to leave the Tesla home. It wasn’t that important, certainly not to worry about charging time or having enough charge in a very cold environment. I took our old Suburban and my wife took her diesel truck.

There ended up not being much snow, just a few flurries, but it was very cold, and we were racing from place to place. In coming back Sunday to Greeley, we had a 10 minute cushion according to Google Maps and lots all that trying to get a cup of coffee and some lunch from a stop. Even if we’d have aimed for the Supercharger for 10 minutes, they don’t have food service nearby. There is a hotel at the supercharger, but they’re a) slow and b) expensive.

I’m happy with the decision. I missed driving the Tesla, but it made sense to skip it for this trip.

Posted in Blog | Tagged , | 2 Comments