can any one help me what are the steps to b take when database is running slow?
This is a huge subject and runs the full gambit from which hardware and operating system are installed, whether or not VM is being used or not, how SQL Server was installed and what settings it has been setup with, how the hard-disks have been formatted and partitioned, how the databases has been setup for growth, how the tables are designed, how the indexes are designed, how the queries are written, how DB maintenance is done, etc, etc, etc and even includes the number of sun spots and the position of the moon. ;-)
My recommendation is to take Step 1 and get some training if you're going to do the job of a DBA. If that's out of the question, consult with my personal "Assistant DBA"... His name is "Google". Tell him you want information on "steps to take when DB running slow". In the process, you'll also learn, which takes us back to Step 1.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs