In this article I think the next Summary SQL Server 2014 introduced a variety of stunning performance! !
Buffer pool extensions (Buffer Pool Extensions)
Buffer pool expansion idea is very simple: put on a very fast storage, such as SSD hard disk, to extend the buffer pool page files are stored. Buffer pool expansion is more convenient, if you add more memory on the database server can not give you physical, consider using the extended buffer pool.
Resource Governor (Resource Governor)
Resource Governor first introduced in SQL Server 2008 years, but that time is not yet a mature technology, because you can not regulate the storage level I / O operations for a given workload group, you can not limit the size of the buffer pool. In SQL Server 2014 where these have changed, because now you can suppress I / O operations. Buffer pool usage restrictions or not, but who knows what will happen in the SQL Server 2016 in it :).
Lock priority (Lock Priorities)
Perhaps you already know, in the enterprise version, SQL Server provides you online operation, or I can call them "near-line operation." They almost are online, because the internal SQL Server or to get some locks, which can cause obstruction. Therefore, SQL Server 2014 introduces a lock priority , where if this happens, you can control how to deal with SQL Server.
Gather column store index (Clustered Column Store Indexes)
In the most popular upgrade SQL Server 2014 is introduced in aggregate column store indexes in SQL Server, it is the amazing new way to process data stored in the column. Otherwise accumulate column store index will directly change - do not like to switch partitions such skills.
Memory optimization table (In-Memory OLTP)
Use memory optimization table Microsoft claims that your workload performance can increase 100 times. Diao ye cool days! Now everything is stored directly in memory, you will not involve physical storage (including the transaction log, if you want it). In addition to optimize memory table based on the so-called lock-free data structures, which means the lock, blocking, latch, lock rotation all disappeared. Of course, this approach is promising there are side effects, there are limits ......
Deferred transaction (Delayed Transactions)
Your workload productivity no matter how good each of the last obstacles and bottlenecks are transaction logs. Because SQL Server uses a pre-written to the log mechanism (Write-Ahead Logging mechanism), before the transaction is committed, the transaction must always physically written to the transaction log. But your transaction log on a slow memory, your performance and productivity will be hurt. Therefore, SQL Server enables so-called deferred transaction ......
Computing base (Cardinality Estimation)
In a relational database, calculated on the basis is the most important thing, because these will flow calculation base query optimizer, its job is to generate enough good execution plan. In SQL Server 2014, Microsoft completely rewritten in a very important component in the calculation base to overcome some of the limitations, this has always been based on yes.
Reference article:
https://www.sqlpassion.at/archive/2014/03/18/performance-improvements-in-sql-server-2014/
Note: This article is WoodyTu learning MS SQL technology, collect and collate the relevant documentation writers, welcome to reprint, please give this article link in the apparent position of the article page!
If you found this article pretty good, please click the bottom right corner under recommendation , with your support in order to inspire greater enthusiasm for writing author, thank you very much!
solution:
all programs -SQL Server 2008- configuration tool - "SQL Server configuration Manager", click "SQL Server 2008 service" right 'properties' -> 'Log on tab' built-in account select "Local System", click on OK to restart.
In this article I think the next Summary SQL Server 2014 introduced a variety of stunning performance! !
Buffer pool extensions (Buffer Pool Extensions)
Buffer pool expansion idea is very simple: put on a very fast storage, such as SSD hard disk, to extend the buffer pool page files are stored. Buffer pool expansion is more convenient, if you add more memory on the database server can not give you physical, consider using the extended buffer pool.
Resource Governor (Resource Governor)
Resource Governor first introduced in SQL Server 2008 years, but that time is not yet a mature technology, because you can not regulate the storage level I / O operations for a given workload group, you can not limit the size of the buffer pool. In SQL Server 2014 where these have changed, because now you can suppress I / O operations. Buffer pool usage restrictions or not, but who knows what will happen in the SQL Server 2016 in it :).
Lock priority (Lock Priorities)
Perhaps you already know, in the enterprise version, SQL Server provides you online operation, or I can call them "near-line operation." They almost are online, because the internal SQL Server or to get some locks, which can cause obstruction. Therefore, SQL Server 2014 introduces a lock priority , where if this happens, you can control how to deal with SQL Server.
Gather column store index (Clustered Column Store Indexes)
In the most popular upgrade SQL Server 2014 is introduced in aggregate column store indexes in SQL Server, it is the amazing new way to process data stored in the column. Otherwise accumulate column store index will directly change - do not like to switch partitions such skills.
Memory optimization table (In-Memory OLTP)
Use memory optimization table Microsoft claims that your workload performance can increase 100 times. Diao ye cool days! Now everything is stored directly in memory, you will not involve physical storage (including the transaction log, if you want it). In addition to optimize memory table based on the so-called lock-free data structures, which means the lock, blocking, latch, lock rotation all disappeared. Of course, this approach is promising there are side effects, there are limits ......
Deferred transaction (Delayed Transactions)
Your workload productivity no matter how good each of the last obstacles and bottlenecks are transaction logs. Because SQL Server uses a pre-written to the log mechanism (Write-Ahead Logging mechanism), before the transaction is committed, the transaction must always physically written to the transaction log. But your transaction log on a slow memory, your performance and productivity will be hurt. Therefore, SQL Server enables so-called deferred transaction ......
Computing base (Cardinality Estimation)
In a relational database, calculated on the basis is the most important thing, because these will flow calculation base query optimizer, its job is to generate enough good execution plan. In SQL Server 2014, Microsoft completely rewritten in a very important component in the calculation base to overcome some of the limitations, this has always been based on yes.
Reference article:
https://www.sqlpassion.at/archive/2014/03/18/performance-improvements-in-sql-server-2014/