Export Option for Excel

adam_hafneradam_hafner Posts: 91 Silver 2
in SQL Dependency Tracker
Can you add the ability to have Excel output for the dependency list?  I know you can export to XML but it would be much more valuable to users to have a direct output to Excel format where it would list the object, what uses that object and what objects it uses just like in the PDF, but something that could be edited or expanded upon.
Tagged:
· Share on Twitter

Answers

  • Jon_KirkwoodJon_Kirkwood Posts: 441 Gold 1

    Hi @adam_hafner

     

    Thank you for reaching out on the Redgate forums, I can submit this to our developers as a potential feature request.

    Looking through our internal systems; I have referenced a few requests for an ability to export a list into Excel over the years. However, there hasn't been enough demand previously to prioritize implementing this feature.

     

    Currently, the solutions provided within the application are to export the XML and open into Excel or to copy the diagram and paste it into Excel or similar programs as an image.

     

    I did some testing and used Excels data import to bring tables from the PDF export into Excel; as a rough test it did import as separate books within Excel, but it may be possible to build a solution using that export.  

    Jon Kirkwood | Technical Support Engineer | Redgate Software
    · Share on Twitter
  • adam_hafneradam_hafner Posts: 91 Silver 2
    @Jon_Kirkwood Would you be able to provide some instructions on how you were able to import this into Excel?  I tried something similar, but it was not intuitive and I couldn't get anything that was very useful without a lot of effort.  So if there's something I was overlooking, I am open to suggestions for a workaround until an Excel output could be possible.

    Thanks!

    --Adam
    · Share on Twitter
  • Jon_KirkwoodJon_Kirkwood Posts: 441 Gold 1

    I was testing using the Insert > Get Data > From PDF menu option to import the exported info from SQL Dependency Tracker.

    This method wasn't the cleanest, as it imported each table as a separate tab. I was able to do some automation using this method but got unwieldy with larger exports.

     

     

     

     For XML I found I needed to enable the Legacy XML import wizard in Excel (File > Options > Data > From XML Data Import (Legacy)

    This allowed me to import the XML file and then could do some ETL processes to get workable data in Excel

    Jon Kirkwood | Technical Support Engineer | Redgate Software
    · Share on Twitter
Sign In or Register to comment.