That's too much for low memory servers and too little for high memory servers.

Chapter 4: http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/

Depends on how the application is written. Ask your developers.

If the restore never finished, drop the DB and restore again.

Did the restore finish without error?

I prefer a conservative approach to memory. Set max server memory lower (the 40 out of 48) and if monitoring shows available memory, increase it slightly. Repeat until happy.

Heard the same about The Old Republic, which I'm in the process...

GSquared (12/18/2012)

---

Amusingly enough, Mayans vs Vikings is part of one of the dungeons in The Secret World. Apparently the Vikings brought Excalibur to North America and used it to...

Schema != owner

That proc is old (pre SQL 2005) and hence changing schema and owner, before SQL 2005 they were the same thing.

Use ALTER AUTHORIZATION to change owner and...

Triggers.

CDC and Change tracking are SQL 2008 features (you posted in a 2008 forum,...

As I said, it's not going to be corruption. (and one does not depend on the error...

I'll just repeat what I said earlier

Even with normal tables, you can't just automatically create whatever the missing index DMVs suggest, unless you want a huge amount of redundant and...

Execute as owner does not use the...

Yes it is. No, you do not.

At most you may want to drop...

Stale statistics. Almost certainly.

It's not corruption. Corruption doesn't cause performance problems. Corruption causes severity 24 error messages.

Impersonation? Got procs with EXECUTE AS 'sa' in them?