October 17, 2002 at 6:27 pm
I have a new server (server A) with SQL Server 7.0 that was recently built by restoring system databases (master, msdb and model) backups from another server (server B). Everything is working well including query analyzer, EM, client application .... until today, when I launch Profiler for server A, it's performing a trace on server B instead. Now I could not run any traces on server A. Does anyone have had idea why Profiler would behave this way? Server A was built from scratch. The only link with server B was the system databases was restored from its backups.
Appreciate any advice.
Thanks in advance.
October 17, 2002 at 6:38 pm
Maybe has to do with how its resolving the server name? Got a WINS alias set up? Local alias?
Andy
October 18, 2002 at 5:09 am
Check alias in Cient Network Utility also.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
October 18, 2002 at 6:52 am
It seems to me that is the system tables were restored from server A, then in the master database, in the sysservers table, row 0 would show server a's name as the server, which of course, is the name of the server. Check that, and if it is, rename your server to what you want it to be.
If your not gonna help, Please move to the side, because if your not helping the situation, your hurting it....
October 18, 2002 at 8:39 pm
We executed sp_dropserver and sp_addserver. So, the sysservers table is showing the correct server. I will look into any aliases that may have been setup by accident(?).
Thanks for all the responses.
October 24, 2002 at 6:59 pm
I found out the Profiler tracing incorrect server was in fact a known bug for sp3 which our server is using. See the link for article on Microsoft site. They recommend a hotfix or sp4 as resolution.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q284351
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply