What's New in SSMA for Access(AccessToSQL)
This topic lists SSMA for Access changes in each release.
The January 2012 release of SSMA for Access contains the following changes:
Provided the option to not persist username and password for MS Access linked tables after migration.
Set cascade actions for circular references to No Action.
Provided proper messages indicating cascade actions for circular references have been set to No Action.
The April 2011 release of SSMA for Access contains the following changes:
Single Installable of “SSMA for Access”, which supports SQL Server 2005, SQL Server 2008, SQL Server “Denali” and SQL Azure.
The ability to connect SQL Server “Denali”
SSMA for Access Console version supports backward compatibility. You will be able to open the projects created by versions earlier to SSMA v5.0
SSMA v5.0 product can be installed side by side (SxS) with older versions of SSMA Product.
The July 2010 release of SSMA for Access contains the following changes:
Support for migrating to SQL Server 2008 R2 and SQL Azure
Secure connection to both SQL Server and SQL Azure.
Support for Access 2010 databases
New SSMA Console application for command line execution
Support for SQL Server DateTime2 data type
The May 2007 release of SSMA for Access contains the following changes:
Support for Access databases that use workgroup policies.
The ability to delete converted objects from the SQL Server metadata explorer.
Support for user-entered comments the SQL Server formatted SQL mode.
Improvements in object conversion.
The November 2006 release of SSMA for Access contains the following changes:
A new Database Migration Wizard that guides you through the migration of a single database from Access to SQL Server.
A new Convert, Load, and Migrate command that converts Access databases, loads the converted objects into SQL Server, and migrates data into SQL Server all in one step.
Improved query migration. Query migration now converts more SELECT queries to views. For more information, see Converting Access Database Objects.
You can now edit table and index properties on the SQL Server Table tab.
New global settings:
You can opt to show line numbers in editor windows.
You can configure SSMA to prompt to replace duplicate objects, or always or never replace duplicate objects during schema conversion.
A new conversion option lets you specify if SSMA displays a warning when a complex query contains a wildcard.