在 SQL Server 2014 中引入了本機(jī)編譯的存儲(chǔ)過程這一特性,而在 SQL Server 2016 中,我們將能夠?qū)崿F(xiàn)標(biāo)量用戶自定義函數(shù)(Scalar
在 SQL Server 2014 中引入了本機(jī)編譯的存儲(chǔ)過程這一特性,而在 SQL Server 2016 中,我們將能夠?qū)崿F(xiàn)標(biāo)量用戶自定義函數(shù)(Scalar UDF)的本機(jī)編譯(Natively Compilation)。
SQL Sever 會(huì)將標(biāo)準(zhǔn)的T-SQL 語句編譯為一種專有的中間語言,并在運(yùn)行時(shí)對(duì)此中間語言進(jìn)行解釋。而在本機(jī)編譯的情況下,存儲(chǔ)過程將轉(zhuǎn)換為C代碼并編譯到一個(gè) DLL 中,SQL Server 會(huì)在運(yùn)行時(shí)使用這個(gè) DLL 文件。
現(xiàn)在,Scalar UDF 也能夠以類似的方式編譯為機(jī)器代碼了。對(duì)于簡(jiǎn)單的操作來說,這一過程會(huì)極大地改善它的性能。只要是普通的 Scalar UDF 能夠使用的場(chǎng)合,都可以轉(zhuǎn)為使用本機(jī)編譯的 Scalar UDF。不僅如此,,它還能夠在本機(jī)編譯的存儲(chǔ)過程中使用,這一點(diǎn)對(duì)于代碼重用來說是個(gè)巨大的勝利,因?yàn)樵?SQL Server 中,這種方式之前總是被認(rèn)為意味著糟糕的性能。
與本機(jī)編譯的存儲(chǔ)過程一樣,本機(jī)編譯的 Scalar UDF 也必須被定義為綁定到架構(gòu)(schema bound)。在存儲(chǔ)過程中,WITH SCHEMABINDING 選項(xiàng)表示本機(jī)編譯是所期望的方式。目前還不清楚這一選項(xiàng)將如何作用于 UDF,不過就像你已經(jīng)看到的一樣,它必然代表綁定到架構(gòu)的函數(shù)?;蛟S它能夠自動(dòng)檢測(cè)到某個(gè)綁定到架構(gòu)的 UDF 可否進(jìn)行本機(jī)編譯,根據(jù)結(jié)果不同進(jìn)行相應(yīng)的舉措。
英文原文:SQL Server 2016: Natively Compiled Functions
本文永久更新鏈接地址:

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

MySQLWorkbench stores connection information in the system configuration file. The specific path varies according to the operating system: 1. It is located in %APPDATA%\MySQL\Workbench\connections.xml in Windows system; 2. It is located in ~/Library/ApplicationSupport/MySQL/Workbench/connections.xml in macOS system; 3. It is usually located in ~/.mysql/workbench/connections.xml in Linux system or ~/.local/share/data/MySQL/Wor
