From cb83eeeb1fd5ae6fe12de9b48b9e78dae3d2211b Mon Sep 17 00:00:00 2001 From: 1DontEx1st Date: Fri, 10 May 2024 09:30:22 -0400 Subject: [PATCH 1/2] Update README.md fix typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1a52b87..b8df491 100644 --- a/README.md +++ b/README.md @@ -332,7 +332,7 @@ The SQL Server error log can have a lot of good information in it about what's g The problem is that it's hard to know *what* to look for, and what else was going on once you filter it. -It's another notoriously bad Microoft GUI, just like Query Store and Extended Events. +It's another notoriously bad Microsoft GUI, just like Query Store and Extended Events. I created sp_LogHunter to search through your error logs for the important stuff, with some configurability for you, and return everything ordered by log entry time. From 9de3226eba17ffe828264c28e112aa96ea5da1fd Mon Sep 17 00:00:00 2001 From: Erik Darling <2136037+erikdarlingdata@users.noreply.github.com> Date: Tue, 14 May 2024 08:22:14 -0400 Subject: [PATCH 2/2] Update sp_QuickieStore.sql Closes #420 --- sp_QuickieStore/sp_QuickieStore.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sp_QuickieStore/sp_QuickieStore.sql b/sp_QuickieStore/sp_QuickieStore.sql index b2b2702..c93a7b9 100644 --- a/sp_QuickieStore/sp_QuickieStore.sql +++ b/sp_QuickieStore/sp_QuickieStore.sql @@ -2447,7 +2447,7 @@ BEGIN IF @df = 1 BEGIN SELECT - @where_clause += N'AND DATEPART(WEEKDAY, qsrs.last_execution_time) BETWEEN 1 AND 6' + @nc10; + @where_clause += N'AND DATEPART(WEEKDAY, qsrs.last_execution_time) BETWEEN 1 AND 5' + @nc10; END;/*df 1*/ IF @df = 7