MSSQL administration with DBA cockpit - Functionalities
Though there are lot of presentations available in various forums, I thought it would be a good idea to share my knowledge on the subject.
In this article we will be focussing on DBA cockpit functionalities with SAP Net Weaver Systems on MSSQL .
Firstly DBA Cockpit is a powerful transaction and itself has an authorisation concept. For more details about the authorisation please see SAP Note:1027512
Is my SQL Server setup complete?
Before proceeding as a user we need to check if the SQL Server is configured correctly. This can be done by hitting the transaction DBA Cockpit ->Configuration ->SQL Server Set up Check
The status messages give an overview with legends marked red, green and blue. All messages are informative and self-explanatory, thanks to the SAP developers who have worked exclusively on this for SQL Server.
To make life easier SAP has provided a note 1609057 for further explanations.
As always SAP provides another way to check the configuration parameters for SQL Server. This includes colour coding and the values are displayed [this can be double checked with SAP notes 1237682 (MSSQL 2008 R2) and 879941 (MSSQL 2005)]
SQL server error logs
The error and log information are very important from an administration perspective and it needs to be monitored correctly.
The errors can be accessed through DBA Cockpit ->Diagnostics ->SQL Error Logs. I will discuss some basic SQL Error log fundamentals so that it is easy to understand.
- Nomenclature is ERRORLOG
- A new error log is started at every SQL Service restart
As a best practice you can always compare the error logs with ST22, SM21
- Severity 20: is critical, must be investigated immediately
- Severity 17-19: should be investigated
- Severity <16: is normal
Deadlocks are normally caused by the application specific coding and rarely related to the database. The deadlocks can be traced by DBA Cockpit ->Diagnostics ->Deadlocks.
From a technical perspective the most important information to look for in case of deadlocks is that of ABAP programme name and the table name.
Missing tables and indexes
There are two possibilities in this case:
- Tables are present in SAP system and not in database
- Tables are present in the Database and not present in Data Dictionary.
For both scenarios DBA Cockpit ->Diagnostics ->Missing Tables and Indexes. Transaction se16 and se14 are used to create the tables and the indexes respectively.
The jobs can be scheduled and monitored from DBA Cockpit ->Jobs transaction.The custom-defined database consistency check can be easily scheduled and the status can be monitored.
DBA Cockpit->Space transaction gives an easy way to analyse statistical details of DB size. The most common use is to find the largest and the fastest growing table.
The dbacockpit provides an all-in-one tool for DB activities especially SQL Server.
Please post your comments and questions regarding the blog. I hope this post provides an insight to dbacockpit.« Back to articles