15:50 That is why, in 2019, you need to bounce Windows machines regularly. Servers, clients, old, new, whatever. Linux and Unix actually have good memory management and don't need regular bounce, at least not for this reason.
18:30 Copying big files between host and RDC sessions must be the worst thing to do, since it is using the memory of the host, the memory of the client session, and the network, but in a way it wasn't designed cause it is not a slim command (like XCOPY) but part of the Windows clipboard function, which is written to copy 7 bytes content on average (text or file). Not to mention it tends to be slow.
the sql dba community must be very small, he knows everyones names :D. i've been a dba for 4 years now, and got a job as a jr dba at a Microsoft Gold partner company,and the first thing they mentioned to me me was look up Brent Ozar and ola Hallengren.
I don't buy what he's saying about the file caches. Why would Windows continue to cache data from disk if SQL Server's in a position to actively request it from the OS? That's not the behavior for *other* types of operations, after all, so I'm not sure why SQL Server would be treated different from another application.
16:40 Agreed to be careful what software to trust, but if it was written by Mark Russinovich, I don't know what more of a clue you are waiting on to get "better" fixes. Remember, MS bought software from this one guy. Some people really think that the vendor is the almighty, and everybody else is stupid.
Ozar is a SQL Legend
Great knowledge, great entertainer as well :)
Great stuff!
15:50 That is why, in 2019, you need to bounce Windows machines regularly. Servers, clients, old, new, whatever. Linux and Unix actually have good memory management and don't need regular bounce, at least not for this reason.
that's why they have SQLServer in Linux I believe to solve these worries. Heard it is a beast unleashed to hit Oracle & other competitors.
Good Stuff Bent
Intel 750s, P3500/3600/3700 are NVME
18:30 Copying big files between host and RDC sessions must be the worst thing to do, since it is using the memory of the host, the memory of the client session, and the network, but in a way it wasn't designed cause it is not a slim command (like XCOPY) but part of the Windows clipboard function, which is written to copy 7 bytes content on average (text or file). Not to mention it tends to be slow.
the sql dba community must be very small, he knows everyones names :D. i've been a dba for 4 years now, and got a job as a jr dba at a Microsoft Gold partner company,and the first thing they mentioned to me me was look up Brent Ozar and ola Hallengren.
Ola Hallengren scripts are awesome.
too good...it hit the target... :)
he is drinking whiskey??! happy presenter !
NVME changes things as does over provisioning
I don't buy what he's saying about the file caches. Why would Windows continue to cache data from disk if SQL Server's in a position to actively request it from the OS? That's not the behavior for *other* types of operations, after all, so I'm not sure why SQL Server would be treated different from another application.
16:40 Agreed to be careful what software to trust, but if it was written by Mark Russinovich, I don't know what more of a clue you are waiting on to get "better" fixes. Remember, MS bought software from this one guy. Some people really think that the vendor is the almighty, and everybody else is stupid.
"10% free or 4GB whichever is greater". Lord help those servers with 4GB memory total :-D (They exist and are not as rare as unicorns).
Cody Konior When your DB is only 1GB in size it's not so bad.
Apparently all 32-bit machines, which must mean: zillions of them.