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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 When was last SP installed? SQL Server Errors

Author  Topic 

TallOne
Starting Member

49 Posts

Posted - 2007-06-01 : 16:15:19
Is there a way for me to see when the last SP was installed on a WIN2K server? I got a client that is suddenly having problems with SQL Server 2000. Event log application

error 17883,Severity:1,stat:0
Process0:0(7ec) UMS Context0x0027EE68 appears to be non-yielding on Scheduler 0

17310: process_commands: Process 2020 generated fatal exception c000001d EXCEPTION_ILLEGAL_INSTRUCTION. SQL Server is terminating this process

17310:
SqlDumpExceptionHandler: Process2020 generated fatal exception c000001d EXCETPION_ILLEGAL_INSTRUCTION. SQL Server is terminating this process.

Also any ideas on these errors would make my FRIDAY much happier! :)

Thanks,
Jerry

jezemine
Master Smack Fu Yak Hacker

2886 Posts

Posted - 2007-06-01 : 18:29:30
select crdate from sysobjects where name='myprocname'


www.elsasoft.org
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-06-02 : 00:52:24
You mean service pack? There is sql sp install log file in windows directory.
Go to Top of Page

jezemine
Master Smack Fu Yak Hacker

2886 Posts

Posted - 2007-06-02 : 01:35:27
hehe, for some reason I thought OP meant "stored procedure" by "SP". It's clear now that's not what they meant.




www.elsasoft.org
Go to Top of Page

TallOne
Starting Member

49 Posts

Posted - 2007-06-03 : 20:22:55
Thanks for the replies. Sorry for the delayed response. I did mean service pack. :( After researching more, the problem with the errors above was a simple select statement. It was really crazy! THere was a column that contained a row with corrupted data. When ever this particular column and row was selected in a query, SQL locked up and only a reboot would cure the symptom......until that particular row in the column was queried again. To resolve the issue, DBCC CheckAlloc (‘tableName) or DBCC CheckDB('tableName') identified the inconsistency in the tables and CheckTable with the repair option fixes it but only after putting the DB in single user mode. Also, the repair_fast option which would have saved the data in the two corrupted records but it would not work so there are 2 missing records now. :( Hope this helps anyone in the future.

TallOne
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-06-05 : 04:48:12
I suggest you run DBCC CHECKDB as part of your scheduled maintenance.

Also check if your have Torn page Detection ON - if you've migrated from SQL7 that may have been off by default.

Better than any corruptions are bought to light as soon as possible after they occur!!

Kristen
Go to Top of Page
   

- Advertisement -