SQLSentry has a great tool as well.

Backup log yyy to disk = xxxx

Copy xxxx to zzzzz

THe Agent can instantiate a Command prompt batch file that does the copy. Powershell or VBScript can handle this.

Restore doesn't run under a user ID. It runs under the service account. That account might not have rights to that path.

this error occurs when you try to insert a value for the identity column in a table that has the identity property set.

If you set up replication, do not replicate...

The check should work

if exists (select from ... day = day, month = month, etc.)

Then I'd disable those not used for 90 days, but I wouldn't remove something until 365...

you could easily check to see if the person had already logged in on that day by checking user name, day, month, year before inserting.

However, are you trying to just...

I would second GSquared's suggestion.

Yes, use the SQL Server 2008 version

It looks OK, however your design would allow multiple projects per job. If that's not the case, it doesn't make a lot of sense to build the separate table unless...

The installed might need to do something, create db, add users, etc. Likely it doesn't need sysadmin, but it's probably not worth figuring it out, unless you want to document...

#s 1 and 2 are why I also recommend you touch your resume every quarter.

And what worries me about #2 is that people will just accept the answer and run things, not bothering to check themselves if they can't check first.

I'll admit there are...

Lynn is correct. You'll be fine, and I wouldn't stop any full or diff backups due to log shipping.

There are a few issues with snapshots.

they don't stay up to date. They are a point in time. To update it, you need to either drop the snapshot and recreate...

You can't selectively restore logs, but you can continue to restore filegroups (new FG backups) over time.