Here is the kind of scripts defined within TEchnet articles about running black-box kind of traces against your SQL Server instance, then also you can take advantage of the blackbox trace if you are facing intermittent problems, you want to make sure that it is always running when your server is running...
use msdb declare @schedule_uid uniqueidentifier select @schedule_uid=(select schedule_uid from msdb..sysschedules where name=N'CollectorSchedule_Every_15min') declare @collection_set_id int; exec dbo.sp_syscollector_create_collection_set @name = N'SqlTraceDefault', @schedule_uid = @schedule_uid...
The following pages were recently modified. Source: Knowledge Base Product: Microsoft SQL Server 2005 Enterprise Edition Notification Contents: New and Major Modifications How to use a stored procedure to monitor traces in SQL Server 2005 http://support.microsoft.com/kb/912914/en-US...( read more )
Yet another important factors that every DBA needs to concerned about table & index fragmentation within their SQL Server environment. Refer to the a rticle about DetectTableFragmentation in both 2000 and 2005 version. Fragmentation occurs due to updates and delets on the table and the golden rule...
Say you have a serious performance problem and few times you will have assertion issue with a dump files creation, in real world say this can be matched to a airplane crash. Where you will know the sequence of events from Black-box records in the flight to investigate, similarly how about having such...