You don't really want to use the timestamp type, rather a datetime marked at the time or some flag that indicates where they were. I'd post the data and insert/...

I like Chris' suggestion and would use that.

I'm not sure this is available in this extended stored procedure.

It's a stored procedure, so an insert..exec will do it

create table mytest( drive varchar(2), mb numeric)

insert mytest exec master..xp_fixeddrives

select * from mytest

drop table mytest

I'm sure they are aware, but this is the easiest way for them to deploy BOL.

I don't see why this wouldn't work. I haven't tried it, but the instances should be separate. One will have to be named, of course.

I've noticed as well. It's on our list.

why do you care? Extra procs have no impact on the system.

It does add a small load, but it also runs quicker (each one runs quicker) because there are less transactions to back up. Won't affect your diffs, but be sure...

Haven't heard anything to date.

using DMO, SQLServer2.ListAvailableServers

I'd go with your schedule, though if I could I'd do the diffs to disk. Anything to have a 2nd copy. Same for the logs, recovery will be quicker if...

Enjoy!!!!

I went twice last year and never got picked. Not sure if that was good or bad.

Not sure about the upper limit. What you said makes sense, though I suspect it's more that interchanges of data with other systems may warrant limiting to 4 digit years.

As...

alter or create need to be the first thing in the batch. I typically always drop and recreate, but I keep the security with the code.