the best way is management

if this is policy than you should report every violation of it to the powers that be. the second best way is to use windows authentication...

when a failover happens the mssql service stops on one node and starts on the other. my guess is that it kills any connection and running process

not sure, but my guess is yes

every time we had a failover we had to restart apps because they lose connection to the sql server. in this case the backup...

have you checked the execution plan? we had a similar issue except it was faster on the sub and it turned out to be statistics

over the last week i tracked down some old army friends, some of which i haven't talked to for 8 years. sent some emails, made some calls and found some...

i don't think so

we have 2 critical db's with heavy inserts. in each case the main table is around 300 million rows. one gets inserts of data all day long...

i agree

our main critical db's used to be simple recovery model until a few months ago. the san would copy them to another set of volumes and attach to another...

one of our servers does more than this. pretty funny doing a profiler session on it with no filters. press play and stop and in a second or so you...

yes, it's in the read me in the sp for vista installs with the details

i would also install 3257 on top of SP2 as well

we do this all the time

some of our pubs don't replicate indexes and we create a custom set on the sub

this will also depend on the network connections of each server, the server hardware itself, the destination of the backups and the network traffic at the time

why not just switch it to simple recovery if you aren't doing log backups?

you need SP2 and at the end it has a part to configure it for Vista

here is a solution for jobs

we have some dev sql servers where the developers make their own sp's and keep there. rule is that anytime someone wants a new copy...

right now the chatter is to run weekly fulls and keep them for 6 weeks and the log backups also only for a few weeks. then run another full backup...