LOB Data

  • Guys I think we should close on this now.

    All of us are coming up with the same point that it is the issue of framing the question.

    If anyone is sharing some knowledge that would be great for all of us.

    I hope u all don't mind.

    With Best Regards

    🙂

  • I found this question to be very subjective, even the reference listed did not make a preferable option but listed them. If my data is in xml format then xml is preferred so .query .nodes can be used to interrogate the data.

  • stewartc-708166 (3/11/2011)


    The options listed are classified as Large-Value data types, not LOB's

    refer:

    SQL2005: http://msdn.microsoft.com/en-us/library/ms178158(v=SQL.90).aspx

    SQL2008: http://msdn.microsoft.com/en-us/library/ms178158(v=SQL.100).aspx

    SQL2008R2: http://msdn.microsoft.com/en-us/library/ms178158(v=SQL.105).aspx

    And yet this:

    http://msdn.microsoft.com/en-us/library/ms187752.aspx

    In SQL Server, based on their storage characteristics, some data types are designated as belonging to the following groups:

    Large value data types: varchar(max), nvarchar(max), and varbinary(max)

    Large object data types: text, ntext, image, varchar(max), nvarchar(max), varbinary(max), and xml

    From the above one can conclude that varchat(max), nvarchar(max) and varbinary(max) are classified as being both. I guess we must have a data class known as chameleon except instead of changing color it changes what group it belongs to? ? ?

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • bitbucket-25253 (3/11/2011)


    stewartc-708166 (3/11/2011)


    The options listed are classified as Large-Value data types, not LOB's

    refer:

    SQL2005: http://msdn.microsoft.com/en-us/library/ms178158(v=SQL.90).aspx

    SQL2008: http://msdn.microsoft.com/en-us/library/ms178158(v=SQL.100).aspx

    SQL2008R2: http://msdn.microsoft.com/en-us/library/ms178158(v=SQL.105).aspx

    And yet this:

    http://msdn.microsoft.com/en-us/library/ms187752.aspx

    In SQL Server, based on their storage characteristics, some data types are designated as belonging to the following groups:

    Large value data types: varchar(max), nvarchar(max), and varbinary(max)

    Large object data types: text, ntext, image, varchar(max), nvarchar(max), varbinary(max), and xml

    From the above one can conclude that varchat(max), nvarchar(max) and varbinary(max) are classified as being both. I guess we must have a data class known as chameleon except instead of changing color it changes what group it belongs to? ? ?

    I second that

    Regards
    Sushant Kumar
    MCTS,MCP

  • I guess we must have a data class known as chameleon except instead of changing color it changes what group it belongs to? ? ?

    It's not a chameleon, it just has a membership to more than one group.

    Like, I'm a driver, a human, an employee, a man, an animal (grrr!) ... but I ain't a chameleon.

    _____________________________________________________________________
    [font="Comic Sans MS"]"The difficult tasks we do immediately, the impossible takes a little longer"[/font]

  • My apologies. Points have been awarded back to the people that have answered and the question has been corrected.

  • Well, that's one of the plusses to getting in to the office late... the radio buttons were already changed to check boxes by the time I answered the QotD. 😛

    As for the debate of large-valued vs LOB, and XML, I think it may have been addressed in some of the other links (I didn't follow them all), but here in cut&paste form:

    In SQL Server, based on their storage characteristics, some data types are designated as belonging to the following groups:

    Large value data types: varchar(max), nvarchar(max), and varbinary(max)

    Large object data types: text, ntext, image, varchar(max), nvarchar(max), varbinary(max), and xml

    From http://msdn.microsoft.com/en-us/library/ms187752(v=SQL.100).aspx

    Now if one of you fart smellers smart fellers could explain difference between 'large value' and 'large object' data types, that would be appreciated! 🙂

  • Thanks for the question. And yes waiting until later in the day to answer the QotD does help. Thanks to everyone for debugging the question! 🙂

  • Steve Jones - SSC Editor (3/11/2011)


    My apologies. Points have been awarded back to the people that have answered and the question has been corrected.

    Thank you Steve 🙂

    M&M

  • Steve Jones - SSC Editor (3/11/2011)


    My apologies. Points have been awarded back to the people that have answered and the question has been corrected.

    But unfortunately the explanation hasn't been corrected. It still refers to an article which gets it wrong (as has previously been pointed out by other commenters) although there is a perfectly clear and relevant BoL article (Table and Index Organization) and still talks about "preferred" LOB types (what does "preferred" mean? If it means "undeprecated" say that, not "preferred") and the list of types is still wrong (Filestream should not be there but is; varbinary(max) and CLR User Defined Types should be there but are not).

    Something obviously went wrong here; that's something that can happen and the question has been fixed, so no issues with the question and the correctness of the answer; but it's a great pity that the explanation wasn't fixed too and will continue to mislead those who see it and refer them to a misleading reference to reinforce that unfortunate effect.

    Tom

  • Tom.Thomson (3/11/2011)


    But unfortunately the explanation hasn't been corrected. It still refers to an article which gets it wrong (as has previously been pointed out by other commenters) although there is a perfectly clear and relevant BoL article (Table and Index Organization) and still talks about "preferred" LOB types (what does "preferred" mean? If it means "undeprecated" say that, not "preferred") and the list of types is still wrong (Filestream should not be there but is; varbinary(max) and CLR User Defined Types should be there but are not).

    Something obviously went wrong here; that's something that can happen and the question has been fixed, so no issues with the question and the correctness of the answer; but it's a great pity that the explanation wasn't fixed too and will continue to mislead those who see it and refer them to a misleading reference to reinforce that unfortunate effect.

    Yah I wondered about the CLR User Defined types. Since spatial is implemented via CLR they seemed to fall into the camp of LOB.



    --Mark Tassin
    MCITP - SQL Server DBA
    Proud member of the Anti-RBAR alliance.
    For help with Performance click this link[/url]
    For tips on how to post your problems[/url]

  • Thanks for the question

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • The spatial CLR user-defined data types are LOBs/large objects? Really???

Viewing 13 posts - 31 through 42 (of 42 total)

You must be logged in to reply to this topic. Login to reply