• Jeff Moden - Monday, May 22, 2017 10:19 PM

    Phil Parkin - Monday, May 22, 2017 6:00 PM

    Anyone in the mood for talking about RAM requirements while remaining tight-lipped about the use of NOLOCK? Here you go.

    Not to mention that he has a fairly busy WebServer and SSIS on the same box.  His database is pretty small though.  As he says, he has 14 LAC (1.4 million in U.S. English terms) "records" on it.  Unless they're "super records", that's a pretty small database as today's databases go.

    But at least they (ahem) "designed the pages" to minimize the impact of NOLOCK, so all should be fine.
    I don't have the energy to fight that battle today, but if anyone wants to, then please tell them how silly it is to first expand RAM and then tune queries so well that you don't ned the RAM anymore, (Not that I would ever protest against more RAM for a DB server, but with 1.4 million rows in 28 GB, he probably holds the entire database in the buffer pool already)


    Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
    Visit my SQL Server blog: https://sqlserverfast.com/blog/
    SQL Server Execution Plan Reference: https://sqlserverfast.com/epr/