MSSQL Install
Service Accounts
Virtual Account
MSA
gMSA
Low Privilege Domain Account
MSSQL Service Account
The MSSQL Service Account name should own the MS-SQL Service
The service account (in case of a local or AD account) and service SID should not be members of the Windows Administrators group.
SQL2008
(TODO Needs additional info)
New-ADUser -Name "SQL01_SVC" -Enabled $True -AccountPassword (ConvertTo-SecureString -AsPlainText "InitialPassword!!!" -Force)
SQL2012
(TODO Needs additional info)
New-ADServiceAccount -Name "SQL01_SVC" -DNSHostName "SQL01.mydomain.local" -Enabled $True
MSSQL Agent Service Account
The MSSQL Agent Service Account name should own the MS-SQL Agent Service
The service account (in case of a local or AD account) and service SID should not be members of the Windows Administrators group.
SQL2008
(TODO Needs additional info)
New-ADUser -Name "SQL01_Agent_SVC" -Enabled $True -AccountPassword (ConvertTo-SecureString -AsPlainText "InitPass!!!" -Force)
SQL2012
(TODO Needs additional info)
New-ADServiceAccount -Name "SQL01_Agent_SVC" -DNSHostName "SQL01.mydomain.local" -Enabled $True
Database Administrator Accounts
It is recommended to create a "DBA" AD Group and allocate users to that group as appropriate.
The example below creates a user, a group, and allocates the user to the group...Group Scope
UniversalAccounts from any domain in the same forestGlobal groups from any domain in the same forestOther Universal groups from any domain in the same forestGlobalAccounts from the same domainOther Global groups from the same domain
Domain LocalAccounts from any domain or any trusted domainGlobal groups from any domain or any trusted domainUniversal groups from any domain in the same forestOther Domain Local groups from the same domainAccounts, Global groups, and Universal groups from other forests and from external domains
Group Type
Security Groups enable assignment of rights and permissions to members of the groupDistribution groups can be used only with email applications to send email to collections of users. Instance Stacking
TL/DR; Don't do it. Use Virtualization instead.
Pros
Lower SQL Licesning Costs
Lower Windows Licensing Costs
Easier Windows Patching
https://www.brentozar.com/archive/2016/12/install-multiple-instances-sql-server/
Cons
Much harder performance tuning
Much harder reboot planning
Security challenges
On Linux, you can only have one instance per server.
On Windows you can have up to 50 standalone instances (reduced to 25 for Always On Failover Cluster Instances).
https://blogs.vmware.com/apps/2020/07/licensing-microsoft-sql-server-for-vmware-vsphere-part-one.html
Evaluation Edition Download Links
Bibliography & References
https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions(2) https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions?view=sql-server-ver16#stand-alone-server-or-domain-controller(4) https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions?view=sql-server-ver16#New_Accountshttps://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2012/ms143504(v=sql.110)(3) https://dba.stackexchange.com/questions/276454/whats-the-meaning-of-resources-external-to-the-sql-server-computer-are-neededhttps://docs.microsoft.com/en-gb/archive/blogs/psssql/sql-server-2012-setup-just-got-smarter
https://docs.microsoft.com/en-us/windows/security/identity-protection/access-control/active-directory-security-groups
Virtualisation(1) https://blogs.vmware.com/apps/2020/07/licensing-microsoft-sql-server-for-vmware-vsphere-part-one.htmlhttps://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/solutions/sql-server-on-vmware-best-practices-guide.pdf
Instance Stackinghttps://www.brentozar.com/archive/2016/12/install-multiple-instances-sql-server/
SQL2012Microsoft® SQL Server® 2008 Enterprise Evaluation: Trial Experience for IT Professionals