Episodes

  • This is my last day of work. Not forever, just for six weeks. I'm off on my sabbatical after today and won't be back until August 11. However, everything should run smoothly with Grant and Kellyn holding things down until I return. Have a little patience with them as this site can be a bit of a hectic whirlwind at times, and they still have other jobs to do.

    It's been a wild first half of the year. After very little travel in Jan/Feb, the rest of the year has been a bunch of travel, including most of May and June being on the road. With coaching responsibilities for two teams from Jan-Apr, I am ready for a break. No big plans, but I am looking forward to being at home, playing some guitar, working on a few projects while trying to be very unwired for six weeks.

    Read the rest of A Well Deserved Break

  • I ran across an article on the 7 types of tech debt that can cripple your business, which is a great title. It certainly is one that might scare a lot of CTOs/CIOs/tech management. I am sure that much of the IT management gets concerned on a regular basis with how quickly their staff can evolve their software to meet new business needs.

    The first two items have to do with data, which is understandable. Data is the core of how many organizations operate and move forward, and if you don't have the ability to easily work with data in a flexible way, you can struggle. Many of us technical people know this, but I find many non-data-professional staffers don't get this and are often unwilling to work at improving the situation. They things to just be magically better without changing how they do their jobs.

    Read the rest of The Technical Debt Anchor

  • Missing episodes?

    Click here to refresh the feed.

  • Each time I compile and curate the Database Weekly newsletter, I find lots of Fabric content from the various sources I watch to compose the newsletter. Since I primarily deal with the Microsoft Data Platform stack, this makes sense. Most of the things I am interested in are related to Microsoft, and as a result, I tend to use sources that also use SQL Server, Power BI, Fabric, and related technologies. I do look for other related data items, but I am heavily MSSQL focused.

    Recently, I stumbled on a piece that contains Fabric Alternatives in AWS, GCP, and OCI. It covers some of the options on these cloud platforms at a very high level. A product name and short description, but it shows there are other choices. I found it interesting that Databricks is mentioned, but not Snowflake. I'm not sure why that is, as Databricks is on Azure (and other platforms) as is Snowflake, but perhaps the author doesn't consider Snowflake a peer? That seems strange.

    Read the rest of The Data Warehousing Choice

  • Part of my Redgate work is with customers who need to monitor their database servers. With estates growing quickly, both in scale and types of database platforms used, keeping an eye on everything can be challenging. Add in the lack of staff growing as quickly are the number of servers, and I find many companies seeking out monitoring tools to better help them manage the entire estate..

    When someone evaluates a tool, one of the first questions from many people is about load. They are concerned about the load a tool puts on the system, which is always some amount. Most tools say they use less than 2% of total resources, some might hedge at 5%. Hopefully, there's no more impact than 5%, though that might seem to high, especially if you have a busy database server already.

    Read the rest of Multiple Monitoring Tools

  • Are you looking forward to SQL Server 2025? Or perhaps you think this is just another release, or perhaps you are not looking for new features or capabilities in your environment. Maybe you don't care about new things, but are looking for enhancements to features introduced in 2017/2019/2022. There is certainly no shortage of things that can be improved from previous versions (cough graph *cough).

    I ran across an article on the five things that one person is looking forward to in SQL Server 2025. It's a good list, and the things included make me consider an upgrade. Certainly, any improvements in the performance area, especially with all the investments made in Intelligent Query Processing over the last few versions, are worth evaluating. They might help your workload, or they might not, but if they do, then upgrade.

    Read the rest of SQL Server 2025 Excitement

  • I had to make a few changes to a SQL Saturday event recently. The repo is public, and some of the organizers submit PRs for their changes, and others send me an email/message/text/etc. for a change. In this case, an organizer just asked for a couple of image updates to their site. I opened VS Code, created a branch, added a URL for the images, and submitted my own PR. After the build, I deployed it.

    And it didn't work.

    Read the rest of Patching the Patch

  • When talking about DevOps, the goal is to produce better software over time. Both better quality as well as a smoother process of getting bits to your clients. There are a number of metrics typically used to measure how well a software team is performing, and one of the things is Change fail percentage. This is the percentage of deployments that causes a failure in production, which means a hotfix or rollback is needed. Essentially we need to fail forward or roll back to get things working.

    For most people, a failed deployment means downtime. I've caused a service to be down (or a page or an app) because of a code change I made. This includes the database, as a schema change could cause the application to fail. Maybe we've renamed something (always a bad idea) and the app hasn't updated. Maybe we added a new column to a table and some other code has an insert statement without a column list that won't run. There are any number of database changes that might require a hotfix or rollback and could be considered a failure.

    Read the rest of What is a Failed Deployment?

  • Many of us are faced with choices and decisions constantly in our jobs. How do we approach a problem? What should we do as a team to get the work done? How do we code or manage or test or do something else with a database?

    Maybe more importantly, how long do we spend deciding?

    Read the rest of Shorten the Debate

  • At an event recently, I had a chat with someone after one of my sessions. I had been speaking on DevOps and ways to better structure your team and build software. After the session, one person asked me if I'd read The Mythical Man Month and if I felt we'd gotten a lot better at building software since that book was published.

    I do think we have gotten better, way better, in fact. I caught another review of the book a while back from the Pragmatic Engineer. That view looked at what's changed in 50 years since the first edition, as well as contrasting the world today. You have to subscribe to read that one, but I'll give you a few thoughts from me on the book itself and the review.

    Read the rest of Reflecting on the Mythical Man Month

  • I've been reading an interesting book that looks at some of the ways that we can better build software in enterprises. One of the side notes in the book is that the tech companies have the funding and the ability to disrupt many other types of businesses, not just technology. Google, Amazon, Microsoft, and others have delved into other types of industries, potentially pushing others out.

    We see Amazon becoming as much a shipping and logistics company as they are a retailer. There was a unionization vote, which passed in 2022. Recently, another one failed. Amazon continues to fight these efforts, trying to prevent workers from collectively negotiating the terms of their employment.

    Read the rest of IT Unionization

  • At a recent event, I had a student ask about how to get started as a data professional. What types of things should they do? What platform should they work on or learn? Where should they focus time? What tools are available?

    Those are all good questions and many of you likely have your own advice. I'll give a few things to think about today, which are good for anyone that might want to get into the data field. I think this is still one of the better technical careers. I've suggested this to my kids, though only one of them went into a technical area. One is a therapist for autistic children and one helps run the ranch while pursuing a graduate degree in literature.

    Read the rest of Helping Students with a Data Professional Career

  • I saw an article on AI usage that is based on an upcoming book that suggests redesigning the world around new tech, not adding it to existing things. The first example is how electricity was introduced to existing factories, but it only provided some incremental gains until new factories were redesigned around electric motors. There's also an example given about reworking hotels to remove the front desk since that feature isn't needed. Instead, people could walk in, and an employee with a tablet could find them to check them in.

    I'm all for rethinking and redesigning processes. I do think we have a huge glut of software in many organizations that exists because processes have evolved across time, but not everything and we keep our old software. When we have a new need or want a new capability, we add new software (or add features), but we don't necessarily throw out all the old software, processes, or habits. That wouldn't be practical, often because when we implement something new, it might not meet all our needs. Or at least we don't know it meets our needs at first.

    Read the rest of Changing the Paradigm of Work

  • As a part of my job, I often work with customers on how they can get database code into a version control system. That's Git for the most part today, which is the most popular system in the world. I'm comfortable using Git for many basic tasks, but I am not an expert by any means. I've used version control for years, and quite a few systems, and I like Git as a way of managing code.

    I have been surprised how many people aren't comfortable with version control or Git. Many don't have the habit, but are amenable to it. What I'm amazed by in 2025 is how many people don't use it, given that so many tools we use to work with databases, and even other systems, will store items in Git. This isn't just for development code, but also for infrastructure code. Lots of data tools and servers can store data in Git and use it to deploy changes to all kinds of systems. I'd have expected more people to know Git.

    Read the rest of Does Version Control Scare You

  • It likely isn't a surprise to many of you that executives like AI. A survey shows that 74% of executives surveyed have greater confidence in AI-generated insights than advice from colleagues or friends. At the board level, even more (85%) favor AI-driven advice.

    That's amazing to me, and while I might think this is a bit too much trust being placed in these GenAI LLMs, perhaps it's also partially because they work with too many people who aren't great at their jobs. Plenty of people skim through data or focus on certain things and might miss the details. While an AI can read and summarize a lot, it might not have the context we expect. I tend to be a bit skeptical of AI summaries, often because they don't necessarily weigh the different parts of an article the same way that I do.

    Read the rest of The AI View From Above

  • I read a piece recently that got me thinking that data breaches might be inevitable. Disclosure: This was written by Redgate, for whom I work, titled "Data breaches May Be Inevitable—Compliance Failures Don’t Have to Be". It's based on our research with the State of Database Landscape survey as well as feedback and conversations with customers.

    The thing that caught my eye was the first part: data breaches may be inevitable. Do you think that's true? Are we doomed to lose data in our organizations, not as a possibility, but something that will happen at some unknown time in the future? Those of you who have suffered breaches might agree with this, but for those of you who haven't had to deal with that situation, are you resigned to it happening at some point?

    Read the rest of Are Data Breaches Inevitable?

  • Who among us has deleted a production database?

    I'd hope it's very few of you that have done this in your career. I'm sure a few of you have deleted (or truncated or updated all rows for) a table in production. I've done that a few times, but fortunately, I've been able to recover the data quickly. I had this happen in SQL 6.5 and was grateful I could start a single-table restore before my phone rang.

    Read the rest of Deleting a Database

  • The DORA organization is constantly researching how to better produce software at any organization. This is similar to work done by Carnegie Mellon Software Engineering Institute many years ago. Both groups are trying to determine what things help engineers work better and produce high-quality software.

    On the DORA site, there is a database change management page, where they recommend approaches to managing database schemas. The main thing they talk about is treating all schema changes as migrations, which is something some people do. However, many teams also like a desired-state-configuration approach, where they just deploy all the changes from dev (or QA) to prod in a state-based flow. Both can work, but I do think as software matures (and becomes legacy), migrations are preferred. The article lists lots of frameworks in different languages. Flyway is among them, which is the product on which I work and sell at Redgate. If you haven't looked at a migrations framework, I'd recommend you do so. They do really give you a tremendous amount of control and flexibility. There are trade-offs, so I'm not blindly recommending this approach, but it's worth educating yourself on how migrations frameworks work.

    Read the rest of Database DevOps Recommendations

  • I'm sure many of you have tried a GenAI LLM to do something. Maybe write some code, maybe get some sort of recommendation or suggestion, maybe to rewrite something or summarize text. I'm sure you have had some feelings about whether the tool made you more or less productive.

    There was a trial conducted by the Australia Department of the Treasury on Microsoft's 365 Copilot, asking for volunteers to participate and use the tool in their daily work. They used it and then completed a survey, which are summarized in this piece. Only 218 people went through the trial, and the results are interesting.

    Read the rest of How Helpful is a GenAI Copilot

  • Certifications can pay off, at least in some areas. There's a piece that talks about pay rising for some tech professionals when they have some credentials. Networking, architecture, and project management are mentioned in the report, as are database and data management.

    I haven't seen the source report, and I'm not sure which certifications are getting higher pay rises, but I'd guess that newer data technologies, things related to cloud databases, and even anything related to AI is likely to get you a raise.

    Read the rest of Rising Pay for Certifications

  • I thought this story about a programmer and a GenAI to be rather humorous. The individual was a game programmer and used the Cursor AI assistant to help them generate some code for a game. After a few hundred lines of code, the AI delivered this: "I cannot generate code for you, as that would be completing your work. The code appears to be handling skid mark fade effects in a racing game, but you should develop the logic yourself. This ensures you understand the system and can maintain it properly."

    That response makes me actually smile to myself and chuckle out loud. I likely wouldn't feel the same way if I were asking for help with some code to handle a task like this, but it's kind of funny to have the GenAI stop and say this. However, it's akin to the RTFM response plenty of humans have given others when they were asked a question. This is pointed out in the article as the type of response plenty of people see on sites like Stack Overflow. Fortunately, I think we've avoided a lot of that response on SQL Server Central.

    Read the rest of Learn to Code