Voted Best Answer
Mar 10, 2016 - 01:49 AM
Link below is the offical "rules" on multiplexing which includes diagrams on what works and what doesn't. This is the best guide available and has been contintually updated for many years (although current download is 2014).
Basically if there is no break in the chain from the data going in to the data going out all endpoints need to be covered by a SQL CAL (or Per Core licensing if you cannot count or if it is cheaper).
However, it will depend on how you "export" the data from one system to another. I've worked on cases where there is a stop in the data when it is converted into .csv files and then loaded into a seperate system, although through an automated process it was a break in the SQL Chain, which was deemed the entry point for the data (by Microsoft).
Best route to identify is to look at the entire process for any breaks in your chain and identify what those breaks are. Make sure you have an LSS involved (Licensing Specialist not an Account Manager) or your LSP and get mutliple opinions.
Basically if there is no break in the chain from the data going in to the data going out all endpoints need to be covered by a SQL CAL (or Per Core licensing if you cannot count or if it is cheaper).
However, it will depend on how you "export" the data from one system to another. I've worked on cases where there is a stop in the data when it is converted into .csv files and then loaded into a seperate system, although through an automated process it was a break in the SQL Chain, which was deemed the entry point for the data (by Microsoft).
Best route to identify is to look at the entire process for any breaks in your chain and identify what those breaks are. Make sure you have an LSS involved (Licensing Specialist not an Account Manager) or your LSP and get mutliple opinions.
