SQL Server 2016 SP1: Know your limits

Published Mar 23 2019 03:18 PM 5,562 Views

First published on MSDN on Dec 09, 2016
With the recent announcement of SQL Server 2016 SP1 , we announced the consistent programmability experience (CPSA) for developers and ISVs, who can now maintain a single code base and build intelligent database applications which scale across all the editions of SQL Server. The processor, memory and database size limits does not change and remain as–in all editions as documented in the SQL Server editions page . We have made the following changes in our documentation to accurately reflect the memory limits on lower editions of SQL Server. This blog post is intended to clarify and provide more information on the memory limits starting with SQL Server 2016 SP1 on Standard, Web and Express Editions of SQL Server.


Features   SQL Server 2016 SP1 Enterprise SQL Server 2016 SP1 Standard SQL Server 2016 SP1 Web SQL Server 2016 SP1 Express SQL Server 2016 SP1 Developer
Scale Maximum number of cores Unlimited 24 cores 16 cores 4 cores Unlimited
  Memory: Maximum memory utilized per instance buffer pool size per instance Operating system max 128 GB 64 GB 1410 MB Operating system max
*(NEW) Memory: Maximum columnstore cache Operating system max 32 GB 16 GB 352 MB Operating system max
*(NEW) Memory: Maximum in-memory data Operating system max 32 GB 16 GB 352 MB Operating system max
  Maximum database size 524 PB 524 PB 524 PB 10 GB 524 PB

 

Understanding the Memory limits for lower editions of SQL Server

In the past, the memory limits defined in table above in the SQL Server editions page for lower editions were referred to as Maximum memory utilized per instance which did not accurately reflect the true limits. The memory limit defined for lower editions of SQL Server is essentially Maximum buffer pool memory limit . In simpler terms, buffer pool memory in SQL Server is a memory cache responsible for caching data and index pages for the entire instance. The rest of the caches in the SQL Server memory (procedure cache, thread stack, backup buffers etc) consumes memory outside buffer pool memory. The memory consumed by caches outside buffer pool is not restricted by above memory limits and can grow up to limits defined by "max server memory". This is not specific to SQL Server 2016 SP1 and is also applicable to earlier releases of SQL Server as well.

Essentially, SQL Server in lower editions can consume and utilize memory outside the maximum buffer pool memory limit defined in the table above due to memory consumed by other caches.

What changed in SQL Server 2016 SP1?

On all lower editions of SQL Server 2016 starting with SP1, we have memory quota limits for In-Memory OLTP data and Columnstore segment cache which is in addition to the maximum buffer pool memory limits described earlier. The following table lists those limits:



The limits for In-Memory OLTP data is per database. If you would like to estimate memory size required for your data, please refer to Estimate Memory Requirements for Memory-Optimized Tables.

The limits for Columnstore segment cache is per SQL Server instance across all the databases in the instance.

Like earlier versions of SQL Server, there are still no quota limits defined for caches other than buffer pool, In-Memory OLTP data and Columnstore segment cache. The memory consumed by other caches will still be solely restricted by max server memory (if capped) on SQL Server or memory on the server if max server memory is uncapped.

For example: A Standard Edition of SQL Server has buffer pool memory limited to 128GB, so the data and index pages cached in buffer pool is limited by 128GB. Starting with SQL Server 2016 SP1, you can have an additional 32GB of memory for Columnstore segment cache per instance and an additional 32GB of memory quota for In-Memory OLTP per database . In addition, there can be memory consumed by other memory consumers in SQL Server which will be limited by "max server memory" or total memory on the server if max server memory is uncapped.

Although the buffer pool, In-Memory OLTP data and Columnstore segments memory are restricted by memory quota in lower editions, if the max server memory is capped lower than the limits defined earlier, SQL Server will honor the max server memory limits defined on the instance.

Enterprise Edition of SQL Server

SQL Server Enterprise Edition continues to be our highly differentiated edition of SQL Server when customers are ready to take their business to the next level where performance, scale and availability of the database is important.

For Enterprise Edition of SQL Server, there are no processor, memory, virtualization or scale limitations as defined in SQL Server editions page . With Windows Server 2016, SQL Server 2016 now supports up to 24TB, 128TB VAS space and 512 logical processors . The following table lists the new logical processor and memory limits supported by Windows Server 2016. For more details on Windows Server 2016 scale limits, please refer to our Windows Server blog .



The following Error log captured from Windows Server 2016 with 24TB of RAM and 16 sockets with 24 cores per socket (384 Logical processors) shows how SQL Server 2016 scales with Windows Server 2016.

2016-09-08 08:25:28.73 Server      Microsoft SQL Server 2016 (SP1-CTP) - 13.0.3645.0 (X64)
Apr 29 2016 23:23:58
Copyright (c) Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows Server 2016 Datacenter 6.3 <X64> (Build 14393: )
2016-09-08 08:25:28.73 Server      UTC adjustment: -7:00
2016-09-08 08:25:28.74 Server      (c) Microsoft Corporation.
2016-09-08 08:25:28.74 Server      All rights reserved.
2016-09-08 08:25:28.74 Server      Server process ID is 14864.
2016-09-08 08:25:28.74 Server      Authentication mode is MIXED.
2016-09-08 08:25:28.74 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-09-08 08:25:28.75 Server      The service account is 'SQL\Administrator'. This is an informational message; no user action is required.
2016-09-08 08:25:28.75 Server      Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
-T 834
2016-09-08 08:25:28.78 Server SQL Server detected 16 sockets with 24 cores per socket and 24 logical processors per socket, 384 total logical processors; using 384 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-09-08 08:25:28.78 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-09-08 08:25:28.78 Server Detected 25165643 MB of RAM. This is an informational message; no user action is required.
2016-09-08 08:25:28.78 Server      Using large pages in the memory manager.

For detailed feature differentiation across editions of SQL Server 2016 SP1, please refer to Editions and Supported Features for SQL Server.

SQL Server 2016 SP1 is a preferred choice of database engine for businesses of all sizes. If you are Developer/ISV, you can start developing on free Developer Edition of SQL Server 2016. If you are a small business, you can start with the free Express Edition of SQL Server. As your business grows and perf, scale and availability requirements of database grows, you can upgrade to Standard Edition of SQL Server. When running mission critical OLTP workloads, high velocity IOT transactions, and high volume data warehousing with advanced analytics, you can choose to upgrade to Enterprise Edition of SQL Server with Windows Server 2016 on modern hardware or migrate to Azure .

These are exciting times to be part of the SQL Server journey which supports businesses of all sizes and allows developers/ISVs to build applications which scale across all editions and cloud. SQL Server v.Next further allows customers to deploy SQL Server on the platform of their choice: Linux, Windows, Docker, on-premises or in the cloud.

Parikshit Savjani
Senior Program Manager (@talktosavjani )

%3CLINGO-SUB%20id%3D%22lingo-sub-385012%22%20slang%3D%22en-US%22%3ESQL%20Server%202016%20SP1%3A%20Know%20your%20limits%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-385012%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EFirst%20published%20on%20MSDN%20on%20Dec%2009%2C%202016%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3EWith%20the%20recent%20announcement%20of%20%3CA%20href%3D%22https%3A%2F%2Fblogs.msdn.microsoft.com%2Fsqlreleaseservices%2Fsql-server-2016-service-pack-1-sp1-released%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20SQL%20Server%202016%20SP1%20%3C%2FA%3E%20%2C%20we%20announced%20the%20%3CSTRONG%3E%20consistent%20programmability%20experience%20%3C%2FSTRONG%3E(CPSA)%20for%20developers%20and%20ISVs%2C%20who%20can%20now%20maintain%20a%20single%20code%20base%20and%20build%20intelligent%20database%20applications%20which%20scale%20across%20all%20the%20editions%20of%20SQL%20Server.%20The%20processor%2C%20memory%20and%20database%20size%20limits%20does%20not%20change%20and%20remain%20as%E2%80%93in%20all%20editions%20as%20documented%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsql-server%2Fsql-server-editions%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20SQL%20Server%20editions%20page%20%3C%2FA%3E%20.%20We%20have%20made%20the%20following%20changes%20in%20our%20documentation%20to%20accurately%20reflect%20the%20memory%20limits%20on%20lower%20editions%20of%20SQL%20Server.%20This%20blog%20post%20is%20intended%20to%20clarify%20and%20provide%20more%20information%20on%20the%20memory%20limits%20starting%20with%20SQL%20Server%202016%20SP1%20on%20Standard%2C%20Web%20and%20Express%26nbsp%3BEditions%20of%20SQL%20Server.%3C%2FP%3E%0A%3CDIV%3E%3CBR%20%2F%3E%3CTABLE%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3E%20Features%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%26nbsp%3B%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3E%20SQL%20Server%202016%20SP1%20Enterprise%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3E%20SQL%20Server%202016%20SP1%20Standard%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3E%20SQL%20Server%202016%20SP1%20Web%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3E%20SQL%20Server%202016%20SP1%20Express%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3E%20SQL%20Server%202016%20SP1%20Developer%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3EScale%3C%2FTD%3E%0A%3CTD%3EMaximum%20number%20of%20cores%3C%2FTD%3E%0A%3CTD%3EUnlimited%3C%2FTD%3E%0A%3CTD%3E24%20cores%3C%2FTD%3E%0A%3CTD%3E16%20cores%3C%2FTD%3E%0A%3CTD%3E4%20cores%3C%2FTD%3E%0A%3CTD%3EUnlimited%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%26nbsp%3B%3C%2FTD%3E%0A%3CTD%3EMemory%3A%20Maximum%20memory%20utilized%20per%20instance%20buffer%20pool%20size%20per%20instance%3C%2FTD%3E%0A%3CTD%3EOperating%20system%20max%3C%2FTD%3E%0A%3CTD%3E128%20GB%3C%2FTD%3E%0A%3CTD%3E64%20GB%3C%2FTD%3E%0A%3CTD%3E1410%20MB%3C%2FTD%3E%0A%3CTD%3EOperating%20system%20max%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E*(NEW)%3C%2FTD%3E%0A%3CTD%3EMemory%3A%20Maximum%20columnstore%20cache%3C%2FTD%3E%0A%3CTD%3EOperating%20system%20max%3C%2FTD%3E%0A%3CTD%3E32%20GB%3C%2FTD%3E%0A%3CTD%3E16%20GB%3C%2FTD%3E%0A%3CTD%3E352%20MB%3C%2FTD%3E%0A%3CTD%3EOperating%20system%20max%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E*(NEW)%3C%2FTD%3E%0A%3CTD%3EMemory%3A%20Maximum%20in-memory%20data%3C%2FTD%3E%0A%3CTD%3EOperating%20system%20max%3C%2FTD%3E%0A%3CTD%3E32%20GB%3C%2FTD%3E%0A%3CTD%3E16%20GB%3C%2FTD%3E%0A%3CTD%3E352%20MB%3C%2FTD%3E%0A%3CTD%3EOperating%20system%20max%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%26nbsp%3B%3C%2FTD%3E%0A%3CTD%3EMaximum%20database%20size%3C%2FTD%3E%0A%3CTD%3E524%20PB%3C%2FTD%3E%0A%3CTD%3E524%20PB%3C%2FTD%3E%0A%3CTD%3E524%20PB%3C%2FTD%3E%0A%3CTD%3E10%20GB%3C%2FTD%3E%0A%3CTD%3E524%20PB%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C%2FDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1505565489%22%20id%3D%22toc-hId-1505565489%22%3EUnderstanding%20the%20Memory%20limits%20for%20lower%20editions%20of%20SQL%20Server%3C%2FH3%3E%0A%3CP%3EIn%20the%20past%2C%20the%20memory%20limits%20defined%20in%20table%20above%20in%20the%20SQL%20Server%20editions%20page%20for%20lower%20editions%20were%20referred%20to%20as%20Maximum%20memory%20utilized%20per%20instance%20which%20did%20not%20accurately%20reflect%20the%20true%20limits.%20The%20memory%20limit%20defined%20for%20lower%20editions%20of%20SQL%20Server%20is%20essentially%20Maximum%20buffer%20pool%20memory%20limit%20.%20In%20simpler%20terms%2C%20buffer%20pool%20memory%20in%20SQL%20Server%20is%20a%20memory%20cache%20responsible%20for%20caching%20data%20and%20index%20pages%20for%20the%20entire%20instance.%20The%20rest%20of%20the%20caches%20in%20the%20SQL%20Server%20memory%20(procedure%20cache%2C%20thread%20stack%2C%20backup%20buffers%20etc)%20consumes%20memory%20outside%20buffer%20pool%20memory.%20The%20memory%20consumed%20by%20caches%20outside%20buffer%20pool%20is%20not%20restricted%20by%20above%20memory%20limits%20and%20can%20grow%20up%20to%20limits%20defined%20by%20%22max%20server%20memory%22.%20This%20is%20not%20specific%20to%20SQL%20Server%202016%20SP1%20and%20is%20also%20applicable%20to%20earlier%20releases%20of%20SQL%20Server%20as%20well.%20%3CBR%20%2F%3E%3CBR%20%2F%3EEssentially%2C%20SQL%20Server%20in%20lower%20editions%20can%20consume%20and%20utilize%20memory%20outside%20the%20maximum%20buffer%20pool%20memory%20limit%20defined%20in%20the%20table%20above%20due%20to%20memory%20consumed%20by%20other%20caches.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1046591472%22%20id%3D%22toc-hId--1046591472%22%3EWhat%20changed%20in%20SQL%20Server%202016%20SP1%3F%3C%2FH3%3E%0A%3CP%3EOn%20all%20lower%20editions%20of%20SQL%20Server%202016%20starting%20with%20SP1%2C%20we%20have%20memory%20quota%20limits%20for%20In-Memory%20OLTP%20data%20and%20Columnstore%20segment%20cache%20which%20is%20in%20addition%20to%20the%20maximum%20buffer%20pool%20memory%20limits%20described%20earlier.%20The%20following%20table%20lists%20those%20limits%3A%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20535px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F98211i8262A1F65BDED561%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20limits%20for%20In-Memory%20OLTP%20data%20is%20%3CSTRONG%3E%20per%20database.%20%3C%2FSTRONG%3E%20If%20you%20would%20like%20to%20estimate%20memory%20size%20required%20for%20your%20data%2C%20please%20refer%20to%20%3CA%20href%3D%22https%3A%2F%2Fmsdn.microsoft.com%2Flibrary%2Fdn282389.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20Estimate%20Memory%20Requirements%20for%20Memory-Optimized%20Tables.%20%3C%2FA%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20limits%20for%20Columnstore%20segment%20cache%20is%20%3CSTRONG%3E%20per%20SQL%20Server%20instance%20%3C%2FSTRONG%3E%20across%20all%20the%20databases%20in%20the%20instance.%20%3CBR%20%2F%3E%3CBR%20%2F%3ELike%20earlier%20versions%20of%20SQL%20Server%2C%20there%20are%20still%20no%20quota%20limits%20defined%20for%20caches%20other%20than%20buffer%20pool%2C%20In-Memory%20OLTP%20data%20and%20Columnstore%20segment%20cache.%20The%20memory%20consumed%20by%20other%20caches%20will%20still%20be%20solely%20restricted%20by%20max%20server%20memory%20(if%20capped)%20on%20SQL%20Server%20or%20memory%20on%20the%20server%20if%20max%20server%20memory%20is%20uncapped.%20%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20example%3A%20A%20Standard%20Edition%20of%20SQL%20Server%20has%20buffer%20pool%20memory%20limited%20to%20128GB%2C%20so%20the%20data%20and%20index%20pages%20cached%20in%20buffer%20pool%20is%20limited%20by%20128GB.%20Starting%20with%20SQL%20Server%202016%20SP1%2C%20you%20can%20have%20an%20%3CSTRONG%3E%20additional%2032GB%20%3C%2FSTRONG%3E%20of%20memory%20for%20%3CSTRONG%3E%20Columnstore%20segment%20cache%20per%20instance%20%3C%2FSTRONG%3E%20and%20%3CSTRONG%3E%20an%20additional%2032GB%20%3C%2FSTRONG%3E%20of%20memory%20quota%20for%20%3CSTRONG%3E%20In-Memory%20OLTP%20per%20database%20%3C%2FSTRONG%3E%20.%20In%20addition%2C%20there%20can%20be%20memory%20consumed%20by%20other%20memory%20consumers%20in%20SQL%20Server%20which%20will%20be%20limited%20by%20%22max%20server%20memory%22%20or%20total%20memory%20on%20the%20server%20if%20max%20server%20memory%20is%20uncapped.%20%3CBR%20%2F%3E%3CBR%20%2F%3EAlthough%20the%20buffer%20pool%2C%20In-Memory%20OLTP%20data%20and%20Columnstore%20segments%20memory%20are%20restricted%20by%20memory%20quota%20in%20lower%20editions%2C%20if%20the%20max%20server%20memory%20is%20capped%20lower%20than%20the%20limits%20defined%20earlier%2C%20SQL%20Server%20will%20honor%20the%20max%20server%20memory%20limits%20defined%20on%20the%20instance.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-696218863%22%20id%3D%22toc-hId-696218863%22%3EEnterprise%20Edition%20of%20SQL%20Server%3C%2FH3%3E%0A%3CP%3ESQL%20Server%20Enterprise%20Edition%20continues%20to%20be%20our%20highly%20differentiated%20edition%20of%20SQL%20Server%20when%20customers%20are%20ready%20to%20take%20their%20business%20to%20the%20next%20level%20where%20performance%2C%20scale%20and%20availability%20of%20the%20database%20is%20important.%20%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20Enterprise%20Edition%20of%20SQL%20Server%2C%20there%20are%20no%20processor%2C%20memory%2C%20virtualization%20or%20scale%20limitations%20as%20defined%20in%20SQL%20Server%20editions%20page%20.%20With%20Windows%20Server%202016%2C%20SQL%20Server%202016%20now%20supports%20up%20to%2024TB%2C%20128TB%20VAS%20space%20and%20512%20logical%20processors%20.%20The%20following%20table%20lists%20the%20new%20logical%20processor%20and%20memory%20limits%20supported%20by%20Windows%20Server%202016.%20For%20more%20details%20on%20Windows%20Server%202016%20scale%20limits%2C%20please%20refer%20to%20our%20Windows%20Server%20blog%20.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20988px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F98212i13D3C2874B2AB553%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20following%20Error%20log%20captured%20from%20Windows%20Server%202016%20with%2024TB%20of%20RAM%20and%2016%20sockets%20with%2024%20cores%20per%20socket%20(384%20Logical%20processors)%20shows%20how%20SQL%20Server%202016%20scales%20with%20Windows%20Server%202016.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.73%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Microsoft%20SQL%20Server%202016%20(SP1-CTP)%20-%2013.0.3645.0%20(X64)%20%3CBR%20%2F%3EApr%2029%202016%2023%3A23%3A58%20%3CBR%20%2F%3ECopyright%20(c)%20Microsoft%20Corporation%20%3CBR%20%2F%3EEnterprise%20Evaluation%20Edition%20(64-bit)%20on%20Windows%20Server%202016%20Datacenter%206.3%20%3CX64%3E%20(Build%2014393%3A%20)%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.73%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20UTC%20adjustment%3A%20-7%3A00%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.74%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20(c)%20Microsoft%20Corporation.%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.74%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20All%20rights%20reserved.%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.74%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Server%20process%20ID%20is%2014864.%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.74%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Authentication%20mode%20is%20MIXED.%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.74%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Logging%20SQL%20Server%20messages%20in%20file%20'C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5CMSSQL13.MSSQLSERVER%5CMSSQL%5CLog%5CERRORLOG'.%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.75%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20The%20service%20account%20is%20'SQL%5CAdministrator'.%20This%20is%20an%20informational%20message%3B%20no%20user%20action%20is%20required.%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.75%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Registry%20startup%20parameters%3A%20%3CBR%20%2F%3E-d%20C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5CMSSQL13.MSSQLSERVER%5CMSSQL%5CDATA%5Cmaster.mdf%20%3CBR%20%2F%3E-e%20C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5CMSSQL13.MSSQLSERVER%5CMSSQL%5CLog%5CERRORLOG%20%3CBR%20%2F%3E-l%20C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5CMSSQL13.MSSQLSERVER%5CMSSQL%5CDATA%5Cmastlog.ldf%20%3CBR%20%2F%3E-T%20834%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.78%20Server%20%3CSTRONG%3E%20SQL%20Server%20detected%2016%20sockets%20with%2024%20cores%20per%20socket%20and%2024%20logical%20processors%20per%20socket%2C%20384%20total%20logical%20processors%3B%20using%20384%20logical%20processors%20based%20on%20SQL%20Server%20licensing.%20This%20is%20an%20informational%20message%3B%20no%20user%20action%20is%20required.%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.78%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20SQL%20Server%20is%20starting%20at%20normal%20priority%20base%20(%3D7).%20This%20is%20an%20informational%20message%20only.%20No%20user%20action%20is%20required.%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.78%20Server%20Detected%2025165643%20MB%20of%20RAM.%20%20This%20is%20an%20informational%20message%3B%20no%20user%20action%20is%20required.%20%3CBR%20%2F%3E2016-09-08%2008%3A25%3A28.78%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Using%20large%20pages%20in%20the%20memory%20manager.%20%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20detailed%20feature%20differentiation%20across%20editions%20of%20SQL%20Server%202016%20SP1%2C%20please%20refer%20to%20Editions%20and%20Supported%20Features%20for%20SQL%20Server.%20%20%3CBR%20%2F%3E%3CBR%20%2F%3ESQL%20Server%202016%20SP1%20is%20a%20preferred%20choice%20of%20database%20engine%20for%20businesses%20of%20all%20sizes.%20If%20you%20are%20Developer%2FISV%2C%20you%20can%20start%20developing%20on%20free%20Developer%20Edition%20of%20SQL%20Server%202016.%20If%20you%20are%20a%20small%20business%2C%20you%20can%20start%20with%20the%20free%20Express%20Edition%20of%20SQL%20Server.%20As%20your%20business%20grows%20and%20perf%2C%20scale%20and%20availability%20requirements%20of%20database%20grows%2C%20you%20can%20upgrade%20to%20Standard%20Edition%20of%20SQL%20Server.%20When%20running%20mission%20critical%20OLTP%20workloads%2C%20high%20velocity%20IOT%20transactions%2C%20and%20high%20volume%20data%20warehousing%20with%20advanced%20analytics%2C%20you%20can%20choose%20to%20upgrade%20to%20Enterprise%20Edition%20of%20SQL%20Server%20with%20Windows%20Server%202016%20on%20modern%20hardware%20or%20migrate%20to%20Azure%20.%20%3CBR%20%2F%3E%3CBR%20%2F%3EThese%20are%20exciting%20times%20to%20be%20part%20of%20the%20SQL%20Server%20journey%20which%20supports%20businesses%20of%20all%20sizes%20and%20allows%20developers%2FISVs%20to%20build%20applications%20which%20scale%20across%20all%20editions%20and%20cloud.%20SQL%20Server%20v.Next%20further%20allows%20customers%20to%20deploy%20SQL%20Server%20on%20the%20platform%20of%20their%20choice%3A%20Linux%2C%20Windows%2C%20Docker%2C%20on-premises%20or%20in%20the%20cloud.%20%3CBR%20%2F%3E%3CBR%20%2F%3EParikshit%20Savjani%20%3CBR%20%2F%3ESenior%20Program%20Manager%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Ftalktosavjani%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%20(%40talktosavjani%20%3C%2FA%3E%20)%3C%2FX64%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-385012%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20published%20on%20MSDN%20on%20Dec%2009%2C%202016%20With%20the%20recent%20announcement%20of%20SQL%20Server%202016%20SP1%2C%20we%20announced%20the%20consistent%20programmability%20experience%20for%20developers%20and%20ISVs%2C%20who%20can%20now%20maintain%20a%20single%20code%20base%20and%20build%20intelligent%20database%20applications%20which%20scale%20across%20all%20the%20editions%20of%20SQL%20Server.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-385012%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESQLServerTiger%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Apr 19 2019 03:02 PM
Updated by: