Since they log OR the data are required to restore, I don't worry about this. dbcc will check this.

Haven't seen anything like that.

If you move the clustered index to another filegroup, it moves the table.

Yep, forgot about that one. Definitely be sure you script everything out in case you forget somthing and need to find out what it was. Permission is the main one...

No way to do it now, no plans, but we'll consider it.

http://www.sqlservercentral.com/columnists/SBoriotti/exchangefromsqlserver.asp

Not quite what you want, but they have a product to help with that.

getdate() will get you the exact minute. If you need everything from today, you'd need to calculate the current day minus the time,

select datepart(mm,getdate() + '/' + datepart(d, getdate())...

MS_foreachtable will run a command against all tables. Might be a way to script it for all indexes.

b&r - your SLA will depend on the tape SLA to get data from tape. I'd set this at some xx minutes per GB. Test in your environment.

User Access -...

Couple things.

Rename - be sure you rename the SQL Server as well as the computer.

The copy objects wizard has been flaky for me (and the task). I'd back and restore...

Scan for all servers.

Check versions/patches

Check security config

Check service accounts

Check for pwds on all accounts

Check for use of roles

Check who has any fixed roles

Be sure you check this againts software that they are using. It's possible there are reasons for downlevels. Not that they shouldn't be patched, but be sure that you know...

I'd agree about using roles. This is exactly why you do it. Take a few minutes and move the permissions to a role and then ad your new user.

You can use this to try and shrink the log

http://www.sqlservercentral.com/scripts/contributions/26.asp

You can move these selects to the FROM clause.

select a, b, c, d

from main, (select c, d, from mytable) b