task_025_licence_and_version

Licence And Version

• stackoverflow.com » How do I find out what License has been applied to my SQL Server installation?

SELECT
 SERVERPROPERTY('MachineName') AS ComputerName,
 SERVERPROPERTY('ServerName') AS InstanceName,
 SERVERPROPERTY('Edition') AS Edition,
 SERVERPROPERTY('ProductVersion') AS ProductVersion,
 SERVERPROPERTY('ProductLevel') AS ProductLevel;
GO

ComputerName	InstanceName	Edition	ProductVersion	ProductLevel
sqlEnterprise	sqlEnterprise	Enterprise Edition (64-bit)	16.0.4075.1	RTM

---

MSSQL

• Quickstart: Run SQL Server Linux container images with Docker
• SQL Server on Linux Frequently Asked Questions (FAQ)
• Installation guidance for SQL Server on Linux
• Configure SQL Server settings with environment variables on Linux
• Deploy and connect to SQL Server Linux containers
• Sample: Unattended SQL Server installation script for SUSE Linux Enterprise Server
• microsoft.com » 2019 » product-licencing/sql-server » Go to the bottom resources section to download the pdf guide
• serverfault.com » How can I check if SQL Server 2019 Standard is activated on Server Core?
• serverfault.com » Can you help me with my software licensing issue?
• reddit.com » Is there a way to verify the number of CALs on my SQL Server Standard 2019?

Reddit Threads

• reddit.com » SQL Server Developer Edition Question
• www.brentozar.com » Microsoft SQL Server Licensing Simplified into 7 Rules
• reddit.com » Developer Edition using Prod domain/vlan
• reddit.com » MS Sql Server - What is "production" data?
• reddit.com » Developer Edition Time Limit?

Other Threads

• learn.microsoft.com » How To Check SQL Server Activation With Valid Key
• quora.com » How do I check if the MS SQL server licenses are valid?

Docker Commands

The Docker run command for SQL Server involves specifying the edition you want to use through the MSSQL_PID environment variable. Below are the Docker run commands for various editions of SQL Server:

1. Enterprise Edition

docker run --rm \
-e "ACCEPT_EULA=Y" \
-e "MSSQL_SA_PASSWORD=Password12345" \
-e "MSSQL_PID=Enterprise" \
-e "MSSQL_AGENT_ENABLED=1" \
-p 1433:1433 --name sqlEnterprise --hostname sqlEnterprise \
-d mcr.microsoft.com/mssql/server:2022-latest

2. Standard Edition

docker run --rm \
-e "ACCEPT_EULA=Y" \
-e "MSSQL_SA_PASSWORD=Password12345" \
-e "MSSQL_PID=Standard" \
-e "MSSQL_AGENT_ENABLED=1" \
-p 1433:1433 --name sqlStandard --hostname sqlStandard \
-d mcr.microsoft.com/mssql/server:2022-latest

3. Express Edition

docker run --rm \
-e "ACCEPT_EULA=Y" \
-e "MSSQL_SA_PASSWORD=Password12345" \
-e "MSSQL_PID=Express" \
-e "MSSQL_AGENT_ENABLED=1" \
-p 1433:1433 --name sqlExpress --hostname sqlExpress \
-d mcr.microsoft.com/mssql/server:2022-latest

4. Developer Edition

docker run --rm \
-e "ACCEPT_EULA=Y" \
-e "MSSQL_SA_PASSWORD=Password12345" \
-e "MSSQL_PID=Developer" \
-e "MSSQL_AGENT_ENABLED=1" \
-p 1433:1433 --name sqlDeveloper --hostname sqlDeveloper \
-d mcr.microsoft.com/mssql/server:2022-latest

Notes

• Ensure to replace "Password12345" with a strong password as per your security guidelines.
• The MSSQL_PID environment variable is used to specify the edition of SQL Server to run.
• Ensure that you comply with licensing terms for the edition you are using, especially for production use.
• Always store sensitive data like passwords securely, consider using Docker secrets or environment variable files instead of hard-coding them into your commands or scripts.
• Ensure that the port 1433 is not being used by another service on your host machine.
• For production deployments, consider additional configuration for security, data persistence, and performance tuning.

Always refer to the official Microsoft documentation for the most accurate and up-to-date information.