A family of Microsoft relational database management systems designed for ease of use.
Again, check your default database.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am trying to use the above tool to migrate an Access backend database to SQL Server.
It ran fine on my PC under SQL 2017 and migrated to the correct SQL database. When I run it on my Client's Server under SQL 2022 the tool tries to create the tables in the Master database not the destination database I have selected, and then fails as I don't have permissions to create tables in the Master database.
Any clues?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
Again, check your default database.
It should be pretty easy to understand. SSMA needs to know where you want to create the migrated tables. If you don't tell SSMA which database to use, it's forced to pick one (or fail) and the path of least resistance for that choice is Master.
"Oh, you didn't want Master? Well, tell me. Which database you DO want to create the tables in? If you make that one the default, I can use it, but I'm not going to keep guessing...."
On the database on my PC and on the database on the Server I have db_owner rights.
I just wanted to comment that it's a good thing the process fails when trying to create user tables in Master....
I assume the login running the tool has rights to the intended target database. I had this issue a decade ago and resolved it by setting the login’s default database to the target database.