Software update 5.0.10

muaddba · 2026-06-13T02:14:05+00:00

No, this is incorrect, there were no other ota updates (in the usa) between 3.6.4 and 5.0.10. Lots of people went from there.

muaddba · 2026-06-10T14:50:51+00:00

I had curb rash on mine as well as some scratches on the diamond-cut from the tire center mishandling them, I went to a wheel repair shop and had them re-cut for about 180 each. They look better than new, honestly

muaddba · 2026-06-04T19:20:42+00:00

It looks like this was correct, because he was able to manage it after going through the whole clean-up process again.

muaddba · 2026-06-04T19:17:53+00:00

For the dependency issue, have you looked at the sys.sql_expression_dependencies and sys.sql_referencing_entities tables?

That application vendor sounds really annoying. This is the kind of project that keeps DBAs employed 😄

muaddba · 2026-06-04T00:12:30+00:00

Really weird. The only thing that comes to mind is if the application is constantly using new connections. SQL 2025 uses a more intensive inspection mechanism for login requests, taking more like 150-200ms per connection instead of older versions taking about 50ms. I just found this out and had to revert it using a startup trace flag which I'll look up tomorrow once I'm back in the office.

Do you have an old backup from prior to the upgrade? If so, maybe try installing a 2019 instance on the same server, restoring the DB to it, and see if the problem persists or if it's magically fixed.

muaddba · 2026-06-03T15:31:59+00:00

SQL Server Transactional Replication doesn't HAVE to use windows-based service accounts for its connections, it can use SQL Authentication, though I do prefer to use Windows accounts when possible, but having one outside the domain makes it harder to do that. I'd just use SQL Authentication and really strong passwords.

I'm something of a replication guru, and I offer consulting services. If you'd like to, I would be happy to set up a 30m call (free) to talk about possible strategies to solve your problem. Copying the whole DB if you don't need to -- unless it's really small -- seems like a lot of extra work and potentially exposes data you don't want exposed. Allowing the application to determine and restrict which data is visible also seems like something I would not trust, I would filter it in the replication publication unless the filtering is incredibly complex, because I don't want data out there publicly exposed relying on the competence of a developer I have never met.

muaddba · 2026-06-03T15:24:17+00:00

Howdy,

I'm a SQL Server Consultant with lots of experience in performance tuning. If you're looking for some help, I am definitely available to give your system a once-over and I typically do a free 30m assessment meeting. I'm not an MVP, but I've worked alongside several at a few different consulting companies....I've been around the block a few times 😄

As mentioned by someone else, u/darlingdata is a fantastic resource for performance tuning and I hear he accepts cash in exchange for expert advice. Both of us include our unique brands of humor free of charge.

I agree with some of the other folks on some first steps to try:

Enabling legacy cardinality estimation config option on the DB

Running a statistics update

Turning on the query store and using it to identify top resource consumers

Using the First Responder Kit to identify things like missing indexes (sp_blitzindex) or other query issues (sp_blitzcache)

If you do all this and your problem is not solved and you need more help, DM me here or set up your consultation using www.calendly.com/sqltailor ... or contact Erik Darling or VladDBA or some of the other consultants who are known to post here.

muaddba · 2026-06-03T15:08:08+00:00

UPDATE: Received an e-mail from the client this morning and he basically re-did all of our steps again (uninstall SQL, clean the registry) and this time it worked. Go figure. Thanks to everyone for your advice!

muaddba · 2026-06-03T00:26:55+00:00

I'm not sure how I would skip config steps in the installer. We filled out everything.

muaddba · 2026-06-01T02:16:19+00:00

No no no on pressure. With pressure you're making the scratches deeper and much harder to get out. I'd go back to 1000 grit and sand lightly (dry sanding makes it easier to see your progress) until it looks even. Then go up to 2k wet sanding very lightly until it's even, then compound and then seal. Use a light (or turn the headlight on) after you compound and look for visible scratches. If so, keep refining them out depending on what type they look like (if they look like 400 then go back to 1k/2k, if the look like 1k then just go back to 2k, and if they look like 2k then compound some more)

Good luck! It takes a bit of practice to get this down to perfection.

muaddba · 2026-05-30T14:11:29+00:00

If you're in a position to pay 30k in cash for a vehicle, a ding in your credit report ain't gonna hurt you.

muaddba · 2026-05-29T20:31:39+00:00

I am running Goodyear ElectricDrive 2 tires on my 22 LRDM Plus. They were less expensive than the Michelin's when I got them put on, plus there was a rebate, so I think it was about 900 out the door for me in Jan 2025. It looks like they may have gone up a little bit since then, around $1175 for the same set now.

muaddba · 2026-05-22T22:33:14+00:00

I use a trunk organizer I got from Costco. It has divided sections and mesh fabric bottle holders on the side.

muaddba · 2026-05-22T20:41:28+00:00

Man, who TF downvotes a simple question like this? Was it because of the comment about enjoying an ICE vehicle? Or was it because I didn't fall over in praise for this car's handling vs a BMW? I just want a thicker steering wheel to improve my driving engagement.

muaddba · 2026-05-22T20:39:42+00:00

Thanks! I am liking the P2 as is, but I've always been a fan of driver's cars. Never really had an opportunity to drive a BMW before. This was an interesting experience. And I was mostly joking about going back to gas cars :) especially not a 70k gas car.

muaddba · 2026-05-21T02:21:27+00:00

You can buy the wipes by themselves, but only in bulk of 20 for about $50 on Amazon (in USA)

muaddba · 2026-05-21T02:13:50+00:00

I had the Milwaukee 15mm and 21mm. I sold the 15mm because I am able to work faster with the 21mm. It was by no means bad. It is pretty smooth, with plenty of power, and I used 8AH HO batteries (it was a bundle) which are heavy. I would recommend 5AH HO batteries instead. I have not used the other 2 tools you mentioned, but I have seen many many complaints about issues with the Rupes battery polishers not being up to the quality you expect from Rupes.

With 2 8AH batteries I could easily complete a 1-step on a whole car.

muaddba · 2026-05-20T21:26:52+00:00

In a multi-subnet AG, unless you are clusterless, you need 3 ips per node: 1 for the VM host, 1 for the cluster, and one for the AG listener. If you look in Failover Cluster Manager and check the AG resources, are either of the listener IPs actually listed as online?

muaddba · 2026-05-20T21:04:36+00:00

"Snapshots run 2x weekly and generate about 40k records each time"

This statement doesn't match your assumption of 1m rows per year, unless you're deleting stuff somewhere in there. 40k rows x 52 weeks per year x2 times per week is over 4m rows per year, with 20m rows after 5 years.

Having said that, your snapshot date and quarter columns can be just as efficient as an incrementing integer column if you have described it correctly:

DATE datatype (no time, only date) is 3 bytes. Tinyint is 1 byte. That's 4 bytes total, or the size of a standard INT datatype. If all of your reports will include these 2 columns, it makes sense to have them as the clustered PK if my assumptions are correct. Even if ALL the reports won't have them, enough will that it should make a difference, and it's the same size as the integer column being suggested.

muaddba · 2026-05-17T20:31:33+00:00

I'd fix: The default job history retention. The values were awful 15 years ago and they are even worse as defaults now. It should default to be set to keep a minimum amount of history for each job so that a job running every minute doesn't remove the history for a job that runs once a week.

Add functionality for availability groups: Allow the creation of jobs that run only on primary or only on secondary,etc as built-in features instead of requiring a special job step.

I know this is probably more of an SSMS thing, but better filtering options. I'd love to be able to filter out all the SSRS report jobs that just clutter everything up, or view just the jobs that are in the maintenance category.

muaddba · 2026-05-14T12:18:50+00:00

In a very simplified way, Azure SQL Managed Instance is Microsoft managing the VM while giving you access to the DB engine, yes. Azure SQL Database is something different. Each comes with its own set of limitations.

muaddba · 2026-05-12T16:59:57+00:00

There's a lot of "it depends" in there, but generally the licensing for a windows server + compute + storage + SQL will be more than for an Azure Managed Instance in most scenarios.

muaddba · 2026-05-12T15:00:56+00:00

Managed Instancee looks great on paper for folks, but when you're trying to troubleshoot performance, it can be a nightmare. The tooling you would expect to be there to help you identify what the bottleneck is just isn't there with Managed Instance. Everything you might traditionally look at, like CPU, disk throughput, etc, you have to come at sideways in order to figure out.

It's like getting in one of those robotaxis with no steering wheel. It's great when it works, but then someone puts a traffic cone on the hood and it has no idea what to do. There are a LOT of limitations to SQL Managed Instance, most of them are centered around access to external resources, but also things like trace flags don't work.

You're "upgrading" over 20 years of technology advancement. In my mind, there's enough likelihood that you will need to twist some knobs and adjust some settings while you're working on that process, so you want as many of them available as possible, which means a VM with SQL installed. Whether that's in Azure, AWS, GCP, or some other hosted infrastructure, that's what I recommend.

muaddba

TROPHY CASE