SSIS - MDS

  • psingla

    Hall of Fame

    Points: 3840

    Comments posted to this topic are about the item SSIS - MDS

    Pramod
    SQL Server DBA | MCSE SQL Server 2012/2014

    in.linkedin.com/in/pramodsingla/
    http://pramodsingla.wordpress.com/

  • Koen Verbeeck

    SSC Guru

    Points: 258965

    Interesting question. I haven't used MDS yet, so definately learned something.

    Curious why SSIS is in the title though. At first sight it doesn't have to do anything with the MDS deployment.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • ksatpute123

    Hall of Fame

    Points: 3325

    Easy one. Thanks

  • This was removed by the editor as SPAM

  • TomThomson

    SSC Guru

    Points: 104773

    Interesting question.

    I haven't used this stuff, so my answer was based on very limited knowledge and was wrong. I'm a bit confused about this stuff. The page referenced in the explanation looks on the surface as if it clears things up, but leaves something of a problem; a better explanation could maybe clear this up (BOL doesn't, as far as I can tell). I suspect the answer to todays QOTD is right although the page it references doesn't actually support it (it doesn't distinguish between metadata and other things the package contains, while the schema for a package makes that a very clear distinction) because I am inclined to regard the BOL documentation in this area as self-contradictory so I am probably better off believing the answer than questioning it.

    But I'm still confused, and some clarification would be useful. The problem is that the information available on various BOL pages appears to contain contradictions. The Model Deployment Package XML Schema (Master Data Services) page states that the package is an XML file with a particular schema, and defines that schema: the schema appears to have no place for subscription views; but the BOL page referenced in the explanation says the package does contain subscription views; the schema puts business rules outside of the metadata element, as something separate, which contradicts the answer (but not the page it references: that page says the package contains business rules, it doesn't say they are part of the metadata - and that would make me suspect the answer today was wrong, if I could trust BOL); another BOL page (can't remember which) says that all user metadata is contained in subscription views - which seems to suggest that if user-defined metadata is not allowed in the package it can't contain subscription views, another apparent contradiction in BOL; collections are not mentioned anywhere in the schema, but the answer and the page it references says they are in the package, another contradiction.

    I guess people can see why I'm confused; maybe someone can tell me which bits of BOL I should believe on this topic?

    Tom

  • ksatpute123

    Hall of Fame

    Points: 3325

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

    I believe the question was picked directly from here.

  • TomThomson

    SSC Guru

    Points: 104773

    ksatpute123 (9/6/2013)


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

    I believe the question was picked directly from here.

    I hope not. If it was, whoever did the question totally misunderstood the page; the question is about metadata; the only thing the page says about metadata is that there is no user-defined metadata in the package as deployed.

    Tom

  • jan.dewettinck

    Default port

    Points: 1492

    Not sure if this helps. But I looked at

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

    and found under Next Steps

    User-defined metadata, file attributes, and user and group permissions are not included in model deployment packages. After you deploy a model, you must update these manually.

  • Thomas Abraham

    SSChampion

    Points: 10761

    jan.dewettinck (9/6/2013)


    Not sure if this helps. But I looked at

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

    and found under Next Steps

    User-defined metadata, file attributes, and user and group permissions are not included in model deployment packages. After you deploy a model, you must update these manually.

    Same information is given in

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

    which does not involve the use of the wizard.

    [font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
    Connect to me on LinkedIn

  • jfgoude

    SSCrazy

    Points: 2586

    cnerver used it! did someone do ? only 733 answer tit his question people seemed not very concerned

Viewing 10 posts - 1 through 10 (of 10 total)

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