Please let us know if this is the case. Might help others or we can give you other suggestions. I think it's probably corrupt, but you never know.

What was the problem (for others)? Security?

No way to restrict things, but some things, like the Object Browser do not work against 2005.

I'd do as Michael suggested and leave him/her with QA.

If you've got programmers,...

Not really supported, but counting by database.

select count(s.spid)

, d.name d

from sys.sysprocesses s

inner join sys.databases d

on s.dbid = d.database_id

group by...

What are you trying to do? We might be able to help another way.

I agree with Noeld that you should try a reboot and see what happens. Maybe shut down some processes and windows on your system. If it happens again, I'd run...

I had something similar in SQL 2000. It had to do with the disk system not keeping up with the update load.

Have you checked to see if there are issues...

I think the extensions of SOX are what has caused the problems. Most regulatory agencies specifically target certain types of data. SOX went after everything.

Or at least the auditors did.

I haven't seen it, but my wife, Mom, karate instructor, and a few others loved it.

Good luck!

The performance is nicely summarized above and it's really a good debate. But the answer is that it depends.

I know, that sucks. But it depends on how you architect things....

Latches are lightweight locks. Typically I wouldn't worry about them, but if there is contention, then they are something to look deeper at.

The problem is there are many things to...

Just monitor. I'd look at CPU, buffer cache hit ratio, memory reads/sec, user connections, transactions/sec, disk i/o reads and writes.

Once you have data, you'll have an idea of what's normal...

Even if there are no complaints, it's likely that your application will outgrow the server hardware over time. Data sizes grow, more users, things just happen that will cause issues.

So...

Sorry.

The big problem with triggers outside the database is that they're inside the transaciton that fired the trigger. so delays escalate locks and blocks. Transactions should be tight and sending...

What's the structure mean? Is EmailID somehow related to threadID or are you just ordering by the threadID.

Why not just order by threadid desc?