![]() It was only when the final "Pure" 2012 servers were built out that the old driver disappeared and packages failed. The developers had both drivers on their machines and so did the db servers we originally deployed to. In SSIS 2012, our packages use an "OLE DB\SQL Server Native Client 10.0" connection to access the SQL Server 2000 databases (we actually just edited the connection strings and changed Provider from "SQLNCLI11.1" to "SQLNCLI10.1"). ![]() It installed alongside the existing 2012 SQLNCLI11 driver nicely. It is worth noting that when following the solution from squillman/technet/etc, while installing the 2008 SQLNCLI.msi on one of our new servers, we received the error "Installation of SQL Server 2008 failed because a higher version already exists on the machine." Despite this, the driver was installed and worked properly without hurting 2012 db server functionality. The SSIS server error that started our research was: "The requested OLE DB provider SQLNCLI10.1 is not registered" That is, it never had SQL Server 2008 installed or an older OS. Our problem occured because the hosting db server never had the old SQL 2008 "SQLNCLI10" installed. We followed these suggestions to install SQLNCLI10 on our 2012 database server. The First Answer From Sqillman ( ) works! Kudos!įor us, the answer (above/below?) allows access to SQL Server 2000 databases from SQL Server 2012 Integration Services packages that are hosted on a SQL Server 2012 database server running on Windows Server 2012 OS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |