Before You Proceed we recommend you to
read our Disclaimer below
The information contained in this website is for general information, Educational and Practice purposes only. The information is provided by .Raghuveera.com and while we endeavour to keep the information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk.
In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website.
Through this website you are able to link to other websites which are not under the control of [business name]. We have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them.
Every effort is made to keep the website up and running smoothly. However, [business name] takes no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control.
Know your Server : For a great Start I would recommend the DBA to Know the server Completely by reading all the documentation available regarding the server. There would be definitely be some sort of documentation available. Documentation like a runbook or a HLD (High Level Design document) LLD (Low Level Design Document). I would Also recommend having a conversation with the DB Architect. The reason why you should know your server is because if you knew your server completely it would be easier to identify a bottleneck rather than trying to troubleshoot from the start. A coffee meet with your Architect will definitely help. Knowing your Server would help you not to waste time on unnecessary troubleshooting steps and would help you concentrate on the right troubleshooting.
There is no systematic scientific approach for troubleshooting. The art of troubleshooting can only be mastered by practice. The best way to find the Problem is by systematically eliminating all general hypothetical causes and narrowing down on the possible causes.
Tip: If we have an adhoc request or a ticket from a user and the user may just say that the application is slow and not working.In situations like these I would advise probing the Probing the User with different Questions will help in narrowing down to the exact possible cause.
I would Like to Classify perfomance Issues by differentiating in Them according to the below.
Let Us Discuss the three accordingly
Continued to Next Page ------>> Performance issues That can be the result of an improper Database design
Reading query plans (.........coming soon)
Tools (.........coming soon)
Pivoting (.........coming soon)
Real time data generation (.........coming soon)BLOCKING