22,207
社区成员
发帖
与我相关
我的任务
分享资源池 'default' 没有足够的系统内存来运行此查询。
资源池 'default' 没有足够的系统内存来运行此查询。
mssql2008 R2+win2008 64位 [/code]
Last Notification 2
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 Error occurred while attempting to drop worktable with partition ID 140737980268544.
51:18. spid53 Error occurred while attempting to drop worktable with partition ID 140737979482112.
51:19. 登录 错误: 17803，严重性: 20，状态: 13。
51:19. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:19. 登录 错误: 17803，严重性: 20，状态: 13。
51:19. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:20. 登录 错误: 17803，严重性: 20，状态: 13。
51:20. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:20. 登录 错误: 17803，严重性: 20，状态: 13。
51:20. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:21. 登录 错误: 17803，严重性: 20，状态: 13。
51:21. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:21. 登录 错误: 17803，严重性: 20，状态: 13。
51:21. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:23. spid53 Worktable with partition ID 0 was dropped successfully after repeated attempts.
51:23. spid53 Worktable with partition ID 0 was dropped successfully after repeated attempts.
54:12. spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
54:12. spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
54:12. spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
54:12. spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
54:12. spid51 FILESTREAM: effective level = 0
54:12. spid51 Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
54:12. spid51 FILESTREAM: effective level = 0
54:17. spid51 Configuration option 'max server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
54:17. spid51 FILESTREAM: effective level = 0
54:22. spid51 Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
54:22. spid51 FILESTREAM: effective level = 0
59:12. spid66 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
59:12. spid66 FILESTREAM: effective level = 0
59:12. spid66 Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
59:12. spid66 FILESTREAM: effective level = 0
59:17. spid66 Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
59:17. spid66 FILESTREAM: effective level = 0
59:17. spid66 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
59:17. spid66 SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
59:17. spid66 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
59:17. spid66 SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
59:17. spid66 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
59:17. spid66 SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
59:22. spid66 Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
mssql2008 R2+win2008 64位 [/code]
Last Notification 2
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 错误: 701，严重性: 17，状态: 123。
51:18. spid53 There is insufficient system memory in resource pool 'default' to run this query.
51:18. spid53 Error occurred while attempting to drop worktable with partition ID 140737980268544.
51:18. spid53 Error occurred while attempting to drop worktable with partition ID 140737979482112.
51:19. 登录 错误: 17803，严重性: 20，状态: 13。
51:19. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:19. 登录 错误: 17803，严重性: 20，状态: 13。
51:19. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:20. 登录 错误: 17803，严重性: 20，状态: 13。
51:20. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:20. 登录 错误: 17803，严重性: 20，状态: 13。
51:20. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:21. 登录 错误: 17803，严重性: 20，状态: 13。
51:21. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:21. 登录 错误: 17803，严重性: 20，状态: 13。
51:21. 登录 There was a memory allocation failure during connection establishment. Reduce nonessential memory load
51:23. spid53 Worktable with partition ID 0 was dropped successfully after repeated attempts.
51:23. spid53 Worktable with partition ID 0 was dropped successfully after repeated attempts.
54:12. spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
54:12. spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
54:12. spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
54:12. spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
54:12. spid51 FILESTREAM: effective level = 0
54:12. spid51 Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
54:12. spid51 FILESTREAM: effective level = 0
54:17. spid51 Configuration option 'max server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
54:17. spid51 FILESTREAM: effective level = 0
54:22. spid51 Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
54:22. spid51 FILESTREAM: effective level = 0
59:12. spid66 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
59:12. spid66 FILESTREAM: effective level = 0
59:12. spid66 Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
59:12. spid66 FILESTREAM: effective level = 0
59:17. spid66 Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
59:17. spid66 FILESTREAM: effective level = 0
59:17. spid66 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
59:17. spid66 SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
59:17. spid66 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
59:17. spid66 SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
59:17. spid66 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
59:17. spid66 SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
59:22. spid66 Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
...全文
请发表友善的回复…
发表回复
Q315054403 2013-09-09
- 打赏
- 举报
这个其实是我自己再设置，因为如果不设置数据库内存就在不断的增大，所以我就加了一个作业五分钟就设置一次最大内存和最小内存，并且释放内存。[/quote]
那你误解了这个设置，和其内在运作机制
魔者侠心之明星级程序员 2013-09-09
- 打赏
- 举报
这个其实是我自己再设置，因为如果不设置数据库内存就在不断的增大，所以我就加了一个作业五分钟就设置一次最大内存和最小内存，并且释放内存。[/quote]
强烈不建议这么做,
1.数据库进程内存增长是正常现象,MSSQL会自行管理内存使用.
不必限制最大内存,设为自动管理即可.
2.每5分钟释放一次内存会导致缓存丢失,每次读取只能去磁盘读,严重影响性能.
[/quote]
一般情况下，最大内存的大小还是要设置的，
尽管SQL SERVER对于外部、内部内存压力有自我条件功能，但是它不是表现的很完美，
有时候有外部内存压力的时候，它的反应不够快，或者不够彻底，那就会引起SQL SERVER被paged out，影响性能。
Q315054403 2013-09-07
- 打赏
- 举报
59:17. spid66 Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
有人捣蛋？？
检查一下SP_Configure
唐诗三百首 2013-09-07
- 打赏
- 举报
这个其实是我自己再设置，因为如果不设置数据库内存就在不断的增大，所以我就加了一个作业五分钟就设置一次最大内存和最小内存，并且释放内存。[/quote]
强烈不建议这么做,
1.数据库进程内存增长是正常现象,MSSQL会自行管理内存使用.
不必限制最大内存,设为自动管理即可.
2.每5分钟释放一次内存会导致缓存丢失,每次读取只能去磁盘读,严重影响性能.
niit3063ljy 2013-09-07
- 打赏
- 举报
2013-09-06 16:17:38.610,spid61,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:17:43.780,spid61,Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:17:43.790,spid61,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:17:49.010,spid61,Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
2013-09-06 16:17:49.060,spid61,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:22:16.660,spid54,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:22:16.720,spid54,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:22:16.800,spid54,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:22:16.810,spid54,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:22:16.880,spid54,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:22:16.940,spid54,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:22:19.030,spid54,Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2013-09-06 16:22:19.030,spid54,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:22:19.110,spid54,Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:22:19.110,spid54,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:22:24.230,spid54,Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:22:24.230,spid54,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:22:32.060,spid59,
niit3063ljy 2013-09-07
- 打赏
- 举报
2013-09-06 15:58:37.640,spid53,Setting database option COMPATIBILITY_LEVEL to 100 for database BWERP_fb001.
2013-09-06 15:58:37.700,spid60,Starting up database 'bw9kbzpro_03'.
2013-09-06 16:00:39.360,spid55,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:00:39.440,spid55,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:00:39.440,spid55,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:00:39.830,spid55,Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2013-09-06 16:00:39.830,spid55,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:00:39.840,spid55,Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:00:39.840,spid55,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:00:44.840,spid55,Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:00:44.840,spid55,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:00:49.900,spid55,Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
2013-09-06 16:00:49.900,spid55,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:00:56.370,spid58,Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2013-09-06 16:00:56.370,spid58,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:00:56.370,spid58,Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:00:56.370,spid58,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:01:01.400,spid58,Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:01:01.400,spid58,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:01:06.470,spid58,Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
2013-09-06 16:01:06.470,spid58,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:05:51.880,spid52,Setting database option COMPATIBILITY_LEVEL to 100 for database BWERP_fb001.
2013-09-06 16:07:06.020,spid52,Setting database option COMPATIBILITY_LEVEL to 100 for database bwerp_pos.
2013-09-06 16:10:16.850,spid4s,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\dataBack\BWERP_fb001.ldf] in database [BWERP_fb001] (10). The OS file handle is 0x00000000000006A0. The offset of the latest long I/O is: 0x00000004810800
2013-09-06 16:12:16.520,spid54,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:12:16.520,spid54,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:12:16.530,spid54,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:12:16.530,spid54,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:12:16.530,spid54,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:12:16.530,spid54,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:12:18.420,spid54,Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2013-09-06 16:12:18.420,spid54,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:12:18.470,spid54,Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:12:18.470,spid54,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:12:23.650,spid54,Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:12:23.650,spid54,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:12:27.810,spid59,Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2013-09-06 16:12:27.810,spid59,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:12:27.880,spid59,Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:12:27.880,spid59,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:12:28.860,spid54,Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
2013-09-06 16:12:28.860,spid54,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:12:33.040,spid59,Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:12:33.040,spid59,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:12:38.320,spid59,Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
2013-09-06 16:12:38.320,spid59,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:17:16.540,spid68,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:17:16.540,spid68,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:17:16.560,spid68,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:17:16.560,spid68,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:17:16.570,spid68,SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2013-09-06 16:17:16.570,spid68,SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2013-09-06 16:17:17.610,spid68,Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2013-09-06 16:17:17.610,spid68,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:17:17.630,spid68,Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:17:17.640,spid68,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:17:22.690,spid68,Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
2013-09-06 16:17:22.690,spid68,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:17:29.320,spid68,Configuration option 'max server memory (MB)' changed from 256 to 2147483647. Run the RECONFIGURE statement to install.
2013-09-06 16:17:29.860,spid68,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:17:38.580,spid61,Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2013-09-06 16:17:38.580,spid61,FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-09-06 16:17:38.610,spid61,Configuration option 'min server memory (MB)' changed from 256 to 256. Run the RECONFIGURE statement to install.
niit3063ljy 2013-09-07
- 打赏
- 举报
这个其实是我自己再设置，因为如果不设置数据库内存就在不断的增大，所以我就加了一个作业五分钟就设置一次最大内存和最小内存，并且释放内存。
發糞塗牆 2013-09-06
- 打赏
- 举报
这种情况通常是因为你的查询性能太差，特别是丢失索引，导致大量的扫描、哈希关联等等高开销的操作，核心工作还是优化代码。
KevinLiu 2013-09-06
- 打赏
- 举报
256 to 2147483647. 你开始的只给你的数据库服务器设置了256M的内存啊？那你整个服务器内存多少？这个也太少了。
Andy__Huang 2013-09-06
- 打赏
- 举报
内存不够，可能是因为计算太复杂，或者事务处理错误只提交没有回滚，或者其他错误导致一直占用系统内存而致内存不足，建议你检查程序是做了哪些操作而产生这样的错误？直接对这个问题去检查代码
