SSDT & DACFx (October 2012) Compatibility Notes

Rate This
  • Comments 2

We recently released a new version of the DACFx runtime, DACFx (October 2012). This latest release brings with it several changes that affect compatibility between DACFx and SQL Server Data Tools (SSDT).


  1. User attempts to exercise DACFx functionality within SSDT including browsing a server/database in SQL Server Object Explorer, using Schema Compare, or opening a Database Project.
  2. User attempts to use a .dacpac inside SSDT via Schema Compare, Add Database Reference, or Import from .dacpac.


  1. Warning dialog surfaces similar to the image below stating: “This version of SQL Server Data Tools is not compatible with the database runtime components on this computer”clip_image002
  2. Error surfaces in one of the following pathways:
    • Import from .dacpac – "Internal Error. The internal target platform type Sql100DatabaseSchemaProvider does not support schema file version '2.5'" or "An incompatible dacpac was encountered."


    • Schema Compare - “Schema Compare cannot handle this dacpac version.”
    • Add Database Reference - “<dacpac file> is not accessible or is not a valid schema (.dacpac) file.”


  1. SSDT September 2012 and previous SSDT releases are not compatible with this new version of DACFX.
  2. Packages created by this release of DACFx (and later) containing Selective XML Indexes (SXI) or packaged table data cannot be consumed by previous releases of DACFx and SSDT.


DACFX (October 2012) introduces a new package format and support for features available in SQL Server 2012 Service Pack 1. These changes impact compatibility with SSDT resulting in the use of this newer DACFx version to be blocked to avoid compatibility issues customers could experience. This compatibility issue does not impact SQL Server Management Studio (SSMS) or other client tools.


  1. Although DACFx (October 2012) is not compatible with previously released versions of SSDT, it ships with and is compatible with the newly released SSDT November 2012 available here.
  2. Previous releases of SSDT and DACFx do not have support for features mentioned above that may now be part of DAC packages. These packages cannot be consumed by previous versions and this behavior is expected.

Note: If you have already acquired DACFx (October 2012) to enable scenarios in other Microsoft products which depend on this latest version of DACFx, removing it to repair SSDT will break these scenarios.

Leave a Comment
  • Please add 5 and 5 and type the answer here:
  • Post
  • First of all, why don't you start using a version scheme, so it is easier to distinquish between versions. It is much more likely, that v1 and v2 are incompatible, than september release and october release are. Also when are you going to use the buildin update mechanism in visual studio 2012? With these frequent releases, it can be a problem to keep developer tools in sync when some update and some doesn't, and there is no easy way for the developers of getting info on updates, except going to this blog.

  • Agree with Mikael, SSDT, VS2010 and VS2012 with TFS client on the same machine is turning into a full time maintenance job. I'm doing more troubleshooting of my toolset than I am working on fixing bugs in my own code these days.

Page 1 of 1 (2 items)

SSDT & DACFx (October 2012) Compatibility Notes