Hi Jeephound, really 17% performance hit? What about async? I can't see how the secondary being readable would impact performance of the primary? It should improve if your report writers...

Hi Perry, I have actually already looked through some of your guide mainly part 7 which focuses on what I am asking, FCI + AG. I've also read a lot...

I whether right or wrong tend to reserver 10% OS when you get to around the 64GB mark. But i round up to the nearest 2GB. So a 64GB server...

I think i might have worked out the issue at least whats been grinding the server to a halt the past few days.

This morning i came in early before there...

DB workload is OLTP, sorry should of mentioned that right off the bat.

DB has nightly maint jobs as per vendors spec which reindex, update stats etc.

BTW i read i shouldn't make any changed to maxdop or cost of parra during business hours as SQL will dump the plan cache?

So we have two HP servers running W2008r2 in a cluster. one node runs the SQL engine, the other the application engine but if a server fails the SQL db...

If your backup software supports VSS you realise SQL will let you create reasonibly reliable backups of the raw data files without stopping SQL?

I've had this happen to a Windows 2008 R2 server with DAS as well. I'd suggest opening a case with your hardware vendor as well just to check drivers and...

What are your reasons for setting up log shipping? Purely for DR or for off loading reporting? If you are thinking of running reporting even off the secondary know that...

Have you logged a case with the hardware vendor of both the servers and SAN? might be worth checking the NIC drivers are up to date? Maybe get MS involved...

Looks like someone created a fileshare on the "BACKUP" disk, given the backup disk is online and the network name is online. All you should have to do is right...

I find with clusters it's nice to have a cluster to play around in so you can test and understand changes better.

We run a Active/Passive 2 node Windows 2008 R2...

I actually had a similar issue once where the first node had an error during cluster setup but the added node didn't so to install service packs i had to...

Great thanks, in that case i might just leave the page file at the current 48GB file size.