i've had a rash of these lately. seems like upgrading to SP2 or reinstalling SP4 on sql 2000 helps

for the curious, seems to be a bug. we had two published...

have you tried to run it manually?

if you figure out how to make major changes to a publication without a new snapshot, let us know. it would make my life a lot easier.

as far as i...

you need to run maintenance on subscribers as well

strange

we did SP2 and the 3161 hotfix over the weekend and SP2 installed everything on both nodes. we failed everything over to 1 node, installed SP2 and then failed over...

were the other nodes up and reachable over the network? i've found that with clusters all nodes need to be up even if you fail everything to one node

we use scripts and do indexing and statistics in that order

if you have the budget get the fiber one. even though i've never used iSCSI, i don't trust it

if you don't have IIS it will flash a warning before installation. that is probably what he meant

i think you will have to set it up where the VPN connects automatically, have them log into the domain over VPN, etc

you could try moving the tembdb to another volume. RAID5 takes a hit on writing and this could be the issue

haven't installed it yet, but looks like it's a lot of of BI

go table by table and see which one has the most rows and why

are you doing a lot of updates in your db or a lot of deletes combined with inserting new data? theoretically this can cause the log to be twice as...

i always remove sql 2005 first then the rest of the components like SNAC, BOL and whatever. it's like 5 uninstalls.