I've been assigned to a project where I need to have high availability for a Asp.Net with MSSQL 2000 or 2005. We have two Dell servers that are of medium quality. Unfortunately that's where the budget stops. We do happen to have iscsi laying around so I figured I'd throw together a test environment (while watching excepts from kb89179<img src='/community/emoticons/emotion-11.gif' alt='8)' /> and followed the process for installing the SQL server. I had to make the nodes AD's (which was done prior to the install of CS and SQL2005). I've got a about 5 hours into it and I'm wondering if this is the path that I need to go down. We need high availability DB only. The web app is stateless and can actually be on both nodes at the same time. Unfortunately I really can't afford to spring for a iscsi array for this project (mostly out of pocket myself for an NPO).<br /><br />So I have two questions...<br /><br />1) If I want to continue to use the cluster similar to that above, is there a way to do it without the shared array. I have read various acticles that talk about local mirrored qorum files. This would be optimal. <br /><br />2) Do I even need to cluster this? I was thinking of Merge replication and have each node just use localhost and sync internally and use Windows Load balancing to do the rest. <br /><br />The machines are Dual Xeon Dell's with 4gb ram each and mirrored 250gb SATA drives.<br /><br />Any advice would be greatly appreciated.