Forum Discussion
SSMA For Access not recognising DateTime/Extended fields
I have already posted up about this here:
https://www.access-programmers.co.uk/forums/threads/ssma-bug-with-date-time-extended-fields.334442/
The current version of SSMA fails to recognise fields set to the DateTime/Extended when trying to migrate to Azure SQL
It fails to match the data type and therefore fails to migrate any of the data from any table with any of that type of field.
I'd appreciate it if this could be fed back to the SSMA team.
4 Replies
Can you provide a small repro accdb with the required tables and fields?
Also, can you specify which version of SSMA you are using? "Current" meaning?I see that you did provide a repro accdb in the other post.
There is no way to add the new, previously defined datatype DateTimeExtended, in SSMA. Maybe there's another workaround, but it sure does look like converting the datatype in Access is the way it will need to be done to support migration, even though SQL Server supports DateTime(2).
Hi George,
Just for information - I'm using SSMA version 10.2
The work arounds are fine for smaller projects but on a large migration would be a massive extra workload, especially if you were frequently replacing the data from a live environment during development, assuming you couldn't change the data types in the live system.
