Loading ...
Sorry, an error occurred while loading the content.

Re: [SQLQueriesNoCode] Any gotchas with heirarchyIDs in SQL Server 2012 or 2012 Express?

Expand Messages
  • Paul Livengood
    I have used this in 1 project I did.  I didn t need to, but I wanted to see how it worked.  I did not notice any major issues with it, but external
    Message 1 of 2 , May 15, 2013
    • 0 Attachment
      I have used this in 1 project I did.  I didn't need to, but I wanted to see how it worked.  I did not notice any major issues with it, but external developers I brought in all had to be trained and that cost time and dollars. 


      ________________________________
      From: Charles Carroll <911@...>
      To: "SQLQueriesNoCode@yahoogroups.com" <SQLQueriesNoCode@yahoogroups.com>
      Sent: Wednesday, May 15, 2013 10:05 AM
      Subject: [SQLQueriesNoCode] Any gotchas with heirarchyIDs in SQL Server 2012 or 2012 Express?


       

      http://technet.microsoft.com/en-us/library/bb677173.aspx

      We are about to use these on a project and I know sometimes MS
      releases a feature that sounds wonderful, but has some HUGE bugs or
      perf issue that magazines and books are afraid to report on lest
      retribution and shunning.

      So did any of you use HierarchyIDs sucessfully in a project. We don't
      have massive data on this projects but we don't want to commit to
      everything revolving around HeirarchyIDs and find out the querys would
      be slow until a hotfix or next version for example.

      Many Many years ago for example I based a project on
      Full Text Search
      http://msdn.microsoft.com/en-us/library/ms142559%28v=sql.105%29.aspx
      and ran into major user concurrency limits that were quite embarassing
      yet admitted to in KB articles after one had already written lots of
      code assuming the feature works.
      For example 'hit highlighting' is a current gotcha i.e.
      http://www.sqlperformance.com/2012/09/t-sql-queries/hit-highlighting-in-full-text-search
      and a million years ago in sql server 7.0 text search had a 9 user
      limit I am not kidding one had to upgrade to 2000. I wondered how they
      could "sell" and publish articles on 7.0 for searching considering
      that huge flaw.



      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.