Start Free Trial
SQL server peformance issues in production
I have Sql sever 2012. In production I am seeing slowness in database.
How do I find slow running queries.
How do we check the CPU usage.
How do I see any deadlock.
Do we have queries to check this?
Any other metrics to check?
Also we have few SSIS packages. They load lot of new data from the files. The DB size is 1.5 TB.
Microsoft SQL Server
8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Raja Jegan R
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
I wouldn't mind much with CPU usage when dealing with databases. Resources as Memory, Disk and Network are more important. CPU should be the last resource to watch to.
But first of all check your queries performance. If the database design is poor (not normalized, lack of indexes, ...) then is highly possible that your queries will be unperformed. You can start by using
SQL Server Profiler
to capture the long running queries and analyze them, one by one.
No need to reinvent the wheel.
Use Task Manager and Resource Monitor to check the overall computer functionality and bottle necks.
Scripts for SQL Server also exist - look e.g. here:
and download and test all sp_Blitz.... scripts. They are perfect for people like you (and me).
Queries to check SQL Server blocking are e.g. here:
Of course, you'll need to learn additional knowledge to understand Query Plans, SQL Profiler output etc. etc.
Your help has saved me hundreds of hours of internet surfing.
Plans and Pricing
Certified Expert Program
© 1996-2023 Experts Exchange, LLC. All rights reserved. Covered by US Patent
But first of all check your queries performance. If the database design is poor (not normalized, lack of indexes, ...) then is highly possible that your queries will be unperformed. You can start by using SQL Server Profiler to capture the long running queries and analyze them, one by one.