You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/Development/ReleaseProcess.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,7 @@ Well, useful is probably the wrong word. More like entertaining. Here we go.
34
34
* sp_BlitzQueryStore @Version and @VersionDate
35
35
* sp_AllNightLog @Version and @VersionDate
36
36
* sp_AllNightLog_Setup @Version and @VersionDate
37
+
* sp_BlitzInMemoryOLTP @Version and @VersionDate
37
38
38
39
## Push to Master
39
40
@@ -47,14 +48,12 @@ Well, useful is probably the wrong word. More like entertaining. Here we go.
47
48
* Copy the FirstResponderKit.zip into Employees/Public.BrentOzar
48
49
* For PowerBi, only keep the .pbit file
49
50
* Copy the Github release text into a WordPress blog post with the First Responder Kit Updates category. The nice thing about doing the Github release first is that you should be able to copy/paste the Github release page and the HTML should paste smoothly into the WordPress draft window, complete with links to the Github issues. At the end of the post, put a download now link that points to: https://www.brentozar.com/first-aid/
50
-
51
51
* Blog post support wording:
52
52
53
53
<h3>For Support</h3>
54
54
55
-
<strong>You can <ahref="https://www.brentozar.com/first-aid/">download the updated FirstResponderKit.zip here</a>.</strong>
56
-
57
55
When you have questions about how the tools work, talk with the community in the <ahref="https://sqlcommunity.slack.com/messages/firstresponderkit/"target="_blank"rel="noopener">#FirstResponderKit Slack channel</a>. If you need a free invite, hit <ahref="http://SQLslack.com/"target="_blank"rel="noopener">SQLslack.com</a>. Be patient - it's staffed with volunteers who have day jobs, heh.
56
+
58
57
When you find a bug or want something changed, read the <ahref="https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/blob/master/CONTRIBUTING.md"target="_blank"rel="noopener">contributing.md</a> file.
59
58
60
59
When you have a question about what the scripts found, first make sure you read the "More Details" URL for any warning you find. We put a lot of work into documentation, and we wouldn't want someone to yell at you to go read the fine manual. After that, when you've still got questions about how something works in SQL Server, post a question at <ahref="http://dba.stackexchange.com"target="_blank"rel="noopener">DBA.StackExchange.com</a> and the community (that includes us!) will help. Include exact errors and any applicable screenshots, your SQL Server version number (including the build #), and the version of the tool you're working with.
Copy file name to clipboardExpand all lines: Documentation/sp_Blitz Checks by Priority.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@ Before adding a new check, make sure to add a Github issue for it first, and hav
6
6
7
7
If you want to change anything about a check - the priority, finding, URL, or ID - open a Github issue first. The relevant scripts have to be updated too.
'The oldest query in the plan cache was created at '+CAST(creation_time ASNVARCHAR(50)) +'. Someone ran DBCC FREEPROCCACHE, restarted SQL Server, or it is under horrific memory pressure.'
3352
+
'The oldest query in the plan cache was created at '+CAST(creation_time ASNVARCHAR(50))
3353
+
+CASEWHEN @user_perm_gb_out ISNULL
3354
+
THEN'. Someone ran DBCC FREEPROCCACHE, restarted SQL Server, or it is under horrific memory pressure.'
3355
+
ELSE'. You also have '+CONVERT(NVARCHAR(20), @user_perm_gb_out) +' GB of USERSTORE_TOKENPERM, which could indicate unusual memory consumption.'
0 commit comments