Hello there everybody and welcome back to of course Redgate DB Ale the podcast that is all about data and beer and increasingly DevOps jokes about my mum and Chris not remembering to get the beer he said he was going to of course my name is Chris. I've also forgotten about your mum and to make jokes about your mum. Of course my name is Chris. I can't remember my name.
Well my name is what my name is. Slim Chrissy. Slim Chrissy I like it. Yeah that's definitely not true I'll do it.
You know what I put it down to all the tortilla chips I ate before this meeting but I'm feeling good. I've only had to do it today. Stick a fork in me Chris I am done. Anyway welcome everyone to this episode 35 I think of DB Ale can you believe we've been going for so long my goodness if we make it to 36 Chris you realize that will be three years worth of episodes and.
Hey, it's it's it's a beautiful thing but guess what. What. Today we are going to be talking about the Olympics of database DevOps that is of course how topical how topical that is of course we are we were a little bit late to record for the Olympics, however we are just in time to record for the Paralympics and fortunately team GB is off to a flying start in fact it seems like the games have been absolutely wonderful so far and massive congratulations to everyone who has been taking part. But today you can expect Chris and I to talk about the different stages of database DevOps and your kind of maturity as an organization when implementing database DevOps.
And then once we've spoken about the bronze the silver and the gold of database DevOps we will of course bring you the data breach news for the month followed by the events digest and rundown all as part of our beloved. You just want to say it twice in one episode that's greedy. Chris did you compete in the Olympics. Chris there isn't a category for the ugly.
If there was you get gold my friend. Thank you I appreciate that I like being the best. No I didn't unfortunately but Chris if you were competing in a sport let's say you competed in a sport of remembering what beer to bring to DBA all several months in a row. I'm afraid you would not.
Well no if you were in the sport of forgetting you would get a gold 100%. Oh cutting comeback. What I suppose just like this beer. Hey here I've got is karaoke tears how's that for a segue baby with cut so what beer were you supposed to get Chris.
I think I suppose to get one called karaoke tears. No you were supposed to get one called golden champion or the golden champion by the badger door sit brewers and it's a bright golden champion. It's a bright golden ale with floral hints of elderflower light and refreshing a crisp taste of summer. It is summer the Olympics are on and guess what if you are a champion at the Olympics you are a golden champion but no unfortunately even though I reminded you twice you didn't get it so you.
It's true. I have karaoke tears so I like this that late night karaoke haze we've all been there when emotions run high in the song keeps building. When our tuning isn't quite there and everyone knows when we are absolutely crushing it but no one cares sometimes tears follow route to celebrate those off key moments in front of friends and strangers. Karaoke tears hits that high note with a lotus hopper and no actual tears.
That is an extremely dramatic thing to put on the side of your cat. I was going to say something you read on the sofa whilst you're scratching your belly opening your third can and you go hmm interesting and then forget about it. Scratching your belly thinking yes this is exactly how I feel in a cat for exactly and Chris why did you why did you get this one. Well it's the best I could do I went into my larder and I could find and the only thing I could find that was vaguely related to the Olympics or Japan or the Paralympics was this one who's got karaoke in the name.
No I think you've done well actually if you come back in with like I don't know a stellar then I'd have been like Chris I'm thinking why is across here perhaps. Yeah that's not just that I mean Chris I have taste. I like stellar. I like taste buds.
Hang on I'm going to open up this champions. Nice. So Chris golden champion Olympics theme why exactly are we crowing on so much about these things why is this our theme. Why is it not segue was not smooth that was not smooth unlike this beer.
Oh. Such a good beer golden champion has has been probably for the last 10 or 11 years of my life one of my favorite beers to drink it's just a beautiful gold nail anyway but what you're telling me is that the reason we got the Olympics theme is to shoe horn or crowbar in your favorite beer. It's actually the only reason that Japan went ahead with the Olympics was so that I would be able to drink a golden champion for DBL. I thought I was the reason I was trying to cancel Olympics.
No, no I got on the blower and I said folks I know you're trying to cancel the Olympics but hear me out I've got DBL to record and when they heard that I mean obviously they knew who I was and they bent over backwards just to make sure they still went ahead I think it was very kind of them. Oh, hey, hey, come on, give me give me a little bit so I can get this really good segue and he was like I'm not I'm not trying to anymore Chris. I'm sorry. Hang on.
No, of course today we're talking about going champions because we're here to talk about the champions of database DevOps the star performers, you know, yes, okay there are other people out there like, you know, Facebook and stuff. I scan a who deploy what four 500 times a day with a little bit of help from you know who, of course, but what's Santa Santa Santa Santa and redgate they actually work together there's a workshop L and why it was a meaningful color choice. Okay. Yeah, exactly.
That's why you always end up with the database stuffed in your stocking at Christmas. But no, of course we're going to be talking about some of the behaviors that typify these sorts of performers and we'll talk about kind of what it is that makes up the kind of bronze silver and gold of star performers. But the interesting thing is Chris, the interesting thing is more interesting than what you just said, more interesting than what I've just said which is not hard because most of the things I say aren't inherently interesting, but more interesting than that. The thing to the thing to bear in mind when we talk about all of this right is that when you think about the Olympics and you think about people who win gold medals.
Do they stop. Like, do they go Oh, I want a gold medal. That's it I never need to compete again I never need to perform again I never need to run again. Otherwise I wouldn't cross the line.
But no, you've got to continuously strike those always people, there's always people in your heels and there's always faster right like you can always do better. You're running the hundred meter sprint or you say well you've got the world record well, you can strike to beat it again. Exactly, you are now your own greatest competitor and with complacency comes falling behind in the middle of the league and sometimes even off of the podium, the wonderful thing about the Olympics about sports and athletics in general, is that there's always going to be a new technique. There's always going to be a new approach there's always going to be new technology right even football right football has changed over the years.
People have gotten faster they've gotten stronger they've gotten paid more they've jumped higher they've gotten paid a lot more we've introduced VAR which some would argue is a good thing some would argue is a bad thing. But the thing is the landscape is always changing. And the landscape of technology is also always changing. So just because you're one of the world's highest performers in DevOps right now doesn't necessarily mean that you're going to continue being the highest performer in the next few years.
If you don't constantly strive to not reinvent the wheel, but do the most important thing that comes along with a DevOps process feedback review and improve. Right, right, nothing ever change. So that everything always changes everything always changes just because you know how to do infrastructure as code doesn't necessarily mean that you're going to be the next master of Kubernetes. So those people who 10 years ago when the Masters of Ruby on Rails.
Or a few years ago when they do was the big thing that everyone wanted expertise and now machine learning. There's always another big thing. artificial intelligence Kubernetes. I didn't want to say Kubernetes actually but I couldn't contain myself.
That's fine. I won't worry about it. These jokes only a few of them come to me at a time. They're just you'll find them in a cluster and then.
Yes, good, good. Okay, so what we're saying is that there's lots of different standards, I guess, and what we want to talk about is how people can achieve that what the differences is between the different standards and how what good looks like what. The level below that looks. Yeah, absolutely.
So I think the obvious place to start is the wooden spoon. I don't know if the concept of the wooden spoon translates globally, but in the UK generally it means last place, right? You've tried your hardest, but you've come last here's your wooden spoon. I thought that was the best dispersive award.
I thought I thought you were just collecting for your soup collection. Do you not think man? I got so many wooden spoons. I think I've got some thinking to do.
Yes, absolutely. But Chris, what would you say typifies someone who you would who you might say is not even a last place. I think even last place is someone trying to improve. Let's go with did not finish now did not start the end.
Definitely definitely Harry and accounting. Oh, I mean, what have you got against Harry? Yeah, I mean, for us, I think there's a few people we talked to who maybe have not really got the starting block when it comes to DevOps. So they really have an understanding, I guess, of really what it is at all the processes that they are running are extremely high touch processes, I say, with fingers in make shift.
Yeah, apostrophes quite well. You're someone what their deployment process is. They have to stop and really think about what a deployment process is. Well, we write a script and a few of us write a script and then we dump it in a folder and then we give it to Jeff and it suddenly like, oh, I guess I haven't really called it a process, but yes, I hear that so often.
And to be fair, for some people and very, very few people, but a lot of people, when they talk about this process, I even saw it on Stack Overflow the other day, which was, how do you manage your database deployments. And people are saying, you know, it's not like I'm proud of this, but we write scripts we give them to the DBA the DBA runs against the environment. If they work, we promote them. If they don't, we rework them.
Fish, bash, bash, and it's only so many times you can provide to DBA. This is true. This is absolutely true. Senior DBA, Uber, senior DBA, boss of DBA is DBA team lead and then Governor of California.
No, but the interesting thing is some people do are almost proud of this process, right? They're kind of like, well, you know, this is how our team has worked for 10 15 years. You know, this is just how it's always been. It's a mindset thing.
They have this belief that, you know, we are a team and we can write good scripts and they will go upstream and the things that aren't considered are what happens, not, not if what happens when something goes wrong. Or what happens when we need to respond faster to changes. And of course, it's not scalable, nor is it sustainable. We've spoken about this before as well, like people wanting to insert themselves as crucial cognitive machine because they believe that that that will give them power in some way or that will.
Exactly. Whereas the danger is actually the reverse of that, but all that does is really mean that you can't be promoted by the business or moved on to more interesting exciting things because you have this responsibility that no one else can do. Yeah. Absolutely.
Which is similar to knowledgeboarding, but it's slightly different way. It's like inserting as other as the crucial part of the process. But if I mean if I was to say, what is the enemy of DevOps, if I could pick one thing that was the enemy of DevOps, I think I would probably pick the word silos, because people like to silo themselves like give that to me that's my job I'm not going to show anyone how to do it. But also that goes for teams and goes for learning as well some some teams like to silo themselves off and spoiler alert everyone who's listening, even if you as a team based on our definitions on TV ale find yourself in the highest performing team right find yourself in that gold medal position.
You also aren't sharing that knowledge with the wider organization or also potentially taking part in, you know, center of excellence work or documenting everything getting that knowledge disseminated to the rest of the company. Then you're actually not the highest performing because actually you're still forming a silo and you should be looking to if you can modernize your process enough that you are a high performer. Then what's stopping the rest of your organization if if you're sharing with the rest of the organization and you not only as a team, but as a company are working at high performance and constantly reviewing wicked then hats off to you here's to you cheers. Oh, that's right.
Oh no, but don't silo yourself. Silos exist in every form silos around team. We agree, obviously, how do we break those eyes though what's the first step. So the first step I said well there's a couple of first steps because to adopt DevOps you need to adjust the way you work for organizational change for technology change process change, you know, I think we've probably said it to death right but people process tooling.
The combination of these three things means that we're working in a more DevOps style fashion is right we're working towards this DevOps approach. And the first thing is to just get everyone's mindset there right so we're on the bronze level here we're talking about that what what puts you on that bronze podium stands, and realistically that all starts with the beginnings of a mindset change taking people who perhaps historically have thought yeah we'll write some scripts and we'll hand them over to the DBA and now getting them to think a bit more like hey, maybe we should have some kind of object level history some kind of version of what we're doing. Version control on the application side our C sharp files are Java files whatever. It's almost unthinkable that we wouldn't put that into some kind of version control even if that was like subversion or team foundation version control not even get but some kind of historical version control so that we have revisions of our work.
And crucially like version control is, you know, and it's hard a way of sharing data amongst teams right breaking those photos. Exactly so if you're all working, you know, a lot of people still work on these kind of large monolithic databases that are 20 to 25 years old, and they're basically spaghetti right you've got stored procedures reference in another store procedure in another day. And then you're like, oh, this is this is an absolute nightmare. But by starting to get things into version control, you start giving people this kind of visibility into what other teams are doing and instead of having five teams working on the same database and trying not to step on each other's toes by getting it into version control.
You can see exactly who is making what change when and why and it really does become that kind of source of truth. Yeah, makes sense. Okay. I was going to I was going to counter with a question, actually.
I did also one thing, but I'm on a little spaghetti. I really like spaghetti. This is a complete aside, but when people say spaghetti code, that's like one of my favorite foods. Spaghetti is also one of my favorite foods.
As long as it's whole week spaghetti because I need need me that fiber, bro. Do you. Well, no, as a vegan, I generally do quite well for fiber, but whole week is still better for you, isn't it? None of those empty.
Don't get me wrong. Regular spaghetti. Oh, amazing. Sorry.
But I was going to say to you, obviously version control obviously version control is quite a new. Subject for a lot of developers and let alone putting the database into version control and if you go back, anyone who's listening, if you go back and listen to when Chris and I talked about state versus migrations versus this kind of hybrid approach of version control. I think it was literally like second or third episode we ever did on DBA source control how and why I think, you know, putting that aside. Let's say that we decide as a team, we are going to go from wooden spoon to bronze.
Yeah. And we're going to start by looking to put the database into source control. What would you first recommend we look into not putting the database into source control, but what kind of things should we start looking at. As in like you're working on a new project and you want to get like we're database developers and we have never used version control before.
That's an interesting idea. There's a lot of things that kind of come to mind. I guess based practice and documentation could be right in there as long as it's not captured in word. Like text files generally like that's what version control is built for.
So if you've got text files for documentation, it's a really easy thing to capture in there, and especially if you go to describe what goes in there. You know, you know, document your stuff first before you put it in there. And then of course the app code is going to be the easy one to put in the database code, which is before the database code. But don't know anyone's or you can't version of database.
Oh, you absolutely can 100%. And I would just say like looking into version control commands, just getting used to it. You know, I've worked with a number of customers who. When I was introduced this kind of idea to them of, Hey, you can put your database in a repository, you can put it under Git.
And they go, well, how does Git work. And that's the point of which you need to start breaking it down and saying, Okay, you've got branches on these branches, you can create a pull request that then merges it back into the main code base. And then the main commands are like, get pull, get push, commit, get add, you know, get in it, get rebase all these sorts of things right. Or you can rename those as well.
Right. So you can you can rename your get push to get yeet if you would like so every time you're finished with your code, you can eat it to your remote. But enough about that. The important thing to bear in mind is that you should before trying to put a database under version control, you should get familiar with that version control system, because otherwise you will find yourselves in a pickle.
You know, you might try and create a branch of an existing branch with some source code on it and not know what the heck is going on, or conversely, you might get your database under version control on your trunk. And, and then just work. Well, just stick to trunk based development when there are a lot of other really useful methodologies out there like get flow and get help flow. So, so we've got all our stuff in version control, everything funky dory.
What's our next step Chris, how do we how do we go from Francis silver. Interestingly, silver is probably the probably one of the easiest steps to achieve once you're at bronze it's in that gold that's going to be the hardest but I'll leave that for you to go over. I'll take the easy one as always. So silver interestingly is, is a kind of a combination of three things number one is this kind of continuous delivery on the application side.
You've got your again your C sharp code your Java code front end code whatever in version control you're building it you're deploying it that's all fine okay you've got full automation there. And what we're now looking for instead of, you know, instead of bronze which is kind of exploring the realms of version control silver becomes this kind of looking for parity and silver is very much okay. The front and devs they know what they're doing they're building the deploying. Now we need to start looking into is it possible to build the database code as well is it possible to somehow take all of our scripts whether they be state scripts declarative scripts in version control.
All migration scripts, and is there any way for us to effectively build the database to kind of replicate this bottom up deployment method of can we take the database and deploy it a fresh if need be from version control for onboarding new clients for instance. And again, this is kind of the stage at which continuous integration takes over, which is anytime we directly affect our master our main our trunk whatever. And we merge code into it or we commit and push directly to it which you shouldn't do of course we use branches, but whenever it picks up behavior on that branch on that main branch once we merge back in that then triggers an automated continuous integration build to validate that all of our code works together as a team or as teams. And by building it from the ground up you get that idea as to whether or not you can still build from nothing you can still take a nothing database and then have everything in terms of schema and static data for instance.
And then you know zero to hero. And I have a hark you think so I'm doing my thing. Thank you. Oh yeah.
That's my soul. Was on a roll. No, anyway. Keep going Chris let's get this flaked up.
Yeah, exactly and all of a sudden DVR gets taken down because we're claimed by Disney. It's fine. It's fine. But the point is this is the this is the bronze is the stage that takes probably the most getting to right I mean I talked about version control and a mindset change getting things into version control is probably surprisingly the biggest jump of the three.
And fair enough, you know there's very little usually on the metal tables between bronze silver and gold they normally within hundreds or tenths of a second of each other. But it's everyone else below them that's lagging behind. And I think that's important to bear in mind is that it's hardest to get to bronze and then you've just got that little extra push to get to silver or gold. And with silver you have that mental change you have that internal culture kind of in transformation people are adopting these best practices people are speaking forming these centers of excellence and understanding really what good devox practices means we're adopting agile and sprints and I'd say this can't make the one thing you said just now is that like silver is probably like the easiest one to get to what's your other bronze level.
And I agree and I personally say that's probably because it's can mostly be achieved purely through adopting technology. Like you can get to a CI step by just plugging all the bits together and you're at silver, right? That's true. That's absolutely true.
And it doesn't really impact things if you don't want it to. Like you could just be running these bills in the black room and the black box and it never tells anything where you've had a success or not. And thankfully you've achieved silver but have you really changed anything. And this is why I'd say that the gold is the hard one to get to is yes, it is fundamentally the same technology that you're just extending it.
But the hard step, the leap of faith, the like the that that moment that light bulb moment is having the trust the faith and the culture within the company to deploy automatically downstream the whole way. Without there being excessive annual checks releasing those money checks. Yeah, specifically we're moving on to gold here and to be fair gold in this sense is as you already talked about it's it's CD, but realistically what we mean by CD isn't just continuous deployment right we can't all be Facebook we can't all be Microsoft we can't all be. You know pumping everything directly from version control all the way to prod just because we trust our automated tests so continuous delivery continuous deployment we talked about before.
You know what are the kind of changes that do need to happen for us to to move to gold from silver what kind of feedback does any to be in place for us to know to have the confidence to achieve gold. As said to me I think it's all about trust like you say that we can't all be Facebook but I don't know a lot of companies can there are obviously exceptions to this but you know we can deliver completely seamlessly. We have to know and understand that actually that is better is that trust for me is knowing that you can trust with others not to put out something poor, rather than putting out serious assistance and checks in place to. To catch anything rubbish that might come out.
Trust developers didn't know that they know what they're doing and put out good stuff and that's a hard one that's a very hard one but trust is crucial trust is like the main thing when it comes to building a team and DevOps fundamentally like said is about breaking silos is about building one big team Dev and ops. Do you know what was said to me recently on a webinar that I did with with one of our partners out of the UAE we were talking his name's D. And he's absolutely phenomenal and oh my gosh the best voice ever just if just go back and find the webinar, go on my LinkedIn go on the red gate events page and just go and find go and find this webinar with me and D. Pack talking about transformation by DevOps but DevOps, the D.
Pack basically said that DevOps and this is where I think it's going to be really relevant to the gold medal. He said it literally said the phrase DevOps is empathy. And that that really hit me right in there. You know DevOps is empathy DevOps is about understanding and it's about sharing about breaking things down and it's about communication and knowing how to help solve situations help you know how to achieve your goals as a business, whilst making sure that you've got this constant feedback constant understanding constant you know communication and about having that empathy because at the end of the day everyone who's doing DevOps and organization is a person.
Right, we use scripts to automate everything we use terraform and Kubernetes and we use it as your DevOps and GitHub and GitHub actions and we use SQL Server Oracle Postgres whatever don't really matter because at the end of the day it all starts with a developer making a change. So yeah for people tuning in and they're like how do we get to amazing DevOps and the answers you've got is empathy and trust. I can feel some eyes rolling. Oh no.
But yeah I mean it is about that like it's about getting everyone's buy into implement these systems and actually use them rather than you know just doing a checkbox exercise to get in place. Exactly and you know even gold performers you know we can be more prescriptive and we can say hey you should be using like cloud based technologies you should be utilizing platform as a service where possible or you know moving to cloud based technologies you should be utilizing platform as a service where possible or you know moving to containerization and you know breaking that link between the operating system and your in your database and your application code etc and we can tell you all of that but I tell you what there are people adopting those newer technologies who don't have the right mindset who don't sorry not the right mindset but who don't have the mindset of empathy of trust of automated testing of you know understanding the issues and gathering feedback as early as possible. They're on the cusp they're on this kind of wave of technology, which is fantastic, but if you don't have that mindset if you don't follow some of those principles. You know if you end up like what's his name is it.
Is it Clint or something in the Phoenix project what's his name. Oh, I'm Jimmy the single point of failure. Keeps getting called from project to project that's really annoying I've had a complete mind blank on that. You're going to Google it right okay.
So if you haven't already go read the Phoenix project because honestly it's one of my absolute favorite books and the sequels are not bad as well you've got breath and but Brent of course it is yes. We're similarly named to our beloved Brent Ozar as well but Brent the single point of failure the person who is drafted into fix everything else you know, even if Brent is working with, like I say, terraform Kubernetes like infrastructure as code working with machine learning and artificial intelligence is not a quantum computing. It really doesn't matter if you don't follow the right principles the right kind of methodologies which ultimately mean that you're able to capture feedback quickly and efficiently and then act on that feedback. If you're still handing scripts up to production any matter of things can go wrong there is no governance there.
And ultimately you're putting yourself and or process more at risk by doing that. DevOps means just good people with good mindsets good process and good tooling. Yeah, all those white hats. Exactly.
And you know that ultimately leads to your gold medal but again like we said at the very beginning. It doesn't matter if you're a gold medal winner doesn't matter if you're the highest performing in the world. If you don't keep on it if you don't keep gathering that feedback and responding to it. You'll end up in silver then you'll end up in bronze and then you'll end up with your wooden spoon.
Oh yeah. All right then so that's how to get to gold you heard it here first. One ex Chris. Next my beer is gone unfortunately.
And fortunately from the previous session I was not able to eat beforehand sets. It's going well I would say it's going I'm strong starts right I'm a very strong. Exactly. Not something we joke about but at least I'm what's the word.
High functioning they go. Let's go with high functioning theoretic at least medium functioning functioning. But it's time for. Right.
The news. The news. Stop. The news.
All right it's time for the news Chris what's the news. So there's a small event that happened in Japan recently that you might have heard of it's called the. Ollie and pikes. So yeah loads of people decided on.
Oops. I mean lots of Japanese people went to Tokyo. Well a few people did there was some I thought there was some crowds. Small crowds.
Small crowds. So yeah we had a big event in Japan and another big event in Japan that is going on going at time of recording. So yeah the these kind of events they roll around every few years and they tend to attract a lot of cyber related crime. Every four years Chris that's how the Olympics works every four years already so it was last Olympics then Chris.
This was the Tokyo 2020 Olympics Chris. Here's it now Chris. 2021 Chris. So the last Olympics was how long ago Chris.
Five years. It doesn't count. I do love the winter Olympics actually I really love curling. Really love curling.
I just I get behind it. I see that little I see the hammer is it they call it hammer I think or something. They throw the disc the big old chunky thing and it goes up the ice and they're brushing away and I'm just like oh my gosh. Who created this sport anyway.
It's a big focus of cyber crime because people suck and obviously it's going to be a big focus there's been reports of all kinds of weird and wonderful things come out from this so simple fishing a lot of you know fake giveaways essentially click this button and we'll give you this competition prize for TV and obviously it's completely fake as a website called Olympic tickets 2020.com there was used by Scammers to sell fake tickets. Wow. Yeah we had a malicious PDF that was being sent around including something called a wiper which essentially just deleted a whole load of stuff that was on that user's system which obviously sucks. There was a data sharing tool from Fujitsu that compromised a whole bunch of organizations as well but the one I want to go into in a little bit of detail is well the one in which a bunch of ticket holders or those looking to volunteer for the event unfortunately had some of their data leads.
So apparently not many the number given the exact number was not large which is always very very useful but essentially the portal information was leaked which meant that Santa's could use that information to log into the portal and from there get a load of sensitive information further. So yeah Olympics ideal ideal in lacking security. Oh yes. But yeah apparently this happens every single Olympics and there was actually a team of white hats that was hired by the Japanese government specifically to try and dig out as much of these as possible before the event obviously not hugely successful but you know I guess you never will be ready.
You can only do as much as you can. Second piece I've used I've got is I've run a report on the cost of a data breach and what they found is that a data breach has grown in dollar impact cost kind of makes sense you know inflation and all that and each incident how much you think each incident is going to be costing each company that it's on average. Incorrect the answer I'm looking for is 4.24 million US dollars. Oh I was going to close though.
Yeah but you were doing it in pounds I guess I guess so. Yeah exactly. So 4.24 million dollars per day to breach which is crazy like one slip up on an IT operation scene plus 4 million dollars. So surely it's worth.
It's not always IT ops remember we talked about we talked about this we talked about a hospital that throughout all of its printers and it had the documents on the hard drives and they were in landfill and that was a breach that's not an IT security slip up that's just a week throughout our old hardware but. I mean technically it is an IT ops slip up. The point is very true but you know they could ultimately be a user failure it could be a developer for those operations but yeah 4.24 million dollars is a big mistake that's it from the news from me how about you Chris. Well I don't have any news specifically but I do have a list of events that are going to be taking place there are a couple in the calendar in the calendar that I got in front of me I'm going to go to the next page.
And there are more as well. There are a couple of data Saturdays coming up Saturday 15 and 14. Plovdiv and Oslo respectively Bulgaria and Norway up there on the chart so Plovdiv is August 28 I think as I mentioned last time Oslo is September the fourth. Also you've got data Saturdays Croatia as well September the 11th and data Saturday Sophia October 9th again Bulgaria look at you on the data Saturdays I like it.
But there are there are also a couple of things I should mention data platform virtual summit I mentioned last time as well but if you're not already attending the data platform virtual summit please do go over and get registered for that because it's going to be an absolutely fantastic event I've already seen some of the speakers and really it's just going to be blown out of the park. The one I really should definitely mention though because the registrations open for it this week no less. Well I think in the last week is the past data community summit 2021 so if you go to pass. If you go to pass.
I'm a big fan of the past 2021. Do you know why? Because it's in 2021. No because one of my good friends is going to be speaking there.
Is it Grant Fritchey? No, go for good. Is it me? Yeah.
Yeah. Yeah. Yes that's right shamelessly I will also be speaking at the past data community summit so if you go to pass data community summit. com or just Google pass data community summit you will find the page is hosted by Redgate with a premier sponsor of Microsoft there are also additional sponsors for pass as well it is a community event.
We want to bring everyone together and we want to make sure that everyone has the opportunity to speak about topics that matter to them. And actually there are a whole bunch of sessions taking place across a whole host of different learning pathways and that includes pre conference sessions half day sessions general sessions and lightning talks. In fact, there are just over 212 sessions across the 8th to the 12th of November. And guess what Chris what it's free.
What do you speak about? I'm going to be so I'm going to be speaking about putting in place and end to end deployment pipeline with a sequel database as your DevOps and flyway DB so I'm going to be using flyway community edition to put in place a free DevOps pipeline for my dev test and prod as your sequel databases and I'll be using the flyway docker image in my yaml to do that. Nice. Nice indeed.
So yes, do get yourself across the past 80 community summit.com and take a look at some of those sessions and hopefully we will see you there, but that is all from me for the events rundown. I think that all that's left for us to say is of course number one, congratulations to everyone who's been competing in the Olympics and in the Paralympics obviously normally we would have a theme like a silly day or something like that, but I think it's all just worthwhile as giving a clap out to those hard friends who have strived to be the best of the best of the best. And I think that's something that we can all take under our take take into our own learnings. I can figure it on that.
Oh yeah. Oh yeah. But for now Chris thank you so much as always and thank you everyone at home for or in the car or wherever you are listening to us. Thank you for joining us.
It is always an absolute pleasure and we look forward to seeing you for the three year DBL anniversary next time that of course DBL 36 but for now. Cheers. Cheers.