Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


M.Rys M.Rys

Niner since 2005

  • DataBound Episode 2 - Semantic Search

    @srikalyan: There is not really an ontology behind it (yet). We are extracting keyphrases or tags (in this case only 1-grams, although the algorithms could also handle n-grams). That information is made accessible in relational form through the table-valued functions. Generating and supporting ontologies is definitively something we are looking into for the future. How close that future is depends on many things though. What do you mean with access priviledges and authentication? This feature is integrated into SQL Server with Fulltext search so you have the standard SQL Server access controls.
  • DataBound Episode 2 - Semantic Search

    One update, the languages supported now include several different versions of Chinese Smiley
  • DataBound Episode 2 - Semantic Search

    @BLinden:All the SQL Server Full-text iFilters are supported. So in the case of XML or HTML, we will not index the markup tags or attribute names. If you want PDF support, you will need to install a third-party PDF iFilter such as Adobe's or FoxIt's.

  • Anders Hejlsberg - LINQ

    "Is at least the fact that all of this is done with strong typing something new?"

    This depends. XQuery and SQL both provide for both static and strong typing on declarative expressions. However, the integration into the programming language type system is well-done (and thus could be considered "novel").
  • Michael Rys - XML in SQL Server

    Thanks for the comments.

    Regarding the killer use cases for XML: I try to address this somewhat in the non-demo part. If your XML describes basically relational data that you want to repurpose, slice and dice in different ways, shredding it into relational form and doing normalization is a good idea. If the XML OTOH is representing a markup document (such as a WordML or XHTML document), or the XML represents a logical unit (aka object) which you want to store and retrieve as efficiently as possible while still having the ability to query into its components, storing the data as XML is easier and often preferrable.

    Best regards