Difference between SM50 and SM66
I heard that SM50 view the work process inan instance's scope and SM66 view them in a system's scope. But I always see there're much more processes displayed in SM50 than SM66. Can anybody explain why some processes don't appear in SM66 even if SM66 has a bigger scope?
Thanks + Best Regards
Rajat Anand replied
SM50 is t-code for process overview. It shows the status of type of work process and their satatus. By double clicking on the row of respective process we can see the details about the kind of programs it is running and SQL statements, database activities and extended memory allocation while the process is running.Basically we use this transaction code to display work processes, To check the Update StatusProcess, Analysis SQL Locks .you can 'kill' the running process with core or without core in SM50.
The T-CODE SM66 is Global servers work area. That means it is having all the servers running with in an organization/company etc. When you again double click on any one of the server at that time is shows SM50 of that particular server. SM50 is local server work area and SM66 is global work area.You can see the how work process is encaged ie status the process running,waiting...
As a note, unless you are a BAIS person and know what you are doing, you shouldn't use SM 50 in PROD. Developers and Support shuld only use SM66. Here, you can display same infomration as SM50, but you cannot accidentally kill any process. In SM66, you can also see Multiple Server Detials in same screen unlike SM50.
Also, Support People should kill loads using SM37 only, SM50 should be used with care
Rewrad suiatble points