Hi All,
Last night I tested migrating my backend of a split access 2013 database to an SQL database on the Azure platform.
Remember that saying, I only wish I knew then what I know now:
Also, does anyone have any experience with SSMA and how to accurately debug these kinds of issues? Immediately, I am thinking I will need to rename some fields, and this potentially means updating a whole lot of queries with new field names. Also, I am looking at basically redesigning a bunch of form fields with queries. And I have not read the entire SSMA metadata report yet. So, part of me thinks, well, maybe I would be better off starting from scratch with a new back end for Azure, and redesigning an entire front end for that instance.
Thoughts?
Last night I tested migrating my backend of a split access 2013 database to an SQL database on the Azure platform.
Remember that saying, I only wish I knew then what I know now:
- Trying to be clever, I named my timestamp fields When in Access, but this is reserved in SQL (ding)
- Trying to enforce quality, I established more than a few fields in the tables as lookup fields, and lookup fields are not allowed in SQL (ding) - this means that in order to have lookup fields in forms, I need to probably create a query for every lookup field I have in order to deploy on Azure.
Also, does anyone have any experience with SSMA and how to accurately debug these kinds of issues? Immediately, I am thinking I will need to rename some fields, and this potentially means updating a whole lot of queries with new field names. Also, I am looking at basically redesigning a bunch of form fields with queries. And I have not read the entire SSMA metadata report yet. So, part of me thinks, well, maybe I would be better off starting from scratch with a new back end for Azure, and redesigning an entire front end for that instance.
Thoughts?