Jörg Stryk

Stored Procedure "ssi_indexrebuild": - Added hardcoded LOCKTIMEOUT of 10 seconds; line 277 - Improved TRY CATCH part; lines 276 - 292

Added hardcoded LOCKTIMEOUT of 10 seconds; line 277 Improved TRY CATCH part; lines 276 - 292

BTW: You could monitor the tempdb-size with such an Alert, for example: USE [msdb]; GO EXEC msdb.dbo.sp_add_alert @name = N'Warning: Size [tempdb]', @enabled = 1, @delay_between_responses = 60, -- dealy between responses, 1 minute, change on demand @include_event_description_in = 0, @performance_condition = N'Databases|Data File(s) Size (KB)|tempdb|>|1024000', -- size threshold, here 1024000 KB = 1 GB; change as applicable @job_id = N'00000000-0000-0000-0000-000000000000'; GO EXEC msdb.dbo.sp_add_notification...

Bloody hell, that happens when you copy & paste too much ... mea culpa ... The Analysis was actually NOT grouping <facepalm emoji=""> ... I fixed that ... (I think) <shame emoji=""> ...</shame></facepalm>

One tester reported a brutal load on "tempdb" - the Job "SSI: Block Recording" ran for more than an hour (?) and dramatically increased the size of the "tempdb" (??) ... Not sure what happened here, since the stuff is just recoding to its own table, by default in "msdb" ... My current guess is: Technically lots of micro-blocks happen which possibly also trigger that Alert, thus it might be (now: have been?) somewhat "hyper-nervous" and recording all this nonsense ... The affected server (above) runs...

<<For a moment, nothing happened. Then, after a second or so, nothing continued to happen.>> (Douglas Adams) "Blocked Queries" are most annoying in SQL Server; stalling, delaying or even cancelling transactions. To thoroughly investigate and analyze these conflicts it is necessary to automatically record these issues. That's what this stuff is about ...

Thanks! Looking forward to getting your feedback!

Added two templates to create the SQL Agent Jobs for "Auto Indexing" (one to EXECUTE, one for "Script Only"). So far "Ix Adder" is doing in 100% of all customer-cases exactly what it is supposed to do! I guess I'll soon put it from status "Beta" to "Production/Stable" ...