Comments on: Auto Close is almost as bad as auto grow http://itknowledgeexchange.techtarget.com/sql-server/auto-close-is-almost-as-bad-as-auto-grow/ Tue, 07 May 2013 13:39:52 +0000 hourly 1 By: Mrdenny http://itknowledgeexchange.techtarget.com/sql-server/auto-close-is-almost-as-bad-as-auto-grow/#comment-349 Mrdenny Mon, 14 Dec 2009 06:49:51 +0000 http://itknowledgeexchange.techtarget.com/sql-server/auto-close-is-almost-as-bad-as-auto-grow/#comment-349 Pretty much no. Having the application use the sa account wouldn’t change the desire to close the database. Auto-close simply flushes the data to disk removing it from the buffer and procedure cache which would then simply slow down the application the next time it needed access to the data.

About the only time that I could see auto close being worthwhile (and this would need some major testing and probably some special configurations to do correctly) would be if your OLTP database and your OLAP database shared a SQL Instance, and the OLTP database was only used during the day, and your OLAP database was only used at night. This would maximize the resources that each database would have access to. However on the flip side without auto-close enabled the SQL Server engine will remove data from the cache if it hasn’t been accessed to make run for the data which is being accessed so even then you would probably be better to leave the database not in the auto-close.

]]> By: Cyberhh http://itknowledgeexchange.techtarget.com/sql-server/auto-close-is-almost-as-bad-as-auto-grow/#comment-347 Cyberhh Thu, 10 Dec 2009 17:13:33 +0000 http://itknowledgeexchange.techtarget.com/sql-server/auto-close-is-almost-as-bad-as-auto-grow/#comment-347 Denny,

Is there a place and time for auto close? For instance when you have a database application that executes all it’s queries as the sa account? At the same time the majority of the reads are going to be to the same database(s) over and over, so your logic may still hold true.

Thanks

]]>