Category: Blog

  • T-SQL Tuesday #116–Always Linux

    tsqltuesdayThis month is an interesting invitation from Tracy Boggiano. It’s on Linux, which I like. I hadn’t thought about this in terms of T-SQL Tuesday, but I think it fits and more than that, I think Linux will be the future of the backend data platform from Microsoft. I’ve said it in a few presentations, and I think we’ll get there in 10 years.

    In any case, I wanted to write about how I use Linux and SQL Server.

    Containers for Work

    One of the technologies that I see gaining a foothold in many companies is containerization. More and more developers are using containers, and asking for their databases to work in containers. At Redgate, we’ve been investigating this and are looking to build solutions that will use containers.

    As a result, I’m experimenting with SQL Server in containers on my laptop ad giving some presentations that share the way in which they work. I’ve written a little at SQLServerCentral as well as on this blog.

    In setting up my laptop, I installed Docker and experimented a little with Windows and Linux containers. I’ve standardized on Linux containers, because they’re more mature for production (Windows containers are in preview now), and I think with Kubernetes and the growth of how the SQL Server 2019 Big Data Clusters will work, I expect more Linux for servers in the future.

    I’m also using this as an opportunity to brush up on some bash and Linux skills, connecting to my containers with the –it (interactive) switch, as well as using the Windows Subsystem for Linux.

    It’s slow learning, and it’s interesting trying to juggle things in bash and PowerShell at the same time, but I expect these skills will become more hand in the future.

  • Learning More about Kubernetes (K8s)

    I know a bit about this, but I’m always looking for more. I had the chance to see Brendon Burns recently and I was impressed. That is one seriously smart dude. In any case, I saw a link from Microsoft: 50 days from zero to hero with Kubernetes. It’s at this link: aka.ms/learnkubernetes

    I decided to dig in a bit, because it’s a complex subject in some sense and going through some resources can help solidify how this works.

    Day 1

    It’s a children’s story of a visit to a zoo, with an attempt to explain what pods, replica sets and other items. The first few items made sense to me since I’d worked with K8s slightly before.

    However, as the story delved into more complex subjects, like Ingresses and Daemon Sets, I had a vague idea of what ese were, but not really. I’m not sure I could explain back what some of these do. I hope future days will help me understand.

    Day 2

    Day 2 is a video on Containers from Brendon Burns. He talks about the history of VMs and then lightly on what a container is and how this fits together. Since I’ve watched some of Nigel Poulton’s courses at Pluralsight, this makes sense and reinforces what I know. It also gives me another way to explain things.

    However, for others, I wonder if this makes sense to them. It’s a very high level, but fast view of containers. Worth watching if you want to know more.

    I’ll continue on with the series as I get time, likely a very sporadic look at this technology.

  • Taxing Travels

    It was a long weekend of travel for me not too long ago, starting at 4:30am on Friday and ending at 7:30pm Sunday night. This was for SQL Saturday #884 in Pensacola, an event I’ve attended 4 or 5 times, a few with my daughter. It’s always enjoyable, and this year was no different.

    However, the travel was surprisingly hard. I need to write a bit more about this, but I was surprised by both the issues that cropped up and how well the flights actually went. I’ll also mention that I had the 3 of nicest flight attendants I’ve ever interacted with on the three different flights. Thanks, @United staff.

    Flight 1

    This started when I hope at 430am Friday. I showered, and checked my phone, seeing a message that my flight was delayed. That’s pretty cool that two hours before flight time they can let me know of issues. I was thinking since this was such an early flight that the plane would be in Denver overnight, but I wasn’t thinking. There are early flights East of here and they can fly to arrive at Denver in time.

    Or not. In this case, weather in the Chicago region delayed the plane, which is why I try to avoid Chicago. In a big deal, but about an hour delay. With a 2 hour layover, I wasn’t too concerned, and headed to the airport. I arrived, got a cup of coffee and went through email/Slack at the gate. Travel doesn’t necessarily stop me from needing to deal with other work, so I made use of the time.

    Our plane arrived, people got off, I was ready to get on. Unfortunately, we were missing a flight attendant. One would think that scheduling staff is easy. It’s not, especially across time zones, locations, and potential limits on working hours. I don’t know if an employee had an issue in Denver or was on another flight or what. In any case, I know people that are in the airline industry and on call. They try to get  to the airport quickly when called, but things happened. In this case, we added about 15 minutes to our delay over just over an hour.

    Flight 2

    One of the really neat things in the United mobile app is that I get information on gates and times, updated during the flight. Almost all United planes have wifi for entertainment, and you can purchase Internet access, but you get access to United data for free, like where your plane is flying.  You can look at a map that gives you an idea of how close you are.

    In this case, I was watching because we kept banking slightly. The generic flight map looks like this:

    den-ord

    Mine looked more like this (I should have taken a screenshot):

    p2-us-map

    To avoid weather, we kept turning. We actually came into Chicago from the North, after circling around the East. I got a side view out of the plane of the downtown area as we came in.

    20190628_101503

    We were late, and I had about 35 minutes before the other flight left, which means 25 minutes to get there. One thing I’ve learned is that the major airports have gate maps in the airline magazine. In this case I was going from one end of C concourse in O’Hare to the other end of F concourse. Not an easy journey. I jogged, and got there with about 10 minutes to spare. If I hadn’t been able to jog, life would have been rough.

    Normally I get a text on delays, but I think the stack of flights was delaying messaging because as I walked up to the gate, I could see the delay message. As I talked to an agent, my phone vibrated with the delay alert. This is one place I think United could do a better job of data sharing, but in any case, this was another scheduling issue.

    My plane was at the gate, workers were outside, so no lightning delays. However, our flight attendants and a pilot were in Milwaukee, which isn’t that far a drive from Chicago. They couldn’t take off because of weather, so we were delayed, even as other planes were coming and going.

    About 2 hours here, but again, a great flight attendant that was very pleasant when we did get going. I took the time to eat some lunch and do a little writing. I’d started some things on the plane that I finished on the ground.

    Flight 3

    After the event, I was at the airport a little early. I sat at a restaurant, writing up some notes from the weekend for changing a presentation as well as reporting for Redgate. The plane arrived on time and we started boarding. I fly enough to be part of the pre-boarding group, so after those with disabilities and families, I scanned my pass and started down the jetway. There I found a line of 6 or 7 people, with a few already on the plane. Since someone had gone with a wheelchair first, I assumed that this was the delay.

    Then I heard someone on the plane tell us to drop people from coming down the jetway. A few minutes later an agent came down and had us all walk back up the jetway and back into the terminal.

    Apparently there was a ground stop in Denver that the pilot had heard, so I can forgive the app not updating me. A 45 minute delay, under mostly sunny skies in Pensacola, though clouds in the distance. This was more concerning, and a little stressful. No work getting done now as I was worn out and annoyed.

    Almost an hour later, we start boarding and get on. The pilot will try to hurry and we take off. I have a couple drinks, thinking this is the end of a long weekend. It’s not.

    As we get close to Denver, we get good news and bad news.

    Good news: Denver is landing planes, albeit slowly.

    Bad news: we need to circle a bit and have an hour of fuel. If we don’t get landing clearance in an hour, we’ll go land somewhere else. Fortunately we have a little plane, so lots of choices.

    30 minutes later we get clearance and land. About two hours later than planned, but still, I’m home.

    Lots of Challenges

    I wrote this because I was thinking about all the challenges in flight operations and trying to coordinate many moving parts. It’s quite a logistical challenge, and while computers can help, I’m sure many humans need to be involved in some decisions along the way.

    These were really minor hassles in my life, and I’m not complaining. More, I’m in awe of the amount of data that must be managed and used to make decisions and direct humans. I didn’t check bags, but I have, and I’m always amazed how well my bags get from point A to point B, especially when I’m running to make connections.

    Nothing went as planned in my flights, but it all worked out well for me. Not for some others, but weather can be a big factor in traveling. I think the main thing I’ve learned is avoid Chicago and Chicago based planes whenever I can.

  • Come See the Future of Database DevOps at SQL Sat Austin

    I’ll be coming to SQL Saturday #890 – Austin in just over a week. Austin is a great technology town, and this should be one of the larger SQL Saturday events. I know traffic is tough, but the event is at St Edwards University, which isn’t downtown, so hopefully some of you can come.

    I’ve got two talks, and I’m excited about both. I’m doing a DevOps talk about the overview of how to incorporate the database into a DevOps flow. This has been a popular talk across the last few years, and I’ve given it at the Summit a couple of times.

    The other talk is one I’m more excited. The Future of Database Development with Containers is a look at how we might use SQL Server in software development in the future. It’s something Microsoft has shown some ideas with, but I’ve got some cool Redgate technology to show off as well, with a database-as-a-service from the Foundry.

    Register today and come see me and a few other fantastic sessions.

    If you want more training, there is a great pre-con on Friday as well. You can learn Data Science with Chris Hyde and add to your skillset. It’s good preparation if your company wants to perform more complex data analysis.