Share via

SQL Developer license

Bertellini, Luca 20 Reputation points
2026-06-11T11:41:06.2366667+00:00

I would like to request formal clarification regarding the permitted use of SQL Server Developer Edition in a specific customer environment scenario.

Context

We are designing and operating a non‑production environment with the following characteristics:

  • Used for:
    • Testing new software releases
      • Training activities
        • Workflow validation / process checks
        • Environment type:
          • Isolated from production systems
            • No dependency for business operations
            • Data usage:
              • No real business transactions are executed
                • No live operational data is processed for production purposes
                • Users:
                  • Internal users and potentially customer users (for training or acceptance testing only)

Key question

Can SQL Server Developer Edition be used in this type of environment, given that:

  • The environment is strictly non‑production
  • It is used only for testing, training, and validation purposes
  • It does not support real business operations or decision-making

Additional clarification requested

We would appreciate confirmation on the following points:

  1. Whether access by customer users (for training or acceptance testing) remains compliant
  2. Whether this scenario is still considered non‑production under Microsoft licensing terms
  3. Any specific restrictions or conditions we should be aware of to remain compliant

Request

We kindly ask for a written confirmation of the compliance of this usage scenario, as this will be used for internal documentation and audit purposes.I would like to request formal clarification regarding the permitted use of SQL Server Developer Edition in a specific customer environment scenario.

SQL Server Database Engine

Answer accepted by question author

Yitzhak Khabinsky 27,196 Reputation points
2026-06-11T13:25:10.66+00:00

Hi @Bertellini, Luca,

Microsoft has an official document that spells out where and under what circumstances SQL Server 2019 Developer edition could be installed and used.

It is any environment except a production:

  • Development
  • Test
  • User Acceptance Testing (UAT)

 

For the installed SQL Server 2019 Developer Edition, you can find its EULA with all details under:

C:\Program Files\Microsoft SQL Server\150\License Terms\SQLServer2019_License_DEV_1033.rtf

(for other versions the folder is slightly different)

Here is a relevant excerpt from the official Microsoft document:

User's image

I attached a similar file for the SQL Server 2025:
SQL_Server_2025_Developer_Express_and_Evaluation_Edition_English.pdf
SQL_Server_2025_Developer_Express_and_Evaluation_Edition_English.pdf

https://www.microsoft.com/content/dam/microsoft/usetm/documents/sql-server/sql-server-2025-developer%2C-express%2C-evaluation/retail/SQL_Server_2025_Developer_Express_and_Evaluation_Edition_English.pdf

Was this answer helpful?

1 person found this answer helpful.
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Bruce (SqlWork.com) 84,086 Reputation points
    2026-06-11T14:22:30.26+00:00

    As long as you don’t charge the customers for the training and don’t use any production data you should be ok. But this a user supported forum. you should check with your Microsoft support for a definitive answer.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-11T11:41:43.97+00:00

    SQL Server Developer Edition is licensed strictly for development, testing, and demonstration in non-production environments and cannot be used for any production workload.

    Based on the described scenario, the environment is compliant with the intended use of Developer Edition if all of the following conditions remain true:

    • It is technically and operationally non-production (no dependency for business operations, no impact if it is offline).
    • No real business transactions are executed there.
    • No live operational data is processed there for production purposes.
    • It is used only for development, testing, training, validation, or demonstration.

    Within that boundary, the following points apply from the provided material:

    1. Access by customer users (training / acceptance testing)
      • Developer Edition is allowed for testing and demonstration as long as the environment is non-production and not used to run real business operations or make real business decisions.
      • Customer or internal users may access such an environment for training or acceptance testing, provided their use does not turn the system into part of the production workflow (for example, no live orders, no real financial postings, no operational reporting relied on for day‑to‑day decisions).
      • If customer-facing use starts to resemble real operational use (for example, UAT that business relies on as part of a go‑live decision path or ongoing operational reporting), this becomes a grey area and may fall outside Developer Edition’s permitted use; in such cases, Microsoft licensing support or the customer’s Microsoft account representative must be consulted for an audit-safe determination.
    2. Whether this is still non‑production under Microsoft licensing terms
      • Developer Edition is described and used in practice as: free, full-featured, and “licensed only for development and test environments, not for production or serving real users.”
      • Moderator guidance confirms that:
        • Developer Edition is appropriate for dev/test/stage environments as long as they are used by developers and for testing new features, performance, troubleshooting, etc., and not as production.
        • Restoring production data into Developer Edition for developer troubleshooting is acceptable while the environment remains strictly non-production and not used by business users for operational purposes.
      • Another moderator clarification explicitly states that Developer Edition “remains non-production only, even if installed on the same VM/server as Standard or Enterprise” and that any use where it “supports or becomes part of a production workload path (even indirectly via integrations)” is outside permitted use.
      • Given the description (isolated, no business dependency, no real transactions, no live operational data used for production purposes), this environment fits the non‑production definition used in the provided guidance.
    3. Restrictions and conditions to remain compliant To stay within Developer Edition’s intended and permitted use in this scenario:
      • Ensure the environment is clearly designated and documented as non‑production (for internal governance and audits).
      • Do not allow it to:
        • Process real customer or financial transactions.
        • Feed data or services into production systems.
        • Provide reports or outputs that are relied on for real business decisions.
      • If production data is copied in for realistic testing, ensure the environment is still used only for development, testing, troubleshooting, training, or demonstration, and not by business users as a substitute for production.
      • In mixed-edition scenarios (Developer plus Standard/Enterprise on the same host), Developer Edition does not gain production rights; Standard/Enterprise instances must cover any production use, and Developer Edition must remain non‑production only.
      • For any edge cases such as:
        • Customer-facing UAT that directly drives go‑live approvals,
        • HA/DR, reporting, or integrations that participate in the production path, formal, audit-safe confirmation must be obtained from Microsoft licensing support or the customer’s Microsoft account team.

    The provided material supports using SQL Server Developer Edition in a strictly non‑production environment for development, testing, training, and validation, as described. However, only Microsoft’s licensing channels (Microsoft licensing support or account representative) can issue binding, organization-specific licensing confirmations.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.