One of our Server was having memory problem, when I started Performance Monitor none of SQL Server counters where available. To resolve this kind of issue, Perform below steps.
Step 1:
Open Command Prompt and type "unlodctr.exe MSSQLServer" and hit Enter
Output:
Removing counter names and explain text for MSSQLServer
Updating text for language 009
Step 2:
Locate the Binn folder of SQL Server Installation and look for file named sqlctr.ini. Now copy the complete path of this ini. For example :
D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlctr.ini
Step 3:
Go to command prompt and type
lodctr.exe "D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlctr.ini"
Output:
No error message.
Incase you are not using double quotes in the path name above you will then get below error message "Unable to find initialization file Files\Microsoft". So Don't forget to enclose the path with quotes.
Now go to Start --> Run --> Type perfmon.msc and check for SQL Counters and you will be able to see it... If not just give a Restart (???). This issue seems to be coming in cluster servers after failover.
Links:
How to manually rebuild Performance Counter Library values
My Journey with Microsoft SQL Server as SQL Server DBA!
Stories on Issues Faced, Struggled, Hacked, Profiled, Troubleshooted, Resolved, Fixed and .... Restarted!
Showing posts with label Performance. Show all posts
Showing posts with label Performance. Show all posts
Sunday, January 25, 2009
Wednesday, November 26, 2008
SQL Server Configuration Settings to Boost Performance
To Know about
Affinity Mask
Lightweight Pooling
Max Async IO
Max Worker Thread
Memory
Priority Boost
Set Working Set Size
How to determine proper SQL Server configuration settings
Do not create more databases since SQL Server need to allocate fixed memory for each database, so there may not be enough virtual memory when you have a large number of databases in SQL Server
A description of the 4 GB RAM Tuning feature and the Physical Address Extension parameter
How to adjust memory usage by using configuration options in SQL Server
awe enabled Option
Setting Server Configuration Options in SQL 2005
How to configure SQL Server to use more than 2 GB of physical memory
Operating Systems and PAE Support
Videos:
Christian Bolton on Understanding memory architecture and how SQL Server uses it can help a great deal with how you approach performance troubleshooting or setup a new SQL Server
Affinity Mask
Lightweight Pooling
Max Async IO
Max Worker Thread
Memory
Priority Boost
Set Working Set Size
How to determine proper SQL Server configuration settings
Do not create more databases since SQL Server need to allocate fixed memory for each database, so there may not be enough virtual memory when you have a large number of databases in SQL Server
A description of the 4 GB RAM Tuning feature and the Physical Address Extension parameter
How to adjust memory usage by using configuration options in SQL Server
awe enabled Option
Setting Server Configuration Options in SQL 2005
How to configure SQL Server to use more than 2 GB of physical memory
Operating Systems and PAE Support
Videos:
Christian Bolton on Understanding memory architecture and how SQL Server uses it can help a great deal with how you approach performance troubleshooting or setup a new SQL Server
Tuesday, October 21, 2008
Run Job During IDLE CPU Condition
SQL Server Agent has an option to schedule a job to run when CPU(s) become idle, this can be a good choice for jobs which need more resources!
For example, You Server may be fully busy during USA and UK business hours and may be idle during the remaining time, so in that case we cannot define the exact period for the job but if we choose this option then SQL Server will automatically run the job when CPU become's IDLE.
On the other side you may get doubt that "incase CPU's are idle for just 2 mins during peak time, this schedule will start and may add to the utilization!"... Don't worry, Explan Enterprise Manager --> Go to SQL Server Agent --> Right click --> Select Properties --> Select Advanced Tab you will find below option
Here you can specify your own criteria for what is so called "IDLE" condition and only if this criteria is met then SQL Server Agent will run those jobs scheduled for IDLE CPU condition!
Test it and implement on exact fit situation!
Subscribe to:
Posts (Atom)