ScottPletcher (2/28/2013)
So if tempdb now does need to grow for whatever reason, and it causes a SQL issue because it can't, you've guaranteed that there's no easy way to recover, since the current physical files absolutely can't be expanded?
A) How does this differ from tempdb trying to autogrow past the size of the drive and failing because you've filled up the drive?
B) Yes, there's an easy way to recover. The transaction returns an error and rolls back. Which is exactly the same thing that would happen if you auto-grew the file to use the whole drive and it ran out of space, except in my case, it would happen quicker because it wouldn't have to attempt the auto-growth before failing.
What are you expecting to happen? Really, your arguments are not logical.