Congrats (just in case).

My word for the day is noise (kids off from school)

That's an image I can do without.

Each instance is completely separate, as though they were on separate machines. One cannot reference the other easily.

You can set up a linked server between the instances. It's not hard,...

You are welcome, but Michael brings up something I'd forgotten to mention. Maintenance is an issue. If you have an app (db) that is being patched/changed more often than others,...

You can always resize if you need it. If your tempdb is not growing often, you should be OK.

It's the growing that's an issue, not the size.

If this is the Microsoft DPM product, I think you need separate groups.

Doh was yesterday's.

Today is "so-close-to-the-weekend-I-can-taste-it"

Andrew has my advice, though if you're not sure, take a guess. Don't leave it at 1MB. I might go for 10% of largest main db size as a...

I'll give this paper as a reference: http://msdn.microsoft.com/en-us/library/ee692366.aspx

Like everything else, this has some level of tradeoff on how you do it. I like VMs since they're easier to move to...

Some info here: http://www.sqlservercentral.com/Forums/Topic484784-146-1.aspx

I'd agree with the above. Use the Export wizard or Import Wizard to get a base package.

It's likely a filter change on your end. We added a DKIM flag, required by some large ISPs

This is definitely a place where the OS and SQL should align the partitions and align the cluster/page size when you create a DB as well.

I'd do what Gus has listed.

I suspected no assignment, but I had these visions of C where = means something happens.