noeld (1/6/2009)

---

In addition your trigger should only perform the update IF the columns on the "deleted" and "inserted" tables have different values. That way you will be minimizing the impact...

GilaMonster (1/6/2009)

---

Marios Philippopoulos (1/6/2009)

---

DECLARE @ActionType char(1)

SELECT @ActionType = CASE

...

Regarding my earlier posting:

Having the trigger takes the onus away from the developers of remembering to include the right code in all their sproc code. The trigger is part of...

GSquared (1/6/2009)

---

If you can guarantee that the only way for this data to be updated is by procs, then including the update date and user in the procswould be better,...

GilaMonster (1/6/2009)

The only other way requires that all access to the table is via known stored...

GilaMonster (1/6/2009)

---

Marios Philippopoulos (1/6/2009)

---

DECLARE @ActionType char(1)

SELECT @ActionType = CASE

...

Using the method in my previous posting, I found the culprit: it is an UPDATE trigger on a large table.

Thank you all for your input.

According to this link - http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx#E4CAC - the features generating version-store records in tempdb are:

• Snapshot isolation

• Read committed snapshot isolation (RCSI)

• Online...

I took a look at http://msdn.microsoft.com/en-us/library/ms186328(SQL.90).aspx. I need to get session and task-level info on the process that gives rise to the...

Thank you both, I'll have a look at your suggestions.

Luke L (12/31/2008)

---

Sounds like perhaps your VSS database has been corrupted. Do you have admin rights to your VSS database? Can you log into it with the VSS...

I found the problem.

I was somehow missing the following 2 registry entries. After adding, the VSS bindings are restored.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe\SCCServerName - value: Microsoft Visual SourceSafe

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe\SCCServerPath - value: path for file ssscc.dll

See...

Yup, but it's not clustered.

DBADave (12/29/2008)

---

Since it's clustered the data is on a SAN. I'm guessing there is an equivelant tool to chkdsk, but I'm not sure I understand the connection. What...

DBADave (12/29/2008)

---

I no longer have the exact log messages since the log has wrapped, but it essentially stated the SQL Server Agent had a problem and needed to be restarted....