Justify the Remote access requirement for Biztalk Log Shipping

I have been in a situation where our Security compliance team requested to prove that remote access configuration is indeed mandatory to setup log shipping for a Biztalk database. As all we know this configuration option is used to execute remote stored procedures from local server or allow access from remote server to execute a local stored procedure. Of course this has to be accompanied with a linked server that provide RPC_OUT services.

Refer below my article for more details.

http://www.sqlservercentral.com/links/337157/360187

Top Processes consuming Memory and CPU

It is at time important to find out what other processes are doing in term of CPU and memory utilization, following commands are helpful for ad-hoc or reporting purpose.

Top 5 Memory consuming processes:

Powershell > get-wmiobject WIN32_PROCESS | Sort-Object -Property ws -Descending|select -first 5|Select processname, @{Name="Mem Usage(MB)";Expression={[math]::round($_.ws / 1mb)}},@{Name="ProcessID";Expression={[String]$_.ProcessID}},@{Name="UserID";Expression={$_.getowner().user}}

Memory consuming processes more than 100MB

tasklist /FI "MEMUSAGE ge 100000"



CPU consuming processes:

wmic path Win32_PerfFormattedData_PerfProc_Process where PercentProcessorTime!=0 get Name,PercentProcessorTime







Top CPU consuming processes that are running for more than 5 minutes:

tasklist /fi "cputime gt 00:05:00"