When I tested the SQL Server 2014 memory database some time ago, I found that if the database size exceeds the configured maximum memory size, SQL Server encountered Error: 701.
Error message:
Error: 701, Severity: 17, State: 123.
There is insufficient system memory in resource pool 'internal' to runthis query.
At that time, I deleted the database and restarted it. In fact, when the memory is insufficient, DAC can still be connected.
The following is my test:
Default Connection Failed:
650) this. width = 650; "src =" http://img.blog.csdn.net/20130723143941000? Watermark/2/text/plain =/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA ==/ dissolve/70/gravity/SouthEast "/>
You can use the DAC to connect successfully (or use the sqlcmd DAC ):
650) this. width = 650; "src =" http://img.blog.csdn.net/20130723143954640? Watermark/2/text/plain =/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA ==/ dissolve/70/gravity/SouthEast "/>
Because I still had memory resources on the server at the time, I can directly modify the maximum memory:
Sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
Sp_configure 'max server memory ', 4096;
GO
RECONFIGURE;
GO
If the DAC is connected, you can view the status of the system and process the problematic sessions. In this way, you do not need to restart the SQL Server and discover the problems in time.
This article is from the "follow SQL Server Technology" blog, please be sure to keep this source http://lzf328.blog.51cto.com/1196996/1255341