Gostev wrote:It is important to realize that LocalDB is not "yet another SQL instance" that requires "extra management", but rather lightweight runtime-only database engine.
By using LocalDB, we are able to re-use big chunks of code from our enterprise backup product that is in fact based on "full-blown" SQL Server. This significantly reduces the costs of development and testing, which is very important for a free product
Stefan121 wrote:But LocalDB is not "lightweight": 578MB private bytes and 378 MB working set size is too large for naming it lightweight.
Mike Resseler wrote:...We truly believe it is too much so worth investigating. Can you create a support call...
I found that LocalDB memory usage was lower than before the reboot. It was around 150 MB.
I wonder if that screenshot in the guide was just taken from a freshly booted system
Users browsing this forum: stevem and 1 guest