not to defend Microsoft because I have the same complaints about speed, but they design for future hardware. They always have so that the new OS takes advantages of hardware...

Andy Warren has a saying I love. "Always use the defaults until you have a reason, and know better, why something else should be done."

I think that applies here. Those...

The question has been edited to show SQL Server 2005 as the context.

I'd agree with Andy. The issue I have with datareader is that it automatically gives rights to all tables. So if I add a table to store anything, meta information...

Heck, I used to enjoy karate tournaments.

Easy to tell who wins when only one is still standing 😉

I'd agree with Michael. You want notification of failed backups from that group. If they don't want to let you know, bring up the issues and show it's needed so...

Run it from the server as well. When you run it from your workstation, it runs under the context of your workstation. When it's scheduled, it runs from the server....

If you have Enterprise, potentially you can snapshot it

If you restore it with STANDBY, you could query it and suck out data.

EXECUTE AS for the add login step.

Otherwise do what you are doing.

SQL Server will search all rows that meet the WHERE clause, with matches and perform the update.

Run a trace.

The only things that truncate a log file are a checkpoint if you are in simple mode, or the backup log command.

CHECKDB has nothing to do with it.

you've given spots of information there. Did SQL install or not?

What are the complaints about specifically? What are the people doing?

I think it's a bit of luck, timing, and location.

There are always jobs around, and there are plenty of places that do value staff and try to keep them. There...

I would suggest you call Microsoft to go through the dump and help you determine what happened.

You should not stop the service to do backups. SQL Server does native online backups while the service is running, and that is the way you should back up your...