« first day (511 days earlier)      last day (178 days later) » 
00:00 - 20:0020:00 - 00:00

8:05 PM
figures
i was close to mortarboarding today
 
that must have been the reason
 
cahoots
 
8:22 PM
index rebuilds! on a system brent built!
 
yup, my fault :(
 
don't worry, you're safe:
yesterday, by Joe Obbish
@ErikDarling No one ever got fired for doing index rebuilds
 
(by joe)
 
@ErikDarling don't make me quote you
 
i haven't said anything
 
8:24 PM
yesterday, by Erik Darling
no one ever gets fired
you AGREED with me, as the transcript shows
 
@Taryn you should upvote my answers just in case 😘
 
that's a batch mode sort
 
@JoeObbish i corrected the record
serial top, distribute, serial sort, gather streams
that's fantastic
probably a collation thing
 
in some cases it will faster than just a serial plan
so I can't say that it's wrong
but it sure feels wrong
 
how many rows?
@JoeObbish serial batch mode?
 
8:27 PM
ONE MILLION ROWS
@ErikDarling yeah, why not
 
@ErikDarling We hit this wait which took everything down
2
Q: What is the DPT_ENTRY_LOCK wait type?

SteveBWe have a SQL Server 2016 Availability Group with 3 servers. Twice in the past 5 days we have had performance issues. 8a is our primary server, and 8b and 8c are the secondaries. We started having issues right before 8PM. We saw timeouts as well as 502 Bad Gateway errors. On 8b and 8c we see...

 
@JoeObbish tss you could run that on my headphones
@Taryn have you tried tf3459 or are you past that?
 
we don't have that turned on for StackOverflow
 
well the moral of the story is you should use log shipping
 
Erik wants to star in an anime about log shippan
How will LOG SHIPPAN MAN save the day today?
 
8:34 PM
@ErikDarling is that really moral?
 
by being STABLE and RELIABLE
 
 
1 hour later…
10:03 PM
Msg 1790, Level 16, State 1, Line 3
The name of a user-defined table type cannot start with a number (#) sign.
foiled again
 
10:43 PM
Supremely
 
Like I said, stop rebuilding indexes
 
@SeanGallardy pfft...never
 
something something cries when you rebuild indexes
it's SQL madlibs
fill in the somethings
 
just fix all the AG issues, Sean and it will work for us
 
I'm on it
ALL OF THEM
 
10:56 PM
work faster!
 
I'm running out of hamsters to run on wheels to power my laptop
 
@ErikDarling Do I have to worry about performing mundane DBA tasks like rebuilding indexes if I use the superior Log Shipping technology?
 
Ever get that data all migrated?
 
@SeanGallardy yes, thanks for asking buddy!
 
@SeanGallardy haha, actually I finished the bulk of it today. Took about 6 months.
 
11:02 PM
@Taryn Yay, GRATZ!
@JoeObbish Gratz to you as well! Any good bus stories?
 
@SeanGallardy It's a day to day move now until we finish the cutover and get new servers
 
Is that better or worse?
 
New servers will be great - we will no longer be on spinny disks.
 
@JoeObbish not if you compress your log backups 😏
 
Question for the room: Do you LOL, facepalm, stare into oblivion, or some combination of the aforementioned when someone tells you that, "Locking and Blocking are bugs in SQL Server and need to be fixed."
@Taryn I can get behind leaving spinny disks!
Also, day 4-ish of stomach meds and I haven't thrown up in the last 2 days. Progress.
 
11:07 PM
@SeanGallardy no because rcsi should be the default 😉
 
@SeanGallardy all of the above
 
@SeanGallardy we're seeing something that looks like an awful like an undetected deadlock on four customer systems
heard about it this week
 
@ErikDarling RCSI might not meet your requirements, versioned data may not be allowed
@JoeObbish I'm talking about regular locking and blocking
like, you rebuild the clustered index, offline mode, and your queries against the table are blocked
 
@SeanGallardy that causes problems for us too. sometimes there's blocking on unrelated objects in sys.partitions. it's very annoying
would you like to try again?
 
Everyone except the honorable Taryn is OP'ing this up
 
11:19 PM
@SeanGallardy that doesn't make a lot of sense
 
4mostpeople
 
11:35 PM
@SeanGallardy millions of databases in azure
 
11:52 PM
@SeanGallardy Silliness.
 
00:00 - 20:0020:00 - 00:00

« first day (511 days earlier)      last day (178 days later) »