3 ms·
SQL Server by design grabs as much RAM as it can, as aggressively and preemptively as it can, because it assumes it's the most important process running on the
by piaste 6y ago
SQL Server by design grabs as much RAM as it can, as aggressively and preemptively as it can, because it assumes it's the most important process running on the machine. Which is almost always the case in production environments, and a reasonable default behaviour as a result. If that's not the case, you can easily set resource limits at the application, container, and/or VM level.
(This comment coming from someone who used to have to support running small backup MSSQL instances on Windows 8 tablets.)
- skeletonjelly 6y agoYep this. SQL Server using RAM is by design. If it's using too much because you're using it for dev work then you can simply limit the amount it can access. RAM is there to be used!
- MereInterest 6y agoIt's a perfectly fine design so long as there's one, and only one, program that is maximizing its RAM usage. When you have many programs (e.g. the browser, Teams, slack, every single electron app), then you get loads of contention.
- easton 6y ago> (This comment coming from someone who used to have to support running small backup MSSQL instances on Windows 8 tablets.) Can I ask what the use case was? Was it just in case the primary DB server died and they wanted a battery powered backup?
- ryanjshaw 6y agoCan't speak for OP but here in Africa I've worked on a two unrelated projects where poor internet connectivity meant it made sense to have a local SQL Express running on a users device, which a service would then try to regularly synchronize with the central server. Makes sense when you are capturing documentation and can make all the decisions in disconnected operation.