(b) You may store instances of the server software and additional software on any of your servers or storage media. If you have users logging in so they can perform tests and validations, I don`t think that`s covered, unless you have some sort of MSDN license (also included in some Visual Studio subscription agreements) that grants you the license to use this and other MS software to test and develop applications.  LICENSOR: Indicate the total number of server licenses for which the end user is authorized under this Agreement. 5. THIRD PARTY NOTES. The software may contain third-party components with separate legal instructions or be subject to other agreements, as described in the ThirdPartyNotices file that is attached to the software. Even if these elements are governed by other agreements, subsequent exclusions of liability as well as subsequent limitations and exclusions of damages apply. As long as only licensed users have access to the software, customers may install an unlimited number of copies of the software on an unlimited number of servers used exclusively for development, testing, or demonstration purposes. This is important because it allows customers to run the software on multiple devices (e.g.B. for trial purposes) without having to license any production server system when the passive server provides data such as reports to customers or performs other “work”, including additional backups, it is considered active and requires its own license. Therefore, core-based licensing is usually cheaper for large organizations. The reseller used the wrong term, but you certainly bought the right licenses.
You`re good. 2.4 Running Instances of the Server Software. Your right to run instances of the server software depends on the option chosen to determine the number of software licenses required: www.microsoft.com/en-us/privacystatement/sqlserver/default.aspx A SQL server is also considered in production if it is connected to another database being produced or running in backup, or to allow a SQL server to produce disaster recovery. As you can imagine, mixing production and non-production environments is a recipe for disaster, as it can lead to hypercomplexity and compliance issues, especially if no access controls are put in place to prohibit use outside of development and testing. . . .