Regenerate integrations docs (#22131)
Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>
Netdata bot committed
Apr 3, 2026 at 18:50 UTC
80562ef6e26e3461531bcf7c3dfffb832f828ef6
1 file changed
+23
-18
src/go/plugin/go.d/collector/mssql/integrations/microsoft_sql_server.md
+23
-18
@@ -153,12 +153,26 @@ If you prefer Windows integrated authentication instead of SQL authentication, g
153
Netdata service account access to SQL Server.
154
155
By default, the Netdata service runs as `Local System`. The identity it presents to
156
-SQL Server depends on your environment:
156
+SQL Server depends on whether the connection is local or remote:
157
158
-**Domain-joined machine (Active Directory):**
158
+**Local connection (Netdata and SQL Server on the same machine):**
159
160
-`Local System` authenticates as the computer account (`DOMAIN\COMPUTERNAME$`).
161
-Replace `DOMAIN\COMPUTERNAME$` with your actual values
160
+`Local System` always authenticates as `NT AUTHORITY\SYSTEM`, regardless of whether
161
+the machine is domain-joined or in a workgroup.
162
+
163
+```sql
164
+CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS;
165
+GRANT VIEW SERVER STATE TO [NT AUTHORITY\SYSTEM];
166
+GRANT VIEW ANY DEFINITION TO [NT AUTHORITY\SYSTEM];
167
+USE msdb;
168
+CREATE USER [NT AUTHORITY\SYSTEM] FOR LOGIN [NT AUTHORITY\SYSTEM];
169
+GRANT SELECT ON dbo.sysjobs TO [NT AUTHORITY\SYSTEM];
170
+```
171
+
172
+**Remote connection (Netdata connects to SQL Server on another machine):**
173
+
174
+On a domain-joined machine, `Local System` authenticates over the network as the
175
+computer account (`DOMAIN\COMPUTERNAME$`). Replace with your actual values
176
(e.g., `MYDOM\SQLBOX01$`).
177
178
```sql
@@ -170,19 +184,10 @@ CREATE USER [DOMAIN\COMPUTERNAME$] FOR LOGIN [DOMAIN\COMPUTERNAME$];
184
GRANT SELECT ON dbo.sysjobs TO [DOMAIN\COMPUTERNAME$];
185
```
186
173
-**Workgroup machine (no Active Directory, localhost only):**
174
-
175
-`Local System` authenticates as `NT AUTHORITY\SYSTEM`.
176
-This only works when SQL Server runs on the same machine.
177
-
178
-```sql
179
-CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS;
180
-GRANT VIEW SERVER STATE TO [NT AUTHORITY\SYSTEM];
181
-GRANT VIEW ANY DEFINITION TO [NT AUTHORITY\SYSTEM];
182
-USE msdb;
183
-CREATE USER [NT AUTHORITY\SYSTEM] FOR LOGIN [NT AUTHORITY\SYSTEM];
184
-GRANT SELECT ON dbo.sysjobs TO [NT AUTHORITY\SYSTEM];
185
-```
187
+For the default `Local System` service account, remote Windows Authentication works
188
+only on domain-joined machines, where it can authenticate as the computer account.
189
+In workgroups, use a different Windows service account if you need remote Windows
190
+Authentication.
191
192
> **Note**: To verify which account SQL Server sees, connect with Windows Authentication
193
> and run `SELECT SYSTEM_USER`.
@@ -286,7 +291,7 @@ Connect using Windows integrated authentication (Windows only).
291
292
When no username/password is provided in the DSN, the driver uses the Netdata service account's
293
Windows credentials. By default, the Netdata service runs as `Local System`, which authenticates
289
-to SQL Server as the computer account (`DOMAIN\COMPUTERNAME$`).
294
+to a local SQL Server as `NT AUTHORITY\SYSTEM`.
295
296
See the [Grant Windows Authentication access](#grant-windows-authentication-access-optional) prerequisite
297
to configure SQL Server for this.