June 17, 2009 at 12:45 pm
Thanks Ven, looks like Standard 2008 does the same.
http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx
Coming in at approx $5000/ea processor license. For kicks, estimate this project would cost:
2 x Servers @ $7000
1 x SAN @ $10000
2 x Switches @ 2500
2 x MSSQL Proc Lic @ 5000
----
$39,000
June 17, 2009 at 12:56 pm
Interesting concept, thanks for an eye opening article. However, as a fan of the 'Keep it Simple' club, I'd prefer not to have to configure & keep updated all of the clustering requirements/options/services etc. if not absolutely necessary. We have several clustered servers, active/passive, active/active. I'd have to keep cluster manager up all the time if all the 150 others were single node clusters. We use dns alias when switching servers to avoid code/client changes, & log shipping from the old to the replacement until the actual switchover.
June 17, 2009 at 2:11 pm
Previous versions of cluster services were very particular about the installation process. So much so that in the event of an error sometimes it was easier to start over rather than debug the issues. On top of that installing SQL Server and adding it to a 2nd, 3rd, etc node was not always so straight forward.
Have you found any obvious stumbling blocks on taking Nodes/SQL Servers in and out of the clustered environment?
June 18, 2009 at 5:59 pm
Great idea! Using cluster to simplify hardware upgrades and minimize resulting impact to the end users. Thank you!
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply