once that's done, take a copy of your front-end and re-link the tables to the RDS database.Īt this point, you'll need to look at any SQL queries in the VBA within your front-end as SQL Server uses a different SQL dialect to Access (or at least it did the last time I did this in 2013).Go through the upgrade wizard on that local backend and upgrade to your new RDS instance.Create a copy of the backend Access database onto your local machine.Create an SQL Server instance in RDS (so this manually at first and choose the smallest instance your you can get away with).What you'll need to do is test out this procedure and see what happens: It will create the tables, migrate the data and create linked tables for you. Happily, Microsoft have built an upgrade wizard into Access to allow you to migrate from an Access database to an SQL Server database. Your application has now started to reaching the limitations of a pure-Access model, and you are fortunate to have a leadership team who recognise the importance of both your application and of migrating it properly. Many IT professionals deride Access because they do not understand its place in the software ecosystem, but it is a perfectly valid and appropriate choice for the things it excels at. Deciding what to do with your front-end in the future.Migrating from an Access backend to an MS SQL Server backend (you could migrate to MySQL or Postgres but going to SQL Server will be far less painful).You've got several separate things going on here: If you're posting a technical query, please include the following details, so that we can help you more efficiently:ĭoes this sidebar need an addition or correction? Tell us here public IP addresses or hostnames, account numbers, email addresses) before posting! ✻ Smokey says: reduce meat and dairy to fight climate change! Note: ensure to redact or obfuscate all confidential or identifying information (eg. ![]() ![]() News, articles and tools covering Amazon Web Services (AWS), including S3, EC2, SQS, RDS, DynamoDB, IAM, CloudFormation, AWS-CDK, Route 53, CloudFront, Lambda, VPC, Cloudwatch, Glacier and more.
0 Comments
Leave a Reply. |