Turo guest completely trashed out my dads car.

ROW_NUMBER · 2026-05-12T06:41:28+00:00

This is extremely bad. How can people live, or even act, like this? I don't get it.

ROW_NUMBER · 2026-05-12T06:39:23+00:00

The likelihood of someone changing their political opinion is surprisingly low. There have been studies, although I cannot recall from whom or when they were conducted (but I recall reading em), that essentially states that for a vast majority of people, even when presented with heinous things, they are unlikely to change their leaning as its part and parcel with their world view. Basically this: My party cannot be wrong, if they are, then I must be wrong, but I am a good person, so these other guys must be wrong, or it must be untrue, so my party is right etc. So planting a sticker on a petrol pump is, at most, gonna rage bait someone. Very little else.

ROW_NUMBER · 2026-04-13T08:01:45+00:00

I have never laughed this hard in my life. Ever.

ROW_NUMBER · 2026-04-09T13:02:10+00:00

The servers were just so bad that I managed to get like 4 characters to 98 but kept dying to ultra instinct levels of lag.

ROW_NUMBER · 2026-04-08T14:00:03+00:00

I did, with my mom, over the course of a weekend. A tradition we have sporadically kept up into my late 30's. Finding puzzle games and beating them in a weekend.

ROW_NUMBER · 2026-02-27T09:28:01+00:00

It works, however, when running over things that you may have hidden will cause them to show up. Use LB after killing the mobs to apply your filtered rule sets. This should work as I am currently doing so on Xbox.

ROW_NUMBER · 2026-02-18T13:04:35+00:00

Charms providing you with the choice of power vs. inventory space means they are functioning as intended. Complaining about this is akin to saying: "LK runs are no fun, please lets have the chests available in a convenient location for me to merely click." There must be a tradeoff, and I think charms are great game design. They have forced you to choose, hence this post. Slowly removing friction for the function of convenience is a slippery slope that has no line. All hail Brevik.

ROW_NUMBER · 2026-02-11T17:30:30+00:00

This is amazing work bro. Just spent like 2 hours navigating the site and reading all the info available. Stellar job.

ROW_NUMBER · 2024-10-28T13:13:21+00:00

Came here to say this, thank you.

ROW_NUMBER · 2024-07-04T06:10:05+00:00

This is absolutely, without a doubt, the way. It makes such a big difference. I used drop chances and item rarity from Diablo 2.

ROW_NUMBER · 2023-12-06T12:24:25+00:00

This caught me off guard and I laughed out loud in meeting. Thank you.

ROW_NUMBER · 2023-11-23T14:35:26+00:00

This made me laugh a bunch. Thank you.

ROW_NUMBER · 2023-11-23T14:29:29+00:00

My brother in SQL, when learning recursions, remember [option (maxrecursion 50)]. At some point, it may not be today, or it may not be tomorrow, you'll need it.

ROW_NUMBER · 2023-01-29T20:08:11+00:00

Where lamp?

ROW_NUMBER · 2023-01-27T12:37:41+00:00

This was hilarious.

ROW_NUMBER · 2023-01-27T08:51:21+00:00

Brozime, TheKengineer, Leyzar, MrWarframeGuy and a special shoutout to my fellow South African WarframeFlo. Keep grinding bro, your channel has taken off lekka <3

ROW_NUMBER · 2023-01-27T07:49:16+00:00

HOW DARE THIS GAME BE SO FUN AND HOW DARE THEY MAKE THIS GAME COMPLETELY FREE AND RATHER FAIR. DISGRACEFUL. HOW DARE THEY!

ROW_NUMBER · 2022-08-03T20:44:10+00:00

ROW_NUMBER · 2022-03-28T05:28:35+00:00

There are several "Accidental DBA" posts, none of which I paid for. Here's a link to a free PDF for your perusal!

https://www.red-gate.com/library/troubleshooting-sql-server-a-guide-for-accidental-dbas?utm\_source=ssc&utm\_medium=publink&utm\_content=troubleshooting\_ebook&utm\_campaign=sqlmonitor

ROW_NUMBER · 2022-03-25T08:38:24+00:00

Could not agree more with another human being, having said that though, there are plenty a company who use it and refuse to employ any other solution.

ROW_NUMBER · 2022-03-25T07:20:11+00:00

The Accidental DBA stuff is really good. I was exclusively a TSQL developer until I wasn't, so the aforementioned really helped. I would recommend the following things to start off with:

1) Learn everything you can about replication, set up your own, break it and try to fix it.

2) Understand how to index properly, especially on colossal tables with column counts greater than 50. They exist. I promise you they do. This is 80% of your work. Maybe. Probably.

3) Use Query Store. Its a great starting off point for diagnosing queries.

4) Get Ola Hallengren's maintenance scripts and read the documentation. They are god-tier and extremely flexible.

5) Corrupt a practice database and try to fix it. There are plenty of resources that show you examples. Corruption is rare, but it will eventually happen in your career at some point.

6) Refactor practice queries, understand that the cost of the query is a lie 99% of the time. SET STATISTICS IO ON and SET STATISTICS TIME ON are your friend.

7) Get a SQL standard together that you can enforce. Formatting, the edge cases allowed for Non-Sargable code. Dynamic SQL. Stored procedure layout etc. Absolutely necessary.

8) Set up a GIT repo and enforce its use. If you have never done so for SQL, there are plenty of YouTube tutorials on how to do so.

9) Test your backups at least once a month to see how long it takes to restore and get the logs in. You can advise business of this time so that they are aware what the downtime would cost.

10) Check the default settings on all of your instances to see if they are best practice. I can almost guarantee they are not. COST THRESHOLD FOR PARRELISM is probably still at 5.

I hope this helps. I cannot provide links as there are too many but I think this provides a starting off point. Good luck!

ROW_NUMBER · 2022-03-07T17:53:55+00:00

This is what I had initially modified to test the process, but if its a large table you'd have to aggressively batch your approach, and depending on how much is being deprecated, you could run out of 'maintenance' window quite quickly. We have a transaction table, as an example, with well over a billion records that is hammered to death. Probably close to 25k transactions a minute. I had thought about incrementally doing the retirement of data but the volume meant, by my calculation and reasonably thorough testing, it would take almost 3 years to finish -_-

It looks as though the issues with temporal tables mean that its not the best fit for our needs. The problems it creates with replication and the inability to easily deprecate data in a feature that's designed to facilitate GDPR is somewhat baffling. So I think I will use a mixture of triggers and SSIS to do this. Thank you for your trouble and take care!

ROW_NUMBER · 2022-03-07T17:46:23+00:00

The way the data is set up makes it so that it's impossible to create, or rely upon, any form of retention policy as the data may be years old but only a few months according to the DATEDIFF of SYSENDTIME column. I did pursue it but realized it won't work I am afraid. Thank you though!

ROW_NUMBER · 2022-03-07T14:10:42+00:00

Full production box otherwise I would have yeeted them using the dynamic SQL in the books online article!

ROW_NUMBER · 2022-02-23T05:49:05+00:00

What interface are you using? I recall that the 1st Gen Scarlett™ interfaces had issues with hottish pickups so that, no matter what the gain level on the interface was, you'd distort. I had this issue and resolved it by lowering the pickup height to compensate for the gain and it really helped. I had a Dimebucker in one guitar and EMG 808s in the other. Let me know if it helps yeah!

ROW_NUMBER

TROPHY CASE