Voice of the DBA

Author: way0utwest

  • Quick Filtering in SSMS–#SQLNewBlogger

    I saw someone limit the databases they see in SSMS, which isn’t something I often do, but I thought this was great.

    A Long List

    This is the list of databases on a demo instance I have. While it’s a lot since I do a lot of testing with customers and colleagues, I see plenty of people will lists of databases longer than this.

    2023-09-18 09_39_38-Window

    I also watch them scroll like I do when trying to find an object in a database.

    However, for demos, this is a lot, so I like to slim things down. I used to have a script to detach all the databases and then attach the ones I need, but that’s time consuming and once in awhile, I need a different database, so that’s an issue.

    I saw the someone filter their list by clicking the filter button in the Object Explorer. This is the funnel button shown here:

    2023-09-18 13_57_35-Window

    Once you click this, a dialog appears that let’s you enter your filter criteria. I’ll use a simple filter of “zero” to limit to those databases in my zerodowntime demo.

    2023-09-18 09_39_25-Window

    Once I click “OK”, I see only those databases listed.

    2023-09-18 09_39_18-Window

    If I want to get everything back, I can click filter again and then delete my criteria, or click “Clear” filter. That gets me the entire list back.

    2023-09-18 09_39_32-Window

    Easy.

    SQLNewBlogger

    This post was something I jotted a note about when I saw someone do this. The note was literally “write about filtering in SSMS object explorer”. I took that and wrote this post in 10 minutes, including time to grab screen shots.

    You could do this as well, showcasing the knowledge that you’re learning to use tools better, which make you more productive. Employers love that.

    Write your own post with more advanced filtering.

  • Running a Service

    Many of us work for some organization and we’re responsible for managing a database or coding some application or some other data related position. Perhaps we ensure reports work for our users or move data around. In many cases, we have customers, whether they are internal to our organization or perhaps external from another business or even the wider public.

    However, many of us see our jobs as a part of the org/business and not that we are actually providing some service to others that we are responsible for. While I’ve certainly felt that way, I learned at some point that if I were an app dev, I ought to treat people using my app as customers, even though they don’t pay me in currency. They often pay me in praise, or better yet, with praise to my boss. As a DBA, I treated both app devs and users as customers. That helped me take pride in my work and learn to view my position from other points of view.

    There was a post on learnings from running a SaaS service for a year. While few of us maintain a SaaS service, we could think of the app we build as Software-as-a-service, albeit without any revenue. We could see databases we manage as DBaaS (databases as a service) or PaaS (platform as a service) items.

    I think that the way we view the world, or view our situations, can be helpful to us in managing our workloads. We can better triage what is critical, what’s important, and what’s nice to have. We can decide when an issue deserves some to cause some stress and we might give an extra effort, and when something can wait until tomorrow. We can decide when we push back on demands and when we accommodate them.

    This approach has also helped me to think about ways to improve the service/software/platform I provide to others in ways that helps my customers, or makes my job easier. This way of thinking leads me to make the situation better when I can. It also helps me to discuss the decisions with others, especially management, in terms that can matter to them. Are we finding ways to improve the overall system?

    It doesn’t always work, but it often has for me.

    And if you’re interested in your own side project, the journey continues in part two. Perhaps you can spend an hour or two a day and build something that becomes your own business. That’s what happened to me with SQL Server Central.

    Steve Jones

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

  • SQL Saturday Denver 2023–VCS Primer for the Database slides

    My slides are here: VCS Primer Denver 2023

    This was an overview of what version control is, and the basics of Git.

    Not too many questions, but if you have some, ask.

  • Are You Worried About AI?

    The AI revolution is happening. I don’t know how successful it will be, but regardless, people are trying to get AI into everything. That might be good or bad in various situations, but it has people worried about AI. This piece looks at a survey from the American Staffing Association that says 47% of people somewhat or strongly agree that their job is replaceable by automation with an AI. There is more data to dig into, but that’s a lot of people who worry about their jobs.

    Most people do think that tech is generally a good thing. I do find that many of us in tech, and some other industries, are buried in work. There’s never a shortage and we could easily work 60, 70, or more hours a week and not complete everything. The flip side of that is a lot of work doesn’t necessarily need to be done now and could be delayed, so I think it’s hard to decide whether we need more help or more patience.

    The various places I’ve seen AI used are often helping people get started or unblock their creativity struggles. Recently someone posted this link on some prompts a person had used to get moving. I found a few of these possibly helpful. Not writing, but maybe having an AI proof something, or even get me started in some new area. I worry about book summaries, or even text summaries, as I’m not always confident the AI understands which pieces I might find important. However, that’s also a danger with humans. I’ve seen no shortage of people asked to summarize something for others. When I understand the subject well, I sometimes disagree with another’s summary (or think it’s just plain wrong).

    I don’t think AIs are a big danger to many people’s employment. I do think that as people learn to use AIs are assistants we might find that we grow or enhance staff less. We might also find that the 10x engineer knows how to engage 10 AIs to help them get things done, especially simple, busy work. The low performers will likely be those working in the same way in the future as they do today. That might not threaten your job, but it might mean lower bonuses and less opportunities in the future if you can’t adapt your skills to this new world.

    Steve Jones

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