Starting from the question and working backwards.
My question: is it OK to use
SQLNCLI10.1 as a provider for SSIS 2008 R2 to connect to SQL Server 2012 database(s)?
I have a SSIS box running SQL Server & SSIS 2008 R2. The SSIS packages connect variously to different data sources including different SQL Server databases, and some of these databases are on SQL Server 2012. In line with the general principle that you would use the right provider for the source you are connecting to, I would expect that the "right" choices are
SQLNCLI11 to connect to SQL Server 2012, and
SQLNCLI10 to connect to SQL Server 2008 & 2008 R2.
SQLNCLI10.1 connects fine to SQL Server 2012 and appears to be fully functional and bug free.
Couple this with these other factors:
The SSIS box I refer to is one element of the dev lifecycle so to change this box means also installing v11 on several other boxes.
The added complexity of having to choose the right provider for the right DB Connection instead of a single SQLNCLI (there are no SQL Server 2000 / 2005 sources to worry about). Especially since the ConnMgr doesn't allow you to change it once set.
Issues such as this which imply there are greater risks in using 11 over 10.
I realise open or discussion type questions are frowned upon, so, Q&A:
Are there any RISKS in staying using
SQLNCLI10to connect from SQL Server 2008 R2 (SSIS) to SQL Server 2012?
Would there be any performance loss for the same, over using v11 instead?
Am I losing functionality or risking breakage by using 10.1 instead of 11.x?