SQL Server ERRORLOG shows Starting up database over and over again

Observed this on Microsoft SQL Server 2014 (SP2) but is probably true for any SQL Server versions. I am seeing a lot of lines like below in ERRORLOG:

2020-09-11 09:45:00.87 spid20s     Starting up database 'DatabaseName'.

The reason for this repeated logs is that the AUTOCLOSE property of the database is set to TRUE. When AUTOCLOSE is set once the last connection to the database closes it will also close the database and release all the resources associated with it. This can be useful to conserve precious resources on the server, unfortunately this can also impact performance and I have seen cases that it actually depletes the resources on the server when the server is under memory pressure combined with maximum server memory is reached.

To disable AUTOCLOSE, open database properties using SSMS and set Auto Close to False under Options page.

Reference:

https://blog.sqlauthority.com/2016/02/20/sql-server-starting-up-database-why-multiple-times-in-errorlog/

Comments

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re

How to shutdown android-x86 pC

Press Alt+F1, then type: #: reboot -p Reference(s): https://groups.google.com/forum/#!topic/android-x86/pEI7xAnOpNY

8thString

Search This Blog