« first day (4299 days earlier)      last day (868 days later) » 

@J.D. Yeah, who knows. Paul has probably blohged about it.
2
@PaulWhite I've never heard of that approach!
It comes up now and again
3
Q: Efficiently storing query-affecting settings in a database

BusinessAlchemistI want to know how to efficiently store query-affecting settings in a large analytical database (MS SQL Server). By efficiency I mean no hardcode (1) and fast/optimal query processing (2). My example I've got a massive table of sales orders. Let's simplify it to two columns: SalesOrder OrderI...

10
Q: Create database level constants (enumerations) without using CLR?

EdmundI have a several SQL objects that need to take alternate actions based on a desired state of the request. Is there a way to create database level constants (enumerations) that can be passed to stored procedures, table-valued functions, and used in queries (without using CLR)? CREATE PROCEDURE d...

The second one being a more 'fun' option
A join isn't "more relational" than a subquery btw
01:39
@PaulWhite Was wondering when I'd be called out for that verbiage lol. Subjective linguistics?
 
2 hours later…
03:18
Hard to know.
03:47
I guess my thought process is the concept of a JOIN is obviously part of relational theory, but I'm not sure if a subquery is, as a construct, or only exists as a concrete implementation in query languages. Or if it is, using one specifically as the predicate to a WHERE clause feels more like a concrete implementation of code / kinda hacky. Hence JOIN being "more relational" of a solution, in my mind.
But I'm definitely no expert on relational theory, so do feel free to call me an idiot. 🙂
 
3 hours later…
06:18
Morning
 
1 hour later…
07:27
morning
 
3 hours later…
10:35
🦇🦇🦇
10:56
A chairde - Morning all!
 
2 hours later…
12:37
> blohged
That's what I get for typing on my phone.
autocorrect was a fine idea
I use my phone 99% of the time on this site, so much so I've added "https://www.brentozar.com/pastetheplan" as a word in my phone's keyboard dictionary lol.
Also good morning!
Mr. Foch didn't even need hindsight (even if he probably was wrong about the possible solution)
as in 'This is not peace. It is an armistice for twenty years.'
@PaulWhite ask my wife
I will when she comes round next Thursday as usual
what, you are in Hungary?
12:57
I'm everywhere, man
13:47
that explains, finally, why you never sleep
boundless energy
many clones
14:36
@PaulWhite I made a (long) edit to that snapshot question. Please check and edit any blunders
Nice link
1
Q: The finer points of writers locking each other out under the snapshot isolation levels

JohnThe read committed snapshot and snapshot isolation levels in SQL Server do away with most locking except one: A writer still locks out other writers. The documentation tiptoes around saying as much and subsequently doesn't document anything else which would be very interesting to know: Is it real...

Maybe this person would be interested in the readpast hint since they’re going into nowait territory
@ypercubeᵀᴹ Fixed the typos
Typo Negative
BRB
15:00
I added another note that seems important. At least according to MS ;)
15:28
I didn’t know your wife was also into databases
Isn't everyone's?
If you mean shopping yes
15:43
I bet she keeps track of her spending and purchases in a database
I like it
@PaulWhite yay!
16:01
@Forrest Reminds me of Craig Freedman's post about apparent constraint violations docs.microsoft.com/en-us/archive/blogs/craigfr/…
16:13
It's fun to find 'inconsistencies' under anything less than complete isolation. Locking read committed is near the bottom of the hierarchy, so it's a relatively target-rich environment.
16:29
@Forrest Best movie I've read this year
16:45
All of this stuff has made me consider assumptions I made about locking with adaptive joins
16:58
Anonymous
May 15, 2007
The comment has been removed
Only good comment
 
4 hours later…
21:16
Erik is out there, protecting the SQL against the EF.
 
3 hours later…
23:47
EF = Evil Forces? 🙃

« first day (4299 days earlier)      last day (868 days later) »