October 24, 2016 at 5:11 am
thanks mate
it doesnt look like i need to install any backward compatibility in that case after the installation.
October 25, 2016 at 5:28 am
The SQL 2005 backward compatibility pack can be installed with any version of SQL Server above SQL 2005. It is not needed with anyt version, unless you want to use one of its components.
BrainDonor has given a list of the items in the pack. The DTS items will not work with SQL 2012 or above, but the SMO items are still usable. SMO can be a useful API to access SQL Server, even with the latest version. However, anything new you develop is best done with PoSh and not SMO.
The backward compatibility pack is completely separate from database compatibility levels. The presence or absence of the backwards compatibility pack will make no difference to the database compatibility level functionality.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 27, 2016 at 2:49 pm
sqlserverDBA2016 (10/24/2016)
i'm gonna be using ssms to run the export and import.but i'm just asking if whether after the installation of sql server 2014 , is there a backward compatibility software which needs to be installed.
Like Eirikur, I have also detached, copied, and reattached a few thousand times and never had corruption or failure.
I have, however, had issues nearly every time I used the import/export wizard to move databases.
I think it may makes sense to look at your options to make sure that this works.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply