I just got my first chance to install SQL Server 2012 on a test machine. I also installed all of the management and Visual Studios components. I created a copy of one of my SSIS 2008 packages and converted it to 2012. The conversion worked jsut fine, but I'm now getting an error stating that connections to SQL Server 2000 and earlier versions are no longer supported.

Is there a workaround for this? Is there another way to create a connection to a 2000 database? We're not currently in a place to move this database off of 2000.

The connection is currently set up as an OLE DB connection for a couple of data sources.

  • I don't have enough reputation yet to post comments, so I guess I'll have to post here: Could you maybe create an ODBC DSN to the server / database and use that instead of OLE DB? – Levi W Jun 13 '12 at 15:27
  • What connection manager (ole, odbc, ado) are you using to talk to the SQL 2000 instance? Is it being used as a source, destination, lookup, something-else? – billinkc Jun 18 '12 at 17:40
  • @billinkc added info – DForck42 Jun 18 '12 at 18:17
  • Well you could upgrade your SQL Server to an instance. I don't mean to sound callus but your server will be able to buy cigarettes in a few years. – Zane Feb 1 '14 at 5:35
  • @Zane Ehh, we've finally gotten rid of it. Now to update all the things. – DForck42 Feb 7 '14 at 22:08

Apparently, the SQL Server Native Client 11.0 (the one that ships with SQL Server 2012) does not support SQL Server 2000. All you have to do is change the data source to use a .Net Provider (SqlClient Data Provider) instead of the Native OLE DB provider. The .Net Provider probably doesn't perform quite as well as the Native OLE DB but it was definitely a lot less work that having to build a bunch of new ETLs to stage the data and a lot less risky too.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.