I didn't see the note about starting the shrink and changing the files.

I'll update the question to clarify.

SQL Kiwi (1/24/2012)

---

That's a fair point. ...

But you can ski? Maybe down the street in Bellevue 😉

I won't be attending either. Too committed to other stuff...

As I was just told, this is the launch, not release.

Tend to agree with Gail. Set it. If it gets changed, investigate why, but it shouldn't be.

If you are only worried about daily backups, leave it in simple.

Eric M Russell (1/24/2012)

---

I can't vouch from personal experience about what goes on at the corporate sales and marketing conventions, but I've heard rumors and have this mental image ......

Having attended lots of conferences, it seems that it's the exception rather than the rule that people are skipping sessions and taking a vacation. The vast majority of the people...

Switching to simple breaks your recovery chain, if you are backing up logs and expecting to recover to a point in time.

ISNULL - http://msdn.microsoft.com/en-us/library/ms184325.aspx

Or Coalesce - http://msdn.microsoft.com/en-us/library/ms190349.aspx

I'm with Gail. Separate backup file every day, with timestamp in the name.

Maintenance plans will do this. Ola Hallengren has a great script on this site that can help you...

what's the variable supposed to be? Or how does it change? you're leaving out lots of details.

For example, if this is a date, you can configure the script to pull...

Yep, in 2008 the backup to a file defaults to append. http://msdn.microsoft.com/en-us/library/ms186865.aspx

It is possible that you have multiple backups in this file. You can use RESTORE HEADERONLY to find this...

Where are the variables? How are you setting them? You many or may not need to pass them in, depends on what you've done in the code.

Glad you liked the question. I was working on something else and learned a few things here.

Sad panda face.

Since Girardi left, but he's been someone I've enjoyed watching.