Cause: After migrating data, hyperlinks in columns lose their functionality and become simple nvarchar(max) columns. Cause: If you later update your SQL Server or SQL Azure tables to contain data types that are not supported by Access, you cannot open the table in Access.
The primary audience for this course are existing database professionals with experience of SQL Server 2014 who want to update their skills to SQL Server 2016.
Additionally this course is for existing SQL Server 2014 MCSAs who want to prepare for the Upgrade exam for SQL Server 2016 certification.
Important To link access tables with an Azure database, you need SQL Server Native Client(SNAC) version 10.5 or above.
You can obtain the latest version of SNAC from Microsoft® SQL Server® 2008 R2 Feature Pack.
Note Your Access tables remain in Access, but are not updated together with SQL Server or SQL Azure updates.
After you link the tables and verify functionality, you might want to delete your Access tables.If the SQL Server or SQL Azure table definitions are altered, you can unlink and then re-link the tables in SSMA by using the procedures shown previously in this topic. To update linked tables by using Access The following sections list issues that might occur in existing Access applications after you migrate databases from Access to SQL Server or SQL Azure and then link the tables, together with the causes and the resolutions.Cause: Some queries might be slow after upsizing for the following reasons: Cause: After calling Record Set.In Access, the tables appear with a "linked" icon, which is a globe with an arrow pointing to it.When you open a table in Access, the data is retrieved using a keyset cursor.This opens a dialog box through which you can navigate to the folder that contains your database.