• Yes , you are right about catalog table....I can use that for name, description, parameters.....but my requirements for documenting rdl also needs drill thtough links, datasource, dataset fields ......

    I have tried building SSIS package but rdl files has some namespace problem, so I was not able to use XML source using plain xml from rdl files and xml schema provided by microsoft.....It returned me errors saying namespace issue....

    So now I am trying to write Xquery that returns me elements and attributes i need so i can store them in database and use that. But the problem i m facing is to get the specific level for the elements in the huge rdl file. for ex. I have 4 drill through link in one report, all are in different data regions so the element level is different for each of them. :crazy: ...and I am also new with xquery...

    Powershell is totaly new thing for me.....so if you can point me to some good sites/articles that explains either powershell to do this kind of stuff or ssis package or xquery....anything will work for me to get this done....thanks in advance...