No need to add it if you'll write it. I'm more looking for a place to keep track of holes that I find in the article base.

They do likely work because of ownership chaining, but that is not the same as including "AS DBO" in the proc. It might be OK for you today, but if...

We've talked about it, though it would require us to change some of the sending procedure to customize each newsletter. Otherwise when someone went to post a reply, answer the...

There is a difference.

If you use "as dbo" in the proc definition, then when the user executes it, it runs as if they were logged in as dbo, or an...

Default is "as the caller"

The permissions are set according to who executes it. The exception being that you might have ownership chaining enabled, so if the sproc owner owns a...

Back to SF. I have some confidence that those Texas boys will hit tonight.

This should help

http://www.sqlservercentral.com/scripts/T-SQL+Aids/31774/

sp_spaceused can be very incorrect in SQL 2000

I agree with Johan here. You have to work around this yourself by writing your own header.

It's a way of changing permissions.

If you create sproc A, you might grant execute to use Alice and Bob for this sproc. However, if you're managing security correctly, you might...

That's only part of the question. Did you not read my post? The Raid setup matters, not just the disks. For a SAN, it can also depend on SAN configuration.

A...

Again, the drive letters don't matter. What underlies the drive letters? How many disks under each one and in what format?

I'm not sure what you're asking. Your English isn't really making sense to me.

Maybe this will help.

If I have 2 drives in my server, set up in a Raid 1...

Nice, solution. Tony. I might check that out with a friend, see if we can swap some bandwidth. Especially as my Home Server has died again.

The backup isn't designed to run across a network. The fact that you have some backup waits seems reasonable to me. The network should be slower than local storage.

As far...

What's the D: drive?

Ideally you want to, IMHO, do this:

1. separate data from backups

2. Separate logs from data

3. separate tempdb from data/logs

4. separate heavily used filegroups

separate is separate physical...