Comments
-
Great question. The existing PLE advisory condition is excellent, and the formula to calculate the dynamic threshold is working as expected. I used it as the main example since it's what I was working on, but I believe the feature could find use with a variety of conditions. The challenge we're facing is not with the what…
-
Great question! I honestly don't know the answer here. Your assumption is intuitive and feels correct - both are technically binary values. Assuming they are both treated as binary for the purposes of a join, a GUID may actually be slightly faster than hashbytes depending on the output length of the hashbytes function. I'm…
-
Is that 1 min 57 sec for the union and 13 sec for the joins?
-
Ah - that does complicate things a bit. Based on the examples I thought they'd all have identical schemas. Hrm... I'll keep mulling it over. Good luck!
-
Cool. I'm wondering about unioning the partitioned tables together before doing a join. Have you tried that yet? I'm guessing a sizeable portion of your issue is due to the number of joins, as each one has to create a sub-table in memory before the next join can be processed. If you could union them all into one table…
-
You say content1, content2, etc. all contain a subsets of the rows found in Content. In the example rows you gave for content1 and content2, these appear to be partitioned by contenttype. Is that always the case? Are there overlaps in the data in any way?
-
I've done this before - it doesn't work in every situation, but can be a lifesaver when it does work. Essentially you concatenate all of the fields in the composite key and dump it into the hashbytes function. Picking a common datatype for all of the fields is usually the hardest part. So for a table with a composite key…
-
Ideal backup strategy is kind of tricky... This is one of those 'It Depends' topics - budget, sensitivity, traffic, etc. all play into what's ideal for a given system. My first step is try to get RTO/RPO numbers from management for a system before start making recommendations. Most of the time I end up with something very…
-
That's an awesome improvement! We recently had a P1 that this would have caught and corrected before anybody noticed a problem. Unfortunately I somehow had equated the auto plan correction setting with the auto-index tuning in Azure, so I've been skipping this setting in my environment. Time to revisit this one.
-
I've never liked web dev, but it's on my list right now since I'm neck deep in automating a bunch of our solutions in PowerShell Universal. Past that, I'm going to start some deeper dives on security and tuning with the new features in SQL2022. Plenty to stay busy with!
