Tag Info

New answers tagged

0

Tempdb won't be available for you in the Mantainance Plan database list box, but you sure can run it as a script: DBCC CHECKDB(N'tempdb') WITH NO_INFOMSGS According to Mr. Brent Ozar, you SHOULD check tempdb for integrity, and if Brent is saying that, that is good enough for me. regards


5

Even if you have plenty of DRAM, tempdb may still be used. This happens in a few situations: Snapshot isolation: Using this feature can create a lot of tempdb activity. Hash and sort Spills: When the optimiser creates a query plan, it will try to estimate the total amount of memory it needs to run the query. Before the query runs, the estimated memory is ...


0

This doesn't answer your question, however I thought you might find it helpful to see if there have been any recent log growths: /* Description: display growth events for all databases on the instance by: Max Vernon date: 2014-10-01 */ DECLARE @Version NVARCHAR(255); DECLARE @VersionINT INT; SET @Version = ...


0

I'm not sure if this report will give you any more information. http://blogs.msdn.com/b/buckwoody/archive/2007/10/12/sql-server-management-studio-standard-reports-schema-changes-history.aspx it also uses the default trace mechanism but maybe it may give you hints about who is messing about with the server, even if it doesn't provide evidence about the ...


2

If you have the default trace configured, and if the change was recent enough, you might be able to find the change. The default trace only maintains a certain amount of trace, but I have found unexpected changes by examining its contents. See: http://msdn.microsoft.com/en-us/library/ms175513(v=sql.105).aspx This describes how to read the default trace so ...



Top 50 recent answers are included