I've seen this happen frequently, and it may not be because the stats are out of date.

It could be that SQL Server has cached a bad query plan for a...

I'm not sure of what actually happens, but....

Won't a rollback act in the same way as doing the changes in the first place, i.e. the rolled back pages will be updated in...

If you have a large batch of SQL, then using fn_get_sql, you can find out the actual statement in the batch that is being executed. With dbcc inputbuffer, you have...

It is documented in BOL, as long as you have the version of BOL that was updated by SP3.

It sounds like your maintenance plan is doing more than just a full backup. Is it reorganising indexes as well? If so, that can create very large transaction logs and...

I've seen this once before, and it turned out to be the login script replacing the part of the registry that contains aliases with a 'corporate' one.

I have the same problem, which is due to security policies in force at this site.

When you retype the password, do you get a message saying that the account has been...

I came across a similar problem 3 or 4 years ago, where some tables were visible and others weren't, and a similar situation with columns.

It turned out to be a...

Assuming that your table already exists, then the syntax would be:-

alter table class add ClassKey AS (AcademicYearCode + SubjectCode + SetCode)

Don't do it!! Set up a computed column or view instead.

If you're determined to do it, then you need to join the inserted table to the Class table:-

UPDATE

Am I missing something here?

On a system with no other users, who are you going to block?

Deleting 1.5 million rows from a table in a transaction is going to...

On a system where there is no other activity, Select Into should work with no problems.

I have used it myself several times, and have seen it used plenty of times,...

Select into can cause system tables locks in tempdb while the data is inserted, this can literally destroy the apllication. I'd stay far away from this.

I'd hope that this...

If you don't care about recovery, think about using SELECT ... INTO instead of INSERT.

Also, look up fn_get_sql in BOL