Skip to content

Commit 00f34d9

Browse files
BUMPS
1 parent 2fddf40 commit 00f34d9

31 files changed

Lines changed: 167 additions & 118 deletions

Alerts/Alerts.sql

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ GO
1111
1212
This script will set up alerts for high severity and corruption errors in SQL Server.
1313
14-
Copyright 2025 Darling Data, LLC
14+
Copyright 2026 Darling Data, LLC
1515
https://www.erikdarling.com/
1616
1717
For support, head over to GitHub:

CLAUDE.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,12 @@ This document outlines the T-SQL coding style preferences for Erik Darling (Darl
1010

1111
- **Keywords**: All SQL keywords in UPPERCASE (SELECT, FROM, WHERE, JOIN, etc.)
1212
- **Functions**: All SQL functions in UPPERCASE (CONVERT, ISNULL, OBJECT_ID, etc.)
13-
- **Data types**:
13+
- **Data types**:
1414
- Never abbreviate data types (use INTEGER instead of INT)
1515
- All data types must be lowercase (varchar, nvarchar, datetime2, bigint, etc.)
1616
- Length specifications must also be lowercase: nvarchar(max), not nvarchar(MAX)
1717
- Precision and scale specifications must be lowercase: decimal(38,2), not DECIMAL(38,2)
18+
- Always use sysname for SQL Server object names (database names, table names, schema names, column names, index names, etc.) rather than nvarchar(128)
1819
- **Keywords**: Never abbreviate keywords (use EXECUTE instead of EXEC, TRANSACTION instead of TRAN, PROCEDURE instead of PROC)
1920
- **Indentation**: 4 spaces for each level of indentation (NEVER use tabs)
2021
- **Line breaks**: Each statement on a new line

Clear Token Perm/ClearTokenPerm Agent Job.sql

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ For background on why you might need this:
1616
1717
In short, if your security caches are growing out of control, it can cause all sorts of weird issues with SQL Server.
1818
19-
Copyright 2025 Darling Data, LLC
19+
Copyright 2026 Darling Data, LLC
2020
https://www.erikdarling.com/
2121
2222
For support, head over to GitHub:
@@ -73,7 +73,7 @@ EXECUTE @ReturnCode = msdb.dbo.sp_add_job
7373
@description = N'For background on why you need this:
7474
https://www.erikdarling.com/troubleshooting-security-cache-issues-userstore_tokenperm-and-tokenandpermuserstore/
7575
76-
Copyright 2025 Darling Data, LLC
76+
Copyright 2026 Darling Data, LLC
7777
https://www.erikdarling.com/
7878
7979
For support, head over to GitHub:

Clear Token Perm/ClearTokenPerm.sql

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ For background on why you might need this:
1616
1717
In short, if your security caches are growing out of control, it can cause all sorts of weird issues with SQL Server.
1818
19-
Copyright 2025 Darling Data, LLC
19+
Copyright 2026 Darling Data, LLC
2020
https://www.erikdarling.com/
2121
2222
For support, head over to GitHub:

Clear Token Perm/Inflate Security Cache Demo And Analysis Script.sql

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ https://code.erikdarling.com
2121
2222
MIT License
2323
24-
Copyright 2025 Darling Data, LLC
24+
Copyright 2026 Darling Data, LLC
2525
2626
https://www.erikdarling.com/
2727

Clear Token Perm/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,5 +71,5 @@ TRUNCATE TABLE dbo.ClearTokenPermLogging;
7171

7272
The DBCC FREESYSTEMCACHE command used in these scripts will clear the security cache, which may cause a temporary performance impact as the cache is rebuilt. Test thoroughly in non-production environments before deploying to production.
7373

74-
Copyright 2025 Darling Data, LLC
74+
Copyright 2026 Darling Data, LLC
7575
Released under MIT license

Create Long IN List/Longingly.sql

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ GO
1313
1414
This procedure exists only to show how long IN clauses can hurt query performance.
1515
16-
Copyright 2025 Darling Data, LLC
16+
Copyright 2026 Darling Data, LLC
1717
https://www.erikdarling.com/
1818
1919
For support, head over to GitHub:

Helper Views/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,5 +100,5 @@ EXECUTE dbo.tempdb_tester;
100100

101101
Some of these scripts (particularly WhatsUpMemory) may cause performance issues if run on busy production servers. Use with caution, especially on servers with large amounts of memory.
102102

103-
Copyright 2025 Darling Data, LLC
103+
Copyright 2026 Darling Data, LLC
104104
Released under MIT license

Helper Views/tempdb_tester.sql

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ GO
1313
1414
This generates some semi-random tempdb activity
1515
16-
Copyright 2025 Darling Data, LLC
16+
Copyright 2026 Darling Data, LLC
1717
https://www.erikdarling.com/
1818
1919
For support, head over to GitHub:

Install-All/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,5 +58,5 @@ The script will:
5858

5959
The WhoIsActive Logging procedures are not included in this file, as they have a different installation process and depend on Adam Machanic's sp_WhoIsActive.
6060

61-
Copyright 2025 Darling Data, LLC
61+
Copyright 2026 Darling Data, LLC
6262
Released under MIT license

0 commit comments

Comments
 (0)