# Choose parallel or fallback destinations for NPS accounting

> Should NPS write accounting records to both SQL and text, or use text only after SQL failure?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-105-choose-parallel-or-fallback-destinations-for-nps-accounting/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:15:26+00:00
- Modified: 2026-09-08T18:23:26+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

Should NPS write accounting records to both SQL and text, or use text only after SQL failure?

## Potentially affected

Administrators configuring Network Policy Server accounting destinations.

## DSE recommendation

Have the authentication and database teams agree on the selected mode and ownership of failure alerts.

## Article

## Source facts

NPS can record accounting for authentication requests, acceptance and rejection messages, accounting exchanges, and periodic status updates. Microsoft offers text-only and SQL-only destinations, as well as two combined modes. Parallel logging writes to both destinations simultaneously. SQL logging with backup uses the text destination if SQL logging fails. NPS event logging is a separate facility used principally to audit and troubleshoot connection attempts. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-accounting-configure).

## Applicability

Identify the accounting consumers, selected destination, database owner, retention requirements, and handling rules. Distinguish a requirement for simultaneous copies from a requirement for a fallback during a database outage.

## DSE recommendation

Have the authentication and database teams agree on the selected mode and ownership of failure alerts. Document where operators should look for records during normal operation and during a logging failure. Review destination access and capacity before enabling the chosen accounting path.

## Verification

Generate controlled accepted and rejected connection attempts and reconcile their timestamps with the expected records. In an approved test, make the SQL destination unavailable and inspect the documented fallback behavior. Record missing events or ambiguous destination ownership before relying on the accounting collection for investigations.

## Official references

[Microsoft Learn: Configure Network Policy Server Accounting](https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-accounting-configure). Source reviewed September 8, 2026.

## Primary reference

- Name: Configure Network Policy Server Accounting
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-accounting-configure
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose parallel or fallback destinations for NPS accounting,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-105-choose-parallel-or-fallback-destinations-for-nps-accounting/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.