Search
Subscribe
Categories
- Backup and Restore
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- Deadlocks
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Jobs
- Links
- Locking
- Memory
- Monitor Performance
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Cachestore
- SQL Error Logs
- SQL Optimizer
- SQL problems
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- Virtualization
- Wait Stats
Recent Posts
- How to check Operating System type with Powershell
- ALTER TRACE and developers
- Predict ALTER INDEX REORGANIZE finish time
- Cannot connect to SQL Server
- Timeout occurred while waiting for latch: class 'LOG_MANAGER'
- The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time
- How to create a SQL Server Security Audit
- Cannot use Large Page Extensions: lock memory privilege was not granted
- Compare two files with Powershell
- Export-CSV Powershell
On a particular server - I see these entries in the Logs, which correlate with failed BACKUP messages from the TSM server :
BackupVirtualDeviceSet::SetBufferParms: Request large buffers failure on backup device 'TDPSQL-000002F8-0000'. Operating system error 0x8007000e(error not found).
My immediate impression was lack of memory.
This server has 32 GB physical memory on a 32 bit Windows 2003 Enterprise Edition , so I checked the following :
- /PAE switch in the boot.ini file (no /3GB switch)
- maximum memory set on SQL Server (17GB)
- AWE is set on
- User running SQL Server - has Lock pages in memory
All this seems OK . Looking further into the Memory manager
VM Commited displays physical memory amount SQL Server allocated ising VirtualAlloc's MEM_COMMIT .
AWE allocated displays the memory amount allocated by AllocateUserPhysicalPages.
Adding these 2 will give approximately the amount SQL Server memory usage
Memory Manager
VM Reserved = 1645036 KB
VM Committed = 211672 KB (.201) GB
AWE Allocated = 17408000 KB (16.6015625 GB)
Reserved Memory = 1024 KB
Reserved Memory In Use = 0 KB
It appears the SQL server is reaching it's memory limit .
One answer is to increase Memory allocation , another option is to investigate the cause of large memory usage
Source:Jack Vamvas (http://www.sqlserver-dba.com)Author: Jack Vamvas (http://www.sqlserver-dba.com)
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |