What Jack said. Keep in mind that you'll have to restart the Agent for the changes to take effect.

Right-click, Tasks, Generate Scripts, select the objects you want to script out.

Have you enabled the mail account for Agent? That's a different step than just setting up DB Mail.

Right Click Agent, then Properties then select Alert System and Enable Mail...

Gail - I think I've been to that one. If it's the one I'm thinking of, it's slightly uphill so I don't think Steve would be interested. 😛

I...

I'm going. It'll be my first PASS summit although not my first time at the conference center. I've been to Seattle a lot over the years but I've...

Agreed. I'm finally biting the bullet and taking my cert exams for 2005. Microsoft has consistently offered an upgrade path so I'll take then when it's appropriate. ...

Other option: Drop and recreate the index. This takes up less t-log space.

Using the COPY_ONLY option on the filegroup backup works. Restore from Full then Differential backup went just fine. No idea where the errors on the other restore process...

Just to update:

The filegroup backup is indeed part of the backup chain, so restoring that and then restoring the differential backup made the restore happy.

However, the DB refused...

I've got a test machine that I'm using. I'll just be wrapping these tests into the benchmarking tests that I'm already running so not a huge deal.

Oh yeah, I'll definitely be doing some testing of all this. Of course testing on a 3 TB database on seriously underpowered machines is a very, very painful thing....

You would be assuming incorrectly.

The filegroup backup is for "archiving".

The whole (very ugly) story:

Client has an olap database that grows at a rate of ~40 GB/day (currently)

Hardware resources limit the...

That's a great thought, Jeffrey. If SQL Server is treating the filegroup backup as part of the backup chain (which it appears that it is) that would make sense....

(first_lsn, last_lsn, checkpoint_lsn, database_backup_lsn, last_recovery_fork_guid)

Differential:

117267000012837600152

117281000015665300001

117267000012837600152

115768000002956500193

E6DE692C-CC38-4630-895E-07D6FF628D47

Filegroup:

115911000022357800058

115926000014383500001

115912000000983700174

115768000002956500193

E6DE692C-CC38-4630-895E-07D6FF628D47

Full:

115767000017493200003

115884000022034300001

115768000002956500193

112308000022358800108

E6DE692C-CC38-4630-895E-07D6FF628D47

Hmmm, so maybe I do have to do the filegroup restore....

I didn't restore from the filegroup backup. That's for something completely different (developer's version of partitioning/archiving that I have to support).

Backup sequence:

FULL backup (type "D" in backup...