I'm no expert in this...and now just use the 'shipped-with-server' views. However before we had this, we had to put it all together ourselves (which is where some of these great blogs/posts came from). Although things may have changed a little, this video (and some resources) was excellent (although things maybe a little different now, I imagine it's still 95% useful!)
The specified item was not found.
about half way down called "Raiders of the Lost Postgres" and here's the thread TDT: Raiders of the Lost Postgres - February 19, 2015
not an expert...but hope that helps
Thanks Simon for the info and I will certainly check it out. As a server admin, I do use the Admin views. But our workbook publishers what insight into the workbooks they are creating. So, building some custom views into this information is required.
Simon, I reviewed this material and while it did not get me exactly what I was after, it did provide some ideas that may help. The following really helped out.
2 of 2 people found this helpful
While not the prettiest SQL I've ever written, here is what I came up with (see attachment). I hate the subqueries that I'm joining to, but it was the quickest way to deal with the custom views\views\workbooks issue.
While not the prettiest SQL I've ever written
...If it works, it works!!
Nice work Lee, and many thanks for coming back and sharing the SQL...I may have a play with this myself!!