ok - I can't draw anything from the errors but I have worked with san storage from way back when. The real problem with storage this way is that often...

I'm not 100% sure of your question but the network service belongs to the local machine so its domain will be the server name. It's a local service.

welcome to the wonderful world of replication! if you read though BOL and/or a couple of books or there must be stuff on sql server central, you'll find out...

hmm .. not done stuff like this for some time - it may be possible to restore the last full backup and then put back indivdual file groups and then...

last time I looked there was a "script" option in SSMS for this - or you could capture in profiler - or you could just use BOL and lookup restore...

I have to ask why on earth you'd want to make such a simple thing as a backup so difficult?

Your domains have to have a trust releationship set as far...

sorry I disagree, on a x64 system with 64GB of ram allocating 60GB to sql server is too much. The allocated memory is only for data cache it does not...

you can use the format ( dot net ) command in ssrs to make the date look like however you want.

I'm sure you have this but - a blanket value for iops on a san is not helpful - you should break that down by lun/database and read writes. ...

with respect you're assuming the load produces fragmented indexes - I have a different situation but similar process - although the index was not fragmented it needed to be rebuilt...

never worried about being on call, done that on and off for around 16 odd years. Generally there are not many calls, if there are then you fix the problems...

OK - tricky. There's a number of posts on my blog about benchmarking and testing storage and the basic code/tests I use are here http://www.grumpyolddba.co.uk/infrastructure/sqlbenchmark.htm

Essentially we did the sequential load...

you can change the sql service accounts in the usual mannner, although I'd advise caution. Never tried to change a cluster service account - not something I'd want to try...

the whole point on all this is you have to find what works for you. If your system is 7 x 24 then your problems are different to those for...

to achieve exactly what? Anything which uses a client not on the server is subject to fluctuations in connection speed/bandwidth. For example in a rdp session on the server...