When you migrate an Access database, it's similar to a split database in that SQL Server is acting as a new back-end for the data that is now located on a server.Īs a result, you can still maintain the front-end Access database with linked tables to the SQL Server tables. The front-end file must only contain all other objects, including forms, reports, queries, macros, VBA modules, and linked tables to the back-end database. The back-end database file must only contain tables and relationships. This is called splitting the database and is designed to facilitate sharing in a network environment. About split databasesĪll Access database objects can either be in one database file, or they can be stored in two database files: a front-end database and a back-end database. The following sections provide background and other information to help you get started. To successfully migrate, follow these stages. The Upsizing Wizard was removed from Access in Access 2013, so now you can use the Microsoft SQL Server Migration Assistant (SSMA). This guide gives you a smooth start to your SQL Server journey, helps preserve Access front-end solutions you created, and hopefully motivates you to use Access for future database solutions. SQL Server (whether on-premises or in the Azure cloud) supports larger amounts of data, more concurrent users, and has greater capacity than the JET/ACE database engine. So when it's time for your Access database to go to the next level, you can migrate to SQL Server. For example, an Access database has a size limit of 2 GB and can't support more than 255 concurrent users. We all have limits, and an Access database is no exception.
0 kommentar(er)
