Comforting Habits
Voice of the DBA
I was chatting with a friend recently about routines and some of the helpful or silly things we do. I mentioned that when I played adult baseball, we often had Sunday morning games and a routine of mine was to drive to town, stop at a 7-11, and get a large cup of coffee and an apple fritter. It was a comforting habit that I still have today, often stopping when I have a morning flight to do the same thing in the way to the airport. Only in Denver though, not when I'm flying out of other cities and returning home. Read the rest of
info_outline
Big Data or Small Data
Voice of the DBA
I went to San Francisco for , a conference sponsored by The premise of the event was that smaller sets of data are both very useful and prevalent. The speaks to me, as I am a big fan of smaller sets of data for sure. I also think that most of the time we can use less data than we think we need, especially when it's recent data. That often is more relevant and we end up with contorted queries that try to weight new or old data differently to reflect this. Maybe the best line for me is this one: Bigger data has an opportunity cost: Time. Read the rest of
info_outline
Learning to Grind
Voice of the DBA
When I was younger, I had a variety of jobs, but in most of the positions I had to work hard for stretches. Really hard, as in more than 8 hours a day or 40 hours a week. Often as I was starting a new position, it took some time for me to develop some understanding, some skill, and some muscle memory. In some jobs, especially in restaurants, I also had to build the physical skills to be on my feet for many hours. In technology, I've often found myself unsure of how to approach a new position, aware I had knowledge gaps about how things worked, and often, I was naïve or ignorant of some piece...
info_outline
The AI/Human Spectrum
Voice of the DBA
I was asked this question recently: is it more likely that AI will replace humans or assist them in their work? It's a good question. If you think about the way AI is being hyped in 2024, many people think AI is, or will soon be, replacing people and we need less of them in work. I guess the simplified view is that AI can do the jobs of many people, but I'm not sure the world is that simple. What I think is more likely is that AI becomes a lever that assists a few people in getting more work done and potentially replacing other, less knowledgable humans. Read the rest of
info_outline
Continuous Learning
Voice of the DBA
It seems there's quite a dichotomy in the technology workforce. On one hand I hear about the Great Resignation where many employees are leaving their jobs because of RTO (return to office) mandates or some other dissatisfaction with their job. On the other, I've seen quite a few people who were laid off and are struggling to find new positions. On the third hand, there is no shortage of companies who report they are struggling to find and hire talented people for some positions. I don't quite know what to think, but I do know that employment seems to be harder to come by. If you are looking...
info_outline
Why Would You Do That?
Voice of the DBA
info_outline
Distributed Monoliths
Voice of the DBA
I was watching a video called . In it, the person being interviewed said that a lot of people really have a distributed monolith. That caught my eye since I've worked with a number of customers who are trying to adopt microservice architectures for their applications. I think this is less a performance/scaling choice than a reworking of their software development teams, and I'm not sure they will end up with a better system. What is ? I am not an expert, but this appears to be a place where all the services still depend on each other. For example, I might have a service getting user profile...
info_outline
Reducing the Cycle Time
Voice of the DBA
There are lots of software development methodologies. lists a few, among them waterfall, agile, iterative, rapid, and more. What's been interesting to me is that the process of deciding what to code and then whether it works doesn't change much between different ways of building software. Instead, the cycle time between when we ask a client what to do and when we deliver it changes. The more agile/lean we are, the lower the cycle time. The more waterfall-ish, the larger the cycle time. I guess that analysis and breakdown of problems into work also changes, as the scope in modern DevOps styles...
info_outline
Doing a Little Research
Voice of the DBA
I've been very pleased with the direction of SSMS the last few years. As it's been separated from SQL Server releases and gets updated more often, I think the changes from v17 though v20 have been improvements. There are still issues, but it's been better. Now we finally have SSMS moving to a modern shell with and I'm excited to see how this changes the future of our tooling. However, the PM for SSMS, Erin Stellato, recently asking why people don't read documentation. She also asks what you want to see in 21, so respond if you think there are holes in the SSMS docs. I think this post came...
info_outline
Have Grace
Voice of the DBA
Thanksgiving is tomorrow in the US and it is supposed to be a holiday when we give thanks for our blessings in life. My wife usually has everyone in our family tell what they are thankful for this year. I also see many people posting things they are grateful for during the month of December. Last month I was lucky enough to have dinner with Bob Ward and we were talking about some of the things we'd seen in travels, often some stressful times for ourselves or others. We've seen many people get upset or angry or have some other reaction. Both of us have some empathy for others, recognizing that...
info_outlineRecently I was watching a presentation on how to scale performance in your SQL Server environment and one of the suggestions was setting up Availability Groups (AGs) and having read-intent connections that would query the secondary and not the primary. It's not a bad idea, and the SQL Native Client (and other drivers) support this and make it easy to implement.
The pattern of using multiple connections in an application, one for reads and one for writes, has been suggested often. However, in practice, I've rarely seen this work. Apparently having a connection variable, named dbConn, for writes and a second one, named dbConnReadOnly, for reads is too complex for most developers or teams.
Read the rest of Separate Reads