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.

I build as a backup/restore from production and script it that way so I can repeat the process.

Be sure that sensitive information is scrambled or changed as part of your...

My biggest issue is that the resources will be in contention. In dev it's easy for someone to test a new query and eat up all the CPU or an...

You can also script in stages, tables, then views, then procs, then logins, etc.

There are a few companies that do this, but it's $$. Protegrity was one.