Brutal.... "there's one vacancy in (other team) and only one person can move over retaining all benefits and service history." Clearly work expected the ~3 eligible people to fight for it.
The two good ones said "fuckit gimme severance" and the shitty guy remains, thinking he won
okay long story short, I'm going through a divorce right now, for the last ~6 months. Part of that is me buying the house and paying the other half to the ex. That means getting a mortgage, which means good proof of income.
So yeah I need a high paying job to qualify as a single person owning a home
this job has a lot of bad sides, but satisfies the bank.
We are having a production Microsoft SQL Server 2019 Enterprise Edition with 128 cores CPU and 256 GB RAM.
Max DOP set as 56 and Cost Threshold as 300.
Disk IOPS is set at 32000.
Database MDF on one disk and LDF on the other.
Frontend Application is Dot Net Core
Inserts and Updates are done throu...
The Easter Bilby is an Australian alternative to the Easter Bunny and chocolate bunnies. Bilbies are native Australian marsupials that are endangered. To raise money and increase awareness of conservation efforts, bilby-shaped chocolates and related merchandise are sold within many stores throughout Australia as an alternative to Easter bunnies.
== Concept and stories ==
The first documented use of the Easter Bilby concept was in March 1968 when a 9-year-old girl Rose-Marie Dusting, wrote a story, "Billy The Aussie Easter Bilby," which she published as a book 11 years later. The story helped...
I've just discovered that GETDATE and friends are actually sniffed as if they were parameters. sqlshack.com/runtime-constants-sniffing I feel like I knew that or should have realized, but interesting to see clearly.
Is there any benefit in parameterizing the value of GETDATE()/GETUTCDATE()? The objective is to allow SQL Server to reuse execution plans, example:
SELECT [c].[ID], [c].[Name]
FROM [Customer] AS [c]
WHERE [c].[ActivationDate] > DATEADD(day, CAST(-7.0E0 AS int), GETUTCDATE()) AND [c].
[Activation...
@ErikDarling Looks like plan reuse is working fine, not sure what you mean dbfiddle.uk/ovAdpfDr Obviously you may want to avoid it in this case, which is what I mentioned in my answer.
Two queries, the only difference is the calculated constant off getdate() which is then sniffed and a different plan selected. Using local variables does not behave in this way dbfiddle.uk/PKi6GrZQ
well, that i'm not arguing with you about anything. it's sniffed per statement. the reason the second query in dima's post gets a bad estimate is that the plan from the first is reused (with the initial sniffing). the recompile against the object invalidates the plan and forces a new one with a fresh stats calculation.
> Msg 12135, Level 16, State 1, Line 1 The Metadata needed for Optimized Locking is not populated yet. Please retry the operation. Msg 5069, Level 16, State 1, Line 1 ALTER DATABASE statement failed.
It's funny how we tend to speak in absolutes about certain things. Which is useful for general guidelines. But also tends to create zealotry over time.
@PaulWhite I don't think plan reuse was the point there, yes obvious you get it. The point of the article was that GETDATE is sniffed, rather than working like a local variable or OPTIMIZE FOR UNKNOWN.
Unless you were referring to the Stack Overflow question. Well unlikely they ever heard of either parameter sniffing or plan reuse, so moot point.
I'm almost 50 - once all this paperwork shit is done and I own the house, I'll buy a small piece of farmland and go live in a tinyhouse, then build an enormous workshop then spend the rest of my life stocking it with old-school tools.
I don't need a large family home for me and the dog
I am not living in a tent or caravan though. A small-home at least.