January 14, 2011 at 12:08 pm
Since the DMV sys.dm_exec_sessions is missing the field original_login_name I'm assuming we have an "old" master database despite the fact that this query shows SP3
SELECT SERVERPROPERTY('Productversion'),serverproperty('productlevel'),serverproperty('edition')
9.00.4262.00SP3Enterprise Edition (64-bit)
It's time to apply SP4 but don't know if that will correct this issue. I'd like to make use of WhoIsActiveUI which leverages Adam Mechanic's WhoIsActive stored procedure, but it's looking for the field original_login_name http://www.schemasolutions.com/WhoIsActiveUI.aspx
January 14, 2011 at 1:08 pm
The definitions of the dmvs aren't in master, they're in the system resource DB. That would have been upgraded during the patch, providing nothing went wrong during the installation.
As far as I recall, original_login_name was there right from RTM, not a later feature.
What columns does this say are there?
sp_help 'sys.dm_exec_sessions'
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 14, 2011 at 1:22 pm
It has login_name but not original_login_name which I believe came with SP2. Create date on our sys.dm_exec_sessions is 10/14/2005 Our resource database has that same date. It looks like following the installation of Sql 2005 64bit the new system database area was renamed to "old" and the 32bit folder was kept. Sql has been running fine that way for a few months. Trying to change the resource database at this point would be frightening to say the least.
session_id
login_time
host_name
program_name
host_process_id
client_version
client_interface_name
security_id
login_name
nt_domain
nt_user_name
status
context_info
cpu_time
memory_usage
total_scheduled_time
total_elapsed_time
endpoint_id
last_request_start_time
last_request_end_time
reads
writes
logical_reads
is_user_process
text_size
language
date_format
date_first
quoted_identifier
arithabort
ansi_null_dflt_on
ansi_defaults
ansi_warnings
ansi_padding
ansi_nulls
concat_null_yields_null
transaction_isolation_level
lock_timeout
deadlock_priority
row_count
prev_error
January 14, 2011 at 1:42 pm
Indianrock (1/14/2011)
It looks like following the installation of Sql 2005 64bit the new system database area was renamed to "old" and the 32bit folder was kept.
Be grateful nothing broke.
Reapply the service packs
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 14, 2011 at 1:46 pm
Would applying SP4 do the trick?
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b953e84f-9307-405e-bceb-47bd345baece
January 14, 2011 at 2:09 pm
Maybe. Probably.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply