Search
Subscribe
Categories
- Backup and Restore
- Capacity Planning
- Compression
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- DBCC
- Deadlocks
- Default Trace
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Execution Plan
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Isolation levels
- Jobs
- Latches
- Links
- Locking
- Memory
- Monitor Performance
- MS DTC
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Blocking
- SQL Cachestore
- SQL DAC
- SQL Default Trace
- SQL DTS
- SQL Error Logs
- SQL Execution Plan
- SQL Optimizer
- SQL problems
- SQL Query Tuning
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL Trigger
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- Stored Procedure
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- View
- Virtualization
- Wait Stats
SQLServer-DBA.com Links
Recent Posts
- SQL Error 1204 - cannot obtain a LOCK resource at this time
- Multi-statement table valued function and inefficient Excecution Plan
- SQL Server Export to Excel with Powershell
- Who dropped the table in SQL Server
- List sql database roles
- SQL Execution Plan - Comparing Estimated Rows and Actual Rows
- DCOM got error "Logon failure: unknown user name or bad password” Event 1004
- SQL Server Triggers and Performance
- SQLServerAgent could not be started (reason: Error creating a new session)
- Performance Tuning - Save hundreds of hours
10 October,2011 by Jack Vamvas
sys.dm_os_loaded_modules is a SQL Server OS Dynamic Management View (DMV). It returns a list each module loaded into the server address space
When executing the t-sql statement below – a recordset is returned . I’ve included some output further down the page :
select file_version,product_version,company,[description],name from sys.dm_os_loaded_modules
I find this dmv useful when troubleshooting corruption .
An example , is to check if there is any anti-virus module which is getting loaded in the SQL memory area. Normally , I’m looking for non-Microsoft Corporation modules .
Returns a row for each module loaded into the server address space.
2005.90:4340.0 9.0:4340.0 Microsoft Corporation SQL Server Windows NT 5.2:3790.4789 5.2:3790.4789 Microsoft Corporation NT Layer DLL 5.2:3790.4480 5.2:3790.4480 Microsoft Corporation Windows NT BASE API Client DLL 8.0:50727.3053 8.0:50727.3053 Microsoft Corporation Microsoft® C Runtime Library 7.0:3790.3959 6.1:8638.3959 Microsoft Corporation Windows NT CRT DLL 8.0:50727.3053 8.0:50727.3053 Microsoft Corporation Microsoft® C++ Runtime Library 5.2:3790.4455 5.2:3790.4455 Microsoft Corporation Advanced Windows 32 Base API 5.2:3790.4759 5.2:3790.4759 Microsoft Corporation Remote Procedure Call Runtime 5.2:3790.4530 5.2:3790.4530 Microsoft Corporation Security Support Provider Interface 2005.90:4035.0 9.0:4035.0 Microsoft Corporation SQLOS Hosting DLL
Related Posts
SQL Server – Download the Perfstats script
How to report a SQL Server performance problem
SQL Server Performance Killers
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: |