Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
 Posted - 2001-08-29 : 15:31:49
|
| This is SQL Server 7's profiler, SQL 2k does not have this bug.I setup a trace on SA and created a login called SZ with the same password as SA with the exception of the last letter in the password, which I changed to Z. With this in mind, we changed the HEX code, using Ultra Edit 32, on an old VB app that was using SA. We changed the SA to SZ and the password to *********Z. We then launched the app and it came up under SA. After a reboot, the app was coming up as SZ. This is not the problem.Later I logged into query analyzer using SA and it came up under the SZ login for the trace. I found that no reboot was needed for the app. The only reason why SZ came up is because I rebooted my box (the one running profiler). It seems that Profiler is seeing SZ/*****z and then later seeing SA/****** and saying, "Hmm. I had SZ/*****Z before this SA/****** must have been passed to me wrong. I'll put this SA with SZ."I tested this several times, on several differnt boxes. All tests included SQL Server 7 Profiler running on Win2k. With a restart of profiler, if SA was the first to show in the trace the SZ and SA would be logged under SA. If SZ was first then SZ and SA would be under SZ. Both SA and SZ had the system admin role granted to them.I was able to change the app to login DQ and it did not require a reboot and the app came up as DQ in the profiler.Has anyone seen this bug before? Did anyone make it to the end of my story?Thanks for any info guys... and sorry so long.DanielSQL Server DBA |
|
|
|
|
|
Awful bug in SQL Profiler