I'm using LocalDb with .NET, and the first time I connect to the default instance a new process is created in order to attach the mdf. Now, as the first opening of the connection is quite slow, I would like the localdb process of sql server to live forever,
or till the closing of my application. The problem is, if there'arent connection for some minutes, the process is shutting down by itself. Is there a way to avoid this behaviour?
Another question related to the same behaviour. Is there a way to "preload" the localdb instance at the startup of Windows (or when the user logs in)? Or should I create a process that does this job for me and set it to the Windows startup?
Thank you in advance for your help
Sebastiano
Go to the complete details ...