Jeffrey Williams wrote:
I have no idea why Microsoft has kept that option in the product - auto shrink will cause massive fragmentation of the database every time it shrinks. It is just a bad option that has no benefits...there should be no reason to shrink a database on a normal basis.
As for why you cannot use auto close - I think that is obvious. If you enable memory optimized tables - they must remain in memory and auto closing the database forces them out of memory, so you cannot use that option in conjunction with memory optimized tables.
If you look carefully at the original post, he's setting Auto_Close to 'False'... it shouldn't be causing an error. 🙂
Totally agreed on your stance for Auto_Shrink... especially since the database is also being set to Read_Only. There shouldn't be a need even if it was a good idea (and I agree it's not). Which brings us to a different subject...
Why would anyone create a new, empty, database as Read_Only? It would remain empty because you couldn't write to it unless you changed Read_Only to 'False' at least for an initial load.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)