Are the drives busy constantly or just at night when LanDesk is running? Id' expect an index rebuild to spin them as you are moving data around.

What's the solution you want? this makes no sense. If you need the data, you need more disk space. If you can delete data, do that.

and re-tune those queries.

The data cache is supposed to fill up with data for queries. If you have bad queries, then are they not reused? Or is just certain queries...

The log backups should let you know what total size your logs need to be to handle the load. Track this across a few weeks, multiple days to see the...

Thanks for the complement on the podcasts. I'm working on it slowly. Enjoy next Tuesday's blooper reel 🙂

As far as the login, we push out a cookie, which is how...

There's no issue with a table with 36M rows, or even 12 * 36M rows even. However if you want to easy reporting, you might look at partitioning and swtiching...

It's nice to see new people participating and I appreciate the responses, comments, and criticisms. It's good to get a debate going on something.

I don't expect everyone to participate, though...

I believe it's the job that fails if sa changes in places.

You could have set credentials in the maintenance plan to connect as SA, which would be a bad idea....

It's normal for SQL Server to spike to 100%, but if it was more than 5-10 minutes, more than a query going hard, I'd be concerned about performance.

Everything logged passes through. If you add a column to a table, it moves to the mirror.

Pull the plug! Not sure that you can do anything else.

There is a switch to start SQL Server without going through recovery.

Why do you want to stop it? This is...

If you go into the properties for IIS, there's a place where you set security. You can set anonymous users with credentials, which is where you can input a Windows...

That one is good. Every so often they have some good database jokes mixed in there.

My PC goes into energy saving mode, but I reboot probably less than once a month. XP, even 2000 before it, have been extremely stable. If you're not getting that...

select * hits every row. If you have an update in a transaction locking those rows, which is what it does, then you can't read every row.

Try reading specific rows,...