Lynn Pettis (1/19/2010)

---

Considering that updating the system table probably wouldn't change any settings on the actual database. There is probably something in the system data stored in the mdf...

You're running SQL 2000 there, not SQL 2005.

It doesn't. Once SQL detects that a drive...

Lynn Pettis (1/19/2010)

---

Oh,...

It may have. Or it may not have. Impossible to tell without running a checkDB, which is...

You need to set a default on the column. Look up ALTER TABLE for the syntax to do so.

gregory.anderson (1/19/2010)

---

GilaMonster (1/19/2010)

---

Scans of the clustered index are table scans. They either indicate that a nonclustered index was not selective enough to be used, or there are nonclustered indexes missing.

How...

Lynn Pettis (1/19/2010)

---

Oh, there is a way to update the system tables in SQL Server 2005, here's how. Let us know if it works for you. No warning...

Please run the following and post the results

SELECT @@version

I'd suggest a reboot. Once SQL's back online, run a checkDB on the original database, see if everything's OK.

You probably didn't need to restore the database, very likely once the...

Take a look at this series

http://www.brentozar.com/becoming-a-dba/how-to-get-a-junior-dba-job/

That's not a compete output and I cannot see from that what's wrong. Where did that come from? Looks like just the job history.

Even ignoring that 'allow updates' is ignored on SQL 2005, sysdatabases isn't even a table any longer. It's a view...

Scans of the clustered index are table scans. They either indicate that a nonclustered index was not selective enough to be used, or there are nonclustered indexes missing.

How did the...

I'd start with google.