We’re rewarding the question askers & reputations are being recalculated! Read more.

New answers tagged

5

Note the very last part of the error message you referenced: .. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized. If you look at the entire chunk of errors related to tempdb creation: 2019-11-01 22:37:07.20 spid9s Clearing tempdb database. 2019-11-01 22:37:07.23 spid9s Error: 5171, ...


1

Use the errorlog file instead of the eventlog, It is easier to see the chain of errors from the first one and to subsequent errors that resulted from that. Post the relevant ones here if you need to after reading below. Tempdb is created according to your sys.master_files. This is the template for your tempdb regarding the files. If your sys.master_files ...


0

As mentioned, if the files doesn't exist, then they are created at startup. So the question is whether to delete them from the old location and lest SQL Server creates new ones? Or to move the files so SQL Server don't have to create new ones? One could argue that one of these would be quicker than the other. If that isn't an issue, then use whichever feels ...


1

The best approach is the one you can find on the Moving the tempdb database section of the documentation. Your method is close to the one Microsoft recommends, except by the 2nd and 3rd steps you listed and the reason is: Because tempdb is re-created each time the instance of SQL Server is started, you do not have to physically move the data and log ...


Top 50 recent answers are included