There isn't, but a nice suggestion.

If this is for DR, you might not want to have this automated to that level. A DR server potentially will have a different name, different IP addressing, different drive...

I would second a look at replication

If you don't want that, you would have to run a script on each server to add the stored procedure. You can script that...

You can script everything with a right click/Generate script.

But I think Lowell's method might be the quickest way to do this and easier to edit if you need to.

Five no-nos this year.

Might be a record year at this pace.

My wife and son saw it and loved it. Said it was non-stop action and funny.

I would also look at perhaps changing the fillfactor a bit to leave more free space, and perhaps limit page splits.

If it has different IP addressing, I think you can move the endpoint to a new address.

There is no undo. Log software, as Scott mentioned, builds a reversing transaction, but it cannot undo the transaction.

Restore from backup to another system, and then copy the data back....

I use the same rule as defaults. Use them until you have a reason to use something else. If maintenance plans work, use them. If you need to go beyond...

You see see, or change it, here: http://www.mssqltips.com/tip.asp?tip=1583

You can definitely do it. I think that the world of databases needs a little maturity, something many young people don't have.

I know some great developers that are older, and...

As I've learned to run and swim (yes, you learn how), I find that I get some great thinking time there. Driving as well.

Don't use the Wizard. Add in each task you need, multiple copies as needed, and set them with precedence constraints.

If the database is restoring, meaning you restored with the NORECOVERY option, you cannot take a backup.