Just to be clear, you should not be regularly running shrinks. This is for emergencies only. Keep free space in your files to handle normal operations.

We have been debating about starting a sister site here for Oracle. Good to know there's a call for it.

You can see some of Mr. Denny's work at SearchSQLServer and we link to his articles here at times.

I think most of these books will work. Just be sure that...

Then only chance for determining this if it's not in the logs is using a log reader. I'm not sure if this is logged, but for 2000 you can download...

There aren't any tables? What are the views of?

Note that you perform these operations on the virtual node, not either instance. If you do that, most things work across both nodes.

Note that as mentioned above, there is only...

You can't schedule more often than every minute, can you? At least in SQL Agent.

Every 2 seconds sounds quite often. I'd be tempted to run this as a job, but...

First, be aware that you want to have free space in your database files. These are not Excel or Word files. Free space is needed for data growth.

Second, is this...

First, I think you need to use the four part naming, not ....

Second, are you sure the credentials used for the linked server can access that item?

You want to keep a few around. When there are issues, it's possible someone will reboot 2-3 or more times and you don't want to have those logs gone. 6...

I most often see bad drivers reported as the issues on this site. HBAs are complicated and their drivers (out of date, mismatched firmware, something like that) seem to be...

There are some process tools at sysinternals as well that can help you dig down into more detail on which processes if you want to go that far.

I'd tend to...

One more thing, don't delete an old backup (or overwrite it) without having a new backup. I've seen people do this:

- delete old backup

- run new backup

Which one day will...

I'm older school, but I'd go with

create proc

insert b (colA, colb, colc)

select otherColA, otherColb, otherColC

from a

return

Note that your restore scenarios should look at how often data changes. If you change data often, and can't afford to recreate those changes, you need to back up often...