New answers tagged

0

Start sql server in single user mode - Net Start MSSQLServer /mSQLCMD /f/t3608 To be in single user mode sqlcmd -S. –E Run the commands Alter database tempdb modify file (name = tempdev, filename = 'E:\SQLDATA\DEFAULT\tempdb.mdf') Alter database tempdb modify file (name = templog, filename = 'E:\SQLDATA\DEFAULT\Templog.ldf') Stop sql server Net stop ...


0

One possibility: Between 2012 and 2014 some significant changes were made to the cardinality estimation routines. While these changes create massive improvements for some complex queries there are a few circumstances where it has a detrimental effect - this could cause the query planner to pick a plan that is less efficient than that picked by the older ...


3

Before troubleshooting TempDB space, it is good to know what objects are using TempDB. Even though you have issues only with Version Store, knowing what objects are using TempDB will give you a good idea on where to start. Remember, TempDB is a global resource for all databases, so this will be used for all databases. At a high level these are the objects ...


4

The only way to find out what process caused the autogrowth is to use Extended events esp. EVENT --> sqlserver.database_file_size_change & sqlserver.databases_log_file_size_changed and ACTION --> sqlserver.sql_text. Looks like @DBA_ANDY already did the hard work of writing an XEvent -- Original Author : @DBA_ANDY http://nebraskasql.blogspot.com/2016/06/...



Top 50 recent answers are included