Hello there everyone. Hang on a second. I was realized that I'm using a different microphone. How absurd.
Welcome. Welcome to the worst quality of voice, Chris, DBAL episode, spectacular stupendous. Yay. No, but seriously, welcome one and all to Redgate DB.
Hey, oh, yeah, yeah, that is of course a nice warbling from myself, Chris. And me, as well. Hello, as well, bring me a cup of tea. No.
Okay, fair enough. Well, that is it. Obviously, no guests or anything today. You're back to regular programming.
Thank you. The original, the Madagascar vanilla bean vanilla ice cream. Perfect. As it is, don't change it.
DBAL. And of course, today, we are Madagascar Vanilla. Oh, because it's lush. It's the best vanilla.
What is it? Yeah, I feel like someone just felt the need to insert magic. I guess. Trying to say to me in a blind taste test, you could tell between a vanilla pod and a Madagascar vanilla pod.
Pass. No, perhaps not. However, we are pretty absurd concept, wouldn't you say? And of course, today on DBAL, we are celebrating something that comes around only once a year, quite unfortunately.
And that is National absurdity day. That is the 20th of ever actually. So it'll be a day before we release, but still you may as well celebrate it, celebrate it as absurd. And we can pass up on the opportunity to celebrate the absurd.
So today we're going to be talking about the absurd or unbelievable things people still do in 2021, when it comes to database development, pipelines, specifically. Pass up on a click that headline is that one? Absolutely. Can't pass it up.
Not even one Iota. And of course, we're going to be talking also about the news, an amazing webinar actually that just came out that we both highly recommend. And of course, we'll be giving you the regular rundown of the events digest. And if there are any red gate events, not I think there are.
Chris, you ready to get weird? Always. Always. Get weird.
So with that in mind, what is your absurd drink for this episode of DBL? So I went with the most standard vanilla thing I possibly could in an everyday context, the most absurd thing I possibly could find in a DBL drinking context, which is a bottle of water. Oh, dear. Great.
Keep branding as well. Way to let the team down there, Chris. Absurdity. It is absurd.
But still, you know, it's absurd to not be drinking beer. So you're on the water. I get it. I get it.
I went entirely the other way. I'm not surprised. You would never pass up the opportunity to drink. I proper Marie Antoinette in this.
So I have actually black label Lancelot champagne. What? Oh, why did I do this? But yeah, I'm getting stuck in.
So I have a presence as you pass them by. So yeah, so it turns out that Lancelot champagne turns out that all of their champagne are vegan. They don't use eyes and glass or milk powder for clearing as clearing agents or whatever they call them, coagulants or something. And I went into my local weight rows.
Other good supermarkets are available for anyone out there who isn't from the UK. Weight rows is kind of is one of the posher people shops, but it certainly isn't up there with MS and Harrods anyway. So I'm going to get this one open. Hang on.
I mean, there are many people who actually do their groceries at Harrods. I think there are some. There are some. They're probably some.
Anyway, I'm going to get this open. Hang on. I can't imagine like Harrods equivalent of, I don't know, like a basics range. Harrods basics.
Harrods basics. Other good department stores are available. That's a proper class of champagne. What a way to finish a Thursday.
Unfortunately, the virtual background is kind of messing with that. Oh, there we go. Cheers, Chris. Cheers.
Oh, that's a good champagne. I'm very happy with that. What a DBL. Kind of weird that we didn't have like a pop off.
I usually have the opening of the beer, don't we? I opened the bottle. I guess. It would have been nice if I had a cork, but then I'd have had to buy a full on 700 mill bottle.
And I would have fallen over honestly. I would have made it to the end of DBL like Chris. Chris, it's time for the news. Also, wow, would have been a luxury and purchase.
That's true, actually. I can't remember how much this little bottle was because I'm boujee in middle class that way. But it definitely wasn't the cheapest little bottle of wine they had. But it's tasty.
And it's absurd. It's absurdly delicious. The first day of afternoon change places. Anyway, I had to get an Alice in Wonderland reference in that.
As you're passing by through the... I don't know. I'll go for the second. No.
Indeed. The passage of words. Never going to make it. Never going to get out.
Excellent. Can you tell what we're doing yet? I'm sure you won't. But maybe some of you will.
Indeed. Some will be griseled. Oh, gosh. That's so good.
Welcome to today's episode of Chris Drinking Champagne. Today we've got Lance on next week. Hopefully, Moé. Ooh.
If there be. Moé for Christmas. Moé for Christmas. Moé!
Moé. Moé. Moé. Anyway, we should move on to the...
What was that? The meat of the episode? The soy meat of the episode. Yes.
Absolutely. Yes, indeed. But of course, we're talking about the absurd. And hopefully anyone who's listening to this episode is already sat there thinking...
Why am I listening to this episode? It's quite absurd. Wait, Rose. What is this magical place you speak of?
Anyway. Ooh, quick. Quick map absurd. anecdote.
Oh, yeah. So I was playing chess the other day. And I actually got to use an on-passant move. When do you ever play chess?
Ah, basically never. So do do do do do do. I never pass up again a solution. I love Sudoku.
Absolutely. Also, my favourite mathematical object is a Pascal's triangle. Anyway. That doesn't even have two S's in it.
Because of it. It's a Pascal's triangle. It could have two S's. Chris.
Anyway, the main subject is of course the absurd things people still do in 2021. So we're talking all things based development here. And you would have heard a spang on about some of these best practices before. But given the webinar that we're going to recommend at the end of this episode, and I absolutely would recommend you go and check it out because it's going to be absolutely fantastic.
Oh, it is absolutely fantastic. It was recorded. And you can watch it. So it's of course the absurd practices when it comes to things like monitoring, database provisioning, deploying database changes.
And actually I'm going to kick us off with one of my favourites to talk about. And that's actually manual processes. Now when I say manual processes, the thing is a lot of people when we say manual processes, the first thing that they think of is that effectively they've got to, you almost imagine kind of cave people kind of hacking away a T-SQL script or a PL-SQL script on a stone tablet and then passing it along to like a stone-aged DBA. But the important thing to bear in mind is that you can automate parts of the process and still have it riddled with manual processes that ultimately just undermine the nature of the pipeline itself.
So effectively, even if you've got an amazing continuous integration process, if part of that process is to spit out the build, the build artifact, then you can put it across onto a USB pen and then mail it to someone. Well, and that's a bit far fetched except probably for the military. And I'm sure that probably gets done at some point or another. But that is still manual and it's still a massive rake in the process.
When we talk about true database DevOps, true kind of synergy of pipeline and smoothness of delivery, minimizing time to market, we mean committing a change and then everything in the middle kind of just happening, just making good sense and then being deployed up street. And the important thing is that we don't introduce lots of manual error. However, this is where it gets absurd is that people build smooth, beautiful, creamy DevOps pipelines. Smooth, beautiful, creamy.
I've tried to describe a play of pasta. Of what? Pasta. Oh, no.
I might have some pastries after that. Anyway, pass out with this, right? Anyway, so yeah, you've got this smooth, wonderful DevOps pipeline. I'm trying to describe things as basically like food because it feels absurd to me, but it's also got the downside of making the hungry.
So if anyone's listening, like a really, really nice play of like, smokey, like, so fast about mushrooms spaghetti with like a nice, creamy, like salty, peppery, herby sauce. Anyway, now I'm plenty hungry enough and hopefully the listeners are as well. People build these pipelines. The absurd week is great for us because we go off on tangents.
So I know, right? It just comes naturally. It's just like say whatever the hell we want. Exactly.
It's like, it's like tennis, but the whole world is our tennis course. Exactly. You can't say whatever it's gone. Pass it to me.
I'll say the next crazy thing. So the, yeah, so they set up these pipelines and then they riddle them with so much manual intervention. You just couldn't even believe. Yes, we're up to one click deployments.
How many clicks does it take to get to prod from Dev? Well, you've got to approve the pull request. Yeah. Then you've got to click the, then you've got to start the build because we want to build it set times, but we don't want to schedule it because we want to make sure the right people are around.
So then we click build and then we manually review the build and then we manually copy across the build artifacts or even if we don't, we then have to manually approve the deployment to integration and then we have to check the deployment to integration and then we've got to manually press next and then manually check the deployment report and then the thing is immediately once you introduce a lot of these manual processes, your pipeline is to more absurd, quite the absurdity. As far as a smooth passage goes, that is not something that I would describe as exactly. So the important thing to bear in mind is do you really need those manual interventions and have you democratized this process enough that it doesn't matter if an employee leaves or a new person who gets bigger, team gets smaller, team takes on different responsibilities. Anyone can handle these deployments, making it just an entirely smooth process.
Boom. Go on. I thought you were going to inject that. No, Chris, you're wrong.
It's clearly subject that you're passionate about. Anyway, moving swiftly. Speaking of Swift, actually, this is an interesting thing is that I did speak to someone. I did speak to Taylor Swift.
I did indeed speak to Taylor Swift. Taylor Swift recommends that you do database deployments in a way that enables you to have a nice lean pipeline to minimize waste. Amazing. It was one of the best ones I heard.
It was often knew about. Things you know. So who are you talking to, Chris? I was talking to a red date customer, Jake.
Finally that. And they were telling me that they had gone from deploying something like once a week to multiple times a day, just by keeping the pipeline small, smooth, incremental. Effectively, they swapped from a state-based methodology to a migration to first methodology. And they've seen great success from it because now, instead of having to do great hulking comparisons, they're just deploying small tiny alter alter statements.
And once it hits integration, that's it. You know, if it hits integration, then everything's worked successfully, the build, the deployment to integration, at that point, then what they do is just trigger the automated deployment upstream to prod because at the end of the day, they have this mentality that if it's made into integration, if it has deployed successfully to integration, there's no going back. So if it does work, deploy up to prod, if it gets to prod and breaks, release a fix, go through the process, don't make a hot fix. If it gets to integration and it's been deployed and it breaks, then you make a new change in dev to overwrite the top of that one, but to make sure that you are effectively caring for the problem that you've caused.
So you're effectively kind of caught bullying it so that yes, you will temporarily, within almost the same statement, release a change onto prod. But by the time it gets to prod, it's already been overwritten by the next change that came after it. Makes sense? Makes sense?
Make another pun. I know you want to. Oh, it's terrible. It's terrible.
That sounds like manual processes should be put out to pasture. This is true, as should you because your puns have become traipassé. With this one. Boom.
All right, all right. I've got another absurd thing, Chris, apart from leaving anything in your capable hands? Oh, so I have a much shorter one, but much more specific one, which is a single server agent shops, specifically manually logging in to validate that they've run successfully. You want the people still do that in 2021?
No, right. Well, there's a huge array of different wonderful ways you can check on these. You don't need to log into every box of manually validate. If you have like 50 servers, for example, you're looking after that's going to take a huge amount of time.
There's a lot of different ways you can handle this, you know, from the more complex or overarching, for example, if you had a monitoring solution, like SQL monitoring place, then that's covered. Or alternatively, Chris, I'm sure you know a variety of different ways to cover that through SQL script. Let me introduce you to my good friend, a PowerShell. PowerShell friend, friend PowerShell.
Hello, I'm PowerShell. I could do a variety of things. I had to pass you that one for sure. Thank you.
I appreciate that. And what we're on that note, another very similar one is supply of dinner and management. There is still a lot of people who have a lot of very sophisticated ways to do itinerary management. A lot of very sophisticated ways that might seem kind of crazy if you take them out of their, I don't know, context or the original zone or, I don't know, if someone else were to talk you through it, I think you think about that.
The best one I've ever seen is like an Excel file that was like the mother of all Excel files. The back end of the UK's tracker trace process. Yeah, I mean, time and time again, right? But it was an Excel file that specifically, well, it was quite clever.
It captured all this stuff. But it was an Excel file. Oh, no, is that the exact thing? Did I get the example?
Yeah, I predicted the example. Anyway, sorry, continue. If you're using something like Excel for to capture itinerary, and literally what servers you have while you are once installed, I mean, that's a good process. If you've got 10 servers, it becomes an absurd process of your thousands.
It's true. It's just impossible. And then you get to the whole manual versus automation thing, right? So again, there are better ways.
Again, I'm sure, Chris, you could suggest many different ways through through script based methods or or this is something that we can do as a single monitor. Absolutely. One of my, I think, it's a taking aside. And normally, we leave a lot of the kind of aggregate product specific stuff until kind of late on in the episode.
Because what we want to do is bring you a nice kind of interesting podcast where we talk about things that we come across and problems that we come across and how we solve them and focus slightly less on the actual way. There's this other product. But one thing I will say is that SQL Monitor have just come out with their configuration comparison and you can pick up configuration drift over the past one, three, five or seven days. And the way that I like, I think, right, like how many people listening to this going to be like, I'm infuriated by my developers changing a setting on one of these servers.
The cost threshold for powers and has gone from five to 50. And this is the thing. This is interesting because, hey, this is what this is something you could something you could start identifying by looking at by looking at traditional metric based monitoring. So for instance, if you see a spike in your CX packet weights, then yeah, maybe someone has been fiddling around with your max stops.
I know I'm max stops. And that's fair, but it's still going to take a little while to get there to remote onto the server to check the configuration. But now in monitor, I just have to go to the page and look at the two look at the side by side of prod and staging or prod one prod two and go, ah, that ain't right. Time to change a setting or even just be alerted if someone changes it.
That's true. That's also a good one. So another absurd thing, Chris, go for it. As I just revolve around, this is no good for anyone who's listening, but I revolved around to almost absurdly indicate that we've moved on to the next thing.
I'm spinning. You spin him. You spin him again. You know it.
So the other thing that I find people do this absurd is that they have weak passwords and you're welcome. And the interesting thing is about passwords is that we've literally had an entire episode about passwords on DBL. Well, honestly, you would think that not everyone in all of the EU forced their children to listen to DBL before bed. I literally, my mum passed on by a few weeks ago and I was wondering about password managers.
You had no idea what it was about. Get a password manager, mum. Oh, I was shocked. I thought you were about to say she'd passed on, but I'm glad to hear you.
All right. I was like, phrasing was very good. It was phrasing. Yeah.
Absolutely not careful enough at the same time. But the, yeah, I keep saying to a number of my friends, you know, have you got password managers yet? No, comes the answer and you think, you're having a laugh. Do you use the same?
I asked one of my friends the other day. I said, do you have a password manager? And they said, no, what's a password manager? I told them.
And they went, that doesn't sound very secure to me. And then I explained the reasons why it's more secure and then you can have all the different passwords for different sites. And they went, oh, why would you need different passwords for the sites? I only have two passwords, one for serious stuff and one for not serious stuff.
When I found out that Facebook was one of their serious ones, that's when I went. No, that's it. I'm sorry, we're going to have to get your password manager now. We've changed some passwords.
So thank goodness. I spent an hour and a half with a friend changing passwords, but now they're nice and safe. And actually, to be fair, they've already told their friends and family out of message yesterday, say, Oh, I just got someone else using a password manager. Yes.
That's a win. Um, those are going with this. Yes, passwords. Don't use weak passwords and don't repeat passwords.
I read an article the other day, or absurdly, I'm almost tipping into news. Read an article is pretty absurd in and of itself. I did actually, as I sat here at my standing desk. I was standing desk.
I was scrolling through LinkedIn and I stumbled across an article, stumbled across an article of this person who had basically identified that a router, I think I remember whether it was the Dutch or Danish government. I promise I'm not getting those fixed up. If we have any Dutch or Danish listeners, I'm not getting them mixed up. I just remember that it was one of you.
But basically, I know that basically someone had hacked the government. I think it was the Dutch government, if I'm honest. Somebody hacked the didn't hack the government. Basically, what they did was they pinged up, I think, a bunch of routers and they identified that there were there were one or two routers that were still using like the admin base passwords, like they hadn't been changed when they were implemented.
Oh, dear. But it happens like when you're looking after a huge network of different switches and routers and you've got an immense amount of networking to do. And we've talked about this in the news in the past as well, you know, people getting routing tables wrong and it's always DNS, all of these sorts of problems. And they found that this router still had the admin password enabled and they said they basically let the government know the military know and basically the military called them back up and asked for their address and this person kind of went, oh, well, I was just trying to help and they were like, just give us your address.
So gave them the address and about a week later, we can half later, you know, what turned up in the post for this person who did the right thing. I'm hoping not a person to arrest them. A t-shirt arrived. Was on a t-shirt, Chris?
On the front of it was I hacked the Dutch government and all I got was this lousy t-shirt. I thought you would get that in the United States, would you? Or be cave for that matter? You know, or any other regime like similar, you know, you'd get someone knocking your door and say, you're coming with me, mate.
Or you'd get recruited by GCHQ. I hope. The carpet people press the car. Yes, the Fitment carpets.
Yes. Everyone likes me. I was sorry, like, this is another randomly of certain attention. Like an absurd attention.
So the old I. See, I see, I see. Chats posting board. Oh, yeah.
We go on that. No, so there's like this. There's a website that I can't remember the name of anymore. Wow.
And where people would post like their greatest hits and my old time favorite one of these is the person who has lost a device. It's in the same room as them somewhere. It's responding to ping. I just don't know where it is.
That's fantastic. Well, I was responding to ping. You kind of know that it exists. I actually I had a similar moment yesterday.
I was I was driving driving my wife home. We got out for a Christmas market spoiler alert, but my Christmas decorations up on Sunday. Thank goodness. It's mid November.
Anyway, yeah, that's that's a bit past. You kind of test. You kind of test though that my Christmas tree is looking absolutely beautiful. I would get a pass.
I'm assuming that's not a real Christmas tree. No, it is a factory, but it looks absolutely stunning. It just passes really well. It does.
It's a really good quality tree. But yeah, sorry, it was actually on offer 50% off. Compassed that up. So the yes, I will just say that.
Yeah, I was driving my wife home and actually I was thinking about old websites yesterday and I was thinking about a couple of the kind of early, early doors, kind of flash video, flash videos that you know, were all the rage in 2004, 2005, you know, literally just as drag or stay didn't take by ozone and the number guy. Oh, yes. became became famous. But all the time.
You're the inside. Well, I was thinking of the end of Z World. I don't know if you've seen it. It's a flash cartoon about the world blowing itself up, basically.
I just I love it because it always makes me think of the English because they're on a yacht playing shuffleboard or something and they just go about that time, H.S. Right. Oh, yeah, that's us. That's as long as this happened with Lance on black label.
We're good. This is going to become more and more absurd as Chris gets slowly more and more drunk. And I don't know what you're talking about. Exactly the same level of sober.
I mean, who was the person who got me a box load of beers for my birthday? I thought we were a passer. Why not? Indeed.
The second says just don't make sense anymore. I'm going to do one more before we move on to the news as well. Access Control. Oh, it's a difficult one.
A lot of people give developers and testers access to systems that they should not have access to. For a lot of people don't. But a lot of people do. And a lot of people forget to review access.
A lot of people move teams and retain access. Have you ever moved team? There's so many people out there who have moved teams for who still have access to things. The number of times I've spoken to friends who go, oh, well, I'm actually new team.
I don't do anything anything to do with that team now, but I still have access to the shared drive, the databases, the mailbox, all of these different things. You know, even now I have access to to see the even though it's nothing to do with me. I still have access to see some of the inbound mail that we get a red gate like income email from days gone by. And it's quite funny because access control is something that absolutely fundamentally needs to be reviewed regularly so that you can make sure that you're giving access to the right people to the right systems, because actually, all it takes is for one disgruntled employee on their way out or for you to have 20 accounts, some of which are semi inactive or inactive and potentially exploitable for someone to get into the system.
The fewer people who have access to production data, the better. And unfortunately, a lot of people just seem to be like, oh, yeah, we, you know, in case we need to make a hot fix, all 30 of our developers have access to prod. Excuse me. Yeah, now that's in my books.
That's absurd. I'm sure it's defensible for some people out there who have special use cases, but I'm at the honest. It's pretty absurd. That was a lot of pause.
I predicted that. I was dramatic effect. Yes. Before say something distinctly not very punchy.
I'm hoping that you just remove the pause entirely so I've seen a bit absurd. That was quite a pause with just me going. And I find that a bit of that. Because it gets mashed together.
One of those speed ups. It sounds like we have chip my voices amazing or slow down. So we have whale voices. Hey, baby.
Can you slow you down and speed me up? What that might be like people. So Chris, what do you think is absurd? Well, I think we're sitting there.
Any who I've got one more one more for me. It is using I was tempted to say any version control system isn't yet. But seeing that some people still have uses for some of those. What about my precious subversion?
Yeah, I'm going to specifically say version control system that are home route home route version control. So do you come across many of those? Yeah. Well, we do.
Only other cross- Well, you say that when I first started at Redgate, all those years ago, it's my six six year anniversary this year, this year month. Another time the earth has passed the sun. Exactly. Six years ago, when I first started talking to people, when I spoke to database developers in particular, they were often saying we don't even we don't source control our database code.
And if they were 50% of the time, they would say, well, even that 25% of the time, I was getting it. And then probably 35% of the time subversion. Oh, no, probably 40% team foundation server and then 30% subversion. Yeah, that sounds about right.
And then every now and then the curial. Be a fault. Yeah. Yeah.
Excuse me. You what? I thought who? Exactly.
I don't know. There's a lot of people who have said this already, like, is so provided these days, it's basically standard. Yeah. There isn't much reason to use anything else.
Yeah. Sure. Pretty upset. Right.
Well, you know what time it is, Chris? The new, the new, the new, the new, the new, the new, the new, the new, the new, the new, the new, we've missed our calling has just been saying the word the news to different songs from childhood. I feel like I needed the BBC news introduction done tonight on DBL news. Dun, Dun, Dun, Dun, Dun.
Oh, that's a good song. Does it. Pop has got a brand new pig bag? What?
It's not bad. I feel like that's Papa's got a brand new pig bag. How many of us? OK, we've lost Chris, we've lost Chris...
Hey, brand new pig bag. Come back to the real world. It's it is Papa's got a brand new pig bag. That's the song that you were humming.
What's it? OK. use. So, so, where do we want to start, Chris?
Well, I think the main, the main one that we want to cover today, I think we've got a couple of things. The main one I want to mention is, I talked about a webinar, the very beginning I mentioned a webinar that I think would be pretty cool if you went and watched it because it was super insightful. And that was actually, it was a, basically it was a, it was a webinar in conjunction with our good friend here at Medgate and also, I think it was Steve Jones who was on with him. Troy Hunt.
There's one person I know who'd recommend the password manager. Yeah, definitely Troy Hunt, absolutely. We've mentioned Troy a billion times on this show. Not yet been able to get him on, unfortunately, but, Salabig.
One day, one day. Troy's very, very busy, especially with, I think he's retained have I've been posted, anyway. So, there was a, there was a webinar on the Redgate events channel called, in conversation with Troy Hunt, security and compliance in database monitoring. And it discusses some of the best practices.
Might I say some of the absurdities in database monitoring and ensuring good security around, uh, database development, database monitoring. So, I would heavily recommend going and checking that one out. You can actually check that out just on the Redgate website. If you go to events, it'll be under webinars in conversation with Troy Hunt.
Troy's such a big name that I don't even need to tell you who he is, but I would highly recommend you go and watch that because it really highlights some of the, some of the things that you don't really think about when it comes to monitoring SQL Server. A lot of people are very metric based, very, how can I monitor my weights? But actually, in many cases, there's a bigger picture. And I think Troy kind of sums it up nicely.
I can't really, there's a few things I want to touch on that they spoke about. And I think that there's, you know, you know, there was a few key talking points from it, like reducing risks of data breaches by bringing security in earlier data is as much a liability as an asset and even kind of regulations are creating an impact, but there's no real industry baseline. So, there's a few really cool things in there to make sure that, you know, that you're following the best practices and sticking to some of those standards at an industry level. So definitely go on what's, I think it's a fantastic webinar and I can't recommend it highly enough.
Also, that's not even the absurd part, the absurd part was just how good it was. Just how fuzzy my head is now feeling after a bottle of champagne. Who would have guessed? The bubbles, the bubbles made absolutely.
Yeah, that's, that's it. Not the booze. So, data breach news. The big one we want to talk about this month was Robin Hood.
Robin Hood is an app that, you know, a lot of people have got into, I guess amateur trading, probably the best opening. Black bus to stock. Yeah, stock or crypto or whatever fights your boat. No crypto.
Your crypto choice. I hate all crypto. I think it's all not great for the environment, but for some specific ones, like she, let's go with she. That's a good one, except I don't believe you can trade at the moment.
But yeah, I also, yeah, can't buy a bit of silicon, say my life. All I want is like a handful of silicon. I just can't get any. It's terrible.
Anyway, they can. What I had for a second. They can't modify a lot, a lot this year for various reasons. If you remember the whole GME stock debacle, yeah, in the center of that one.
Also, a incident where I believe they're being sued for someone losing about $780,000, wow, due to a missed transaction by them. But very recently, they have been under scrutiny for a data breach. And it's one of those data breaches that is not through some clever technical manipulation, not through someone putting something where they shouldn't, but a simple case of social manipulation or cartistry. A social manipulator basically called up their support team and managed to get them to expose a total of five million customer records.
And the level of detail in there breaks down a little bit further. So there was five million customers of those. I think there's about 400 IP cards. And of those, there are 10 customers who have been exposed even further than that.
But apparently, apparently, no cell phone numbers, no social security numbers. The hacker who was responsible has now also in an exciting twist, puts this information out on the dark web sale and is after five figures for the data. Oh, is that a couple of dozen thousand? Yeah, I mean, well, it depends how you value that information, I guess.
Like a lot of it wasn't the most highly sensitive of information. Like social security numbers, that's the real highly grail, I think I believe that can get really valuable. But it's up for sale, if you want it. You're wondering what to do with your huge crypto earnings.
I don't have huge crypto earnings. I have about 30 quid in new kind of network, about 20 quid in ADA, about 10 quid in Doge and about five quid in Litecoin. So I'm not going to be the world's next rich crypto billionaire. Yeah, give it 20 years.
Yeah, give me a back to you, Chris. Well, on that subject, we've been using the word past, if you could tell. I mean, it would be quite subtle about it, I think. If you couldn't tell that we were using the word past literally the entire way through the episode, then you're okay.
But anyway, the absurdity is that past is over. Can you believe it? Past data community summit has finished and we've been building up to it. I see that a couple of speakers on that.
Yeah, well, you know, some of them are pretty intelligently pretty pretty. Oh, yeah, pretty nice. I can't think of them as someone who is on this podcast with me, but not me. Oh, Chris, I don't believe it.
Literally lives one person anyway. But yes, past is over. Can you believe it? It's it's absolutely.
Yeah, I couldn't believe it, but it went by so quickly. The good news is if you were registered for past data community summit, you'll find that the you'll still have access to all of the materials for the next few months. So if there was anything you missed or you want to take a bit of time to go back over anything, fortunately, you've got all the recordings and everything, all the keynotes and everything still on demand. And in fact, the keynotes are now available on YouTube as well.
So you can still catch the keynotes, the ones with in collaboration with Microsoft, Red Ozar, obviously all the big names. They just go ahead and have a look on the red game. In fact, I think it's on the past specific data community platform, YouTube channel where you will find a lot of this information. But if you missed it, I'm so sorry.
However, guess what? Pass will be returning next year. So get yourself over to the past data community website, get yourself signed up for them notifications. And who knows, you could just meet anyone from Redgate next year.
Let it pass you by. Don't let it pass you by. But yeah, definitely get yourself signed up. Get those notifications coming because this year was a dehousie and next year is promising already to be even better.
And we're looking forward to seeing them. Fantastic. In terms of events, though, obviously, pass is over. And there aren't really that many that made still to come.
In fact, there's a couple that are being advertised for 2022. So data Saturday Stockholm is already planned. There's also SQL Saturday Jacksonville in May 2022, Visual Studio Live from February to March 2022. And then there is still remaining one more conference that I can see that I can find in 2021 in December.
And that is Dev intersection Las Vegas. So if you feel like I go to Las Vegas, I don't know if they're actually making it a virtual event, they might well be. But if you're interested in attending Dev intersection Las Vegas, then you will find it on devintersection.com. And in fact, I can see the MGM brand Las Vegas workshops December 5th.
6th and 10th with a December 7th to 9th conference. So it's a SQL server and a CSEQO specific conference. So do feel free to go on there. Amazing.
If I just happened to be in Las Vegas, then maybe I will. A chance is a back, Chris. Slim, I'd say. I'm still verging on the absurd, perhaps.
One day, though. One day. Indeed. Anyway, Chris, look, we've rapidly gone out of time.
I can't even believe how quickly this time has gone. I can't believe how quickly that champagne went down. How's your water going? Still there.
Oh, well, as I was just saying, hydrated. In any case, Chris has been an absolute pleasure, as always, to speak to you. Thank you so much for taking the time. Not you, but thank you to the listeners for taking the time to listen to us.
We do, as always, really appreciate it. If you have any thoughts, any feedback or want to get in touch with either of us, again, remember you can contact us at dbaal.rrenhiving.com or you can contact me on Twitter because Chris never checks his Twitter. So for me, it's at plant-based SQL dot, well, at plant-based SQL or plant-based SQL dot com. I'm getting my website and my Twitter handle mixed up.
Plant-based SQL dot com for me. Anyway, for now, one more of said thought, G-cris. An episode thought to finish us off. Go on.
Yeah, round off a day. Imagine that we'd be recording this whole podcast and you hadn't hit record at the start. We'd just talking to each other for 55 minutes about random stuff. That would be quite absurd.
Fortunately, I did hit the record button. So, gentle listener, I leave you with this. And that, of course, is Cheers. Cheers.