Okay, so it does appear that the Governance Dashboard does not check for the <Lineage> element in the QVD metadata xml, even though when AllowDataLineage = 1 is configured, you do get database connection and statements in the QVD xml metadata, like:
<LineageInfo>
<Discriminator>Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Data\ABC_1.0.mdb;Mode=Share Deny None;Extended Properties="";Jet OLEDB:System database="";Jet OLEDB:Registry Path="";Jet OLEDB:Database Jet OLEDB:Engine Type=5;Jet OLEDB:Database Locking Mode=1;Jet OLEDB:Global Partial Bulk Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database Jet OLEDB:Create System Database=False;Jet OLEDB:Encrypt Database=False;Jet OLEDB:Don't Copy Locale on Compact=False;Jet OLEDB:Compact Without Replica Repair=False;Jet OLEDB:SFP=False</Discriminator>
<Statement>LOAD CategoryID,
ItemCost,
ItemPrice,
ProductID,
ProductName,
QuantityPerUnit,
SupplierID,
UnitCost,
UnitPrice,
UnitsInStock,
UnitsOnOrder;SQL SELECT *
FROM products</Statement>
</LineageInfo>
However, there is a limitation here in that the QVD will list all load/select statements and store ... into statements from the QVW that created it - not just the ones specifically related to it. In other words, if you have a QVW which loads from four different database tables -- resulting in four distinct data tables in the QVW - and each of these is stored to QVD, all four QVDs will list all four data connections and load statements. So there is no programatic way that I know of to correctly specify which Load connection(s)/statement(s) apply to each QVD that is generated.
In summary - there are two limitations in play:
1- QVD metadata (xml) includes all lineage metadata from its CreatorDoc QVW, not just ones related to the table stored to QVD.
2- Governance Dashboard does not capture the Discriminator and Statement lineage data from QVDs (only the CreatorDoc).
