Allen Kinsel - SQL DBA

SQL Server, PASS, and other data mishaps

SQL/Windows Clustering Stupidity

By Allen Kinsel, 5 months and 12 days ago

Win98 300x225When is high availibility not? 

When its any version of SQL running on a clustered Windows 2003 Server or sql 2005 running on clustered Windows 2008 Server.  Seems that while you can dynamically add a disk and use it in SQL when your running a standalone server, if your running in a «highly availiable» cluster configuration you have to take SQL offline to add the disk as a dependency in order to be able to use it within SQL.  Here's the proof right from SQL books online.

Im sure there was a good reason to require this at the time but clearly this wasnt thought out in the grand scheme of taking 0 downtime.  Anytime a single server has a more highly availiable architecture than your system that is designed for high availibility -->youre doing it wrong, Sorry someone had to say it

Related posts

Share this post

No comments

Be the first to write a comment on this post.

Write a comment

If you want to add your comment on this post, simply fill out the next form:





* Required fields

You can use these XHTML tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>.

No trackbacks

To notify a mention on this post in your blog, enable automated notification (Options > Discussion in WordPress) or specify this trackback url: http://​www.allenkinsel.com/​archive/​2010/​02/​sql-windows-clustering-stupidity/​trackback/

Follow Me


Tags

Allen Kinsel on Twitter

Categories

Most Recent Posts

Subscribe

Archives

Next Posts

Latest comments

  • Community Choice Sessions at the PASS Summit 2010:
    • Allen Kinsel: Thanks, We hope that this will be a good test of community selections, and hope to expand it a bit in the future
    • robert cook: glad you decided to keep blogging and gracias to you and your amigos for giving an opportunity to the sql community for direct involvement with session choices
  • Sql Server and SSPI handshake failed error hell:
    • Robert L Davis: I agree about the reboot. That's why I check SPN's before DC/Kerberos errors. An SPN can be fixed without rebooting, but if the issue is DC connection and no one can log in to the SQL Server, you're down anyway so a reboot shouldn't be out of the question. The problem with having a...
    • Allen Kinsel: I guess should have worded that a little differently, in my experience in a lot of environments kerberos isnt used since its not configured, so it always falls back to NTLM, with only NTLM and no Kerberos in the result list, its usually safe to say that SPN's arent the issue. I...
    • NULLgarity: This post should win an award. These SSPI errors have cause me all sorts of trouble over the years and are EXTREMELY difficult to troubleshoot. In my experience, they often went away before I even had a chance to look into them. Thanks for the post!
    • Shawn Melton: It's been a while since I have done SA duties with AD but I would be curious too. I actually have a User Group meeting tonight (06/17/10) with an MCT that teaches AD and will ask him if he can explain that authentication mess.
    • Robert L Davis: sys.dm_exec_connections does not tell you what protocol they used to attempt their connection. It tells you which protocol suceeded. Kerberos is ALWAYS tried first and NTLM is used as a failback. So if they show as using NTLM, it's not because they didn't attempt to use Kerberos, its because Kerberos wasn't successful. In my...
  • SQL Saturday 35 Recap:
    • Jen McCown: Cookout, eh? Maybe we'll have the next after party at chez McCown :)

Most commented posts