Workarounds for SQL Server Profiler cannot be paused and stopped
Although SQL Server Profiler works well, there is an issue where you cannot pause and stop after you start profiler on the local database (locally) (Once you pause or stop for a long time), this problem occurs primarily because profiler uses the install SQL by default Server, the local computer name is logged to access the local database, and if you modify the computer name after you install SQL Server, the profiler can start an issue that cannot be stopped.
1. WORKAROUND: Use the computer name or IP to connect to the database using Profiler, instead of (local), you can pause and stop normally.
2. WORKAROUND: Update the computer name that is logged in SQL Server. Open the sysservers table of the master database, modify the Srvname field and the DataSource field as the current computer name (because it is a system table, it is not allowed to modify by default, so you need to set it before you modify it: Right-click the (Local) node in Enterprise Manager, "properties "-" Server Settings ", tick" allow direct modifications to the system directory "in" Server Behavior ".
Workarounds for SQL Server Profiler cannot be paused and stopped
