You're making unfounded claims that defame the program and its members. Since I'm both (PM of the program and an MCM), I'm doubly offended by your unfounded claims. Even worse,...

I checked out all of those sites you provided links to, and none of them are selling MCM brain dumps. On the contrary, they are selling simulations that their experts...

No, I'm quite serious. Please feel free to purchase the so called MCM materials those sites offer. I assure you that it won't help you pass.

If someone is offering to...

Very well said, Steve. One of my favorite interview questions is to ask someone who is certified how they prepared for the certification exams. It gives me insight into how...

There are no brain dumps for the MCM. We have taken considerable steps to ensure that is not possible.

If you feel otherwise please point these alleged brain dumps out. I...

Just to reinforce what others are already telling you, that error means that a SQL process tried to use memory outside of the buffer pool but there wasn't enough memory...

It doesn't have to have huge transactions. If you're not backing up the log, it adds up. Obviously it is that busy because the log had to grow.

My general rule of thumb is that you should back up the log AT LEAST every half hour. If the database is busy, then do it more frequently. The busier...

Yes, I agree. Shouldn't be any harm in unchecking it.

You can't drop a user that owns schemas. You have to change the schema owner first. Expand the schemas tab and change the owner of each schema.

Make sure you are not logged in as the user when you are trying to change their permissions.

Don't uncheck public. Leave it checked as well.

Full privileges would be the db_owner database role.

You checked every single role for the user? So, you gave them (for example) db_datareader access and db_denydatareader access. A DENY (almost) always overrides a GRANT.

I have seen this before, but it resolved for me by taking another full backup. It's a bug but not a harmful bug. it doesn't indicate corruption.

Did you attempt what I recommended? (create a snapshot manually and run DBCC CheckDB on the snapshot directly).