Remove the auto-close option from databases by way0utwest

Hello,

Thank you for submitting this suggestion, but we're trying to clean house and remove items we feel we will likely not address given their priority relative to other items in our queue. We believe it is unlikely that we will address this suggestion, and so we are closing it as “won’t fix”.

This cleaning will help us focus on the high-priority items that we feel need to get done, and we hope that it help provide better clarity to you about the issues we will (and won't) address.

While we've tried to look at each of these items individually, this was a large effort, and so we may have erred in assessing this particular suggestion's priority. If you feel that this is worth reconsidering, please feel free to re-file it and we will be happy to take another look.

--
Umachandar, SQL Programmability Team

My apologies for not being clearer. I understand the deprecation list, and that is what I envision as the removal process. deprecate through 2 versions, then remove from the 3rd.

The issues that I have seen, and which are posted often on my site, are poor performance from the database due to startup/shutdown of the files. There are novices that think this saves significant resources, and don't understand the impact in multi-user databases.

I could see this as a feature only enabled on single user databases, but with hardware becoming so fast, and the resources required to keep the db open low, is it really needed anymore? I would vote to simplify and streamline the product, removing features that are not necessary.

Thanks for submitting this request to the SQL Server team. Please let me know if I am understanding the request correctly. The request is to remove the auto-close feature of database altogether because it is not longer needed (could you please elaborate why?) and novice dbas/admins might set it without realizing the repurcussions.

I have added this as a DCRs to consider.

On a side note, we typically do not remove features but put them on the deprecation path, so we don't impact customers that are using that feature.

Thanks