Sage 100

This is probably not supported by Sage, but has anyone implemented Sage 100 Premium on Microsoft Azure SQL? I've managed to get the data migrated and circumvented the user creation but are getting a few errors. When I apply SQL Settings, ""MAS_User Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Inavlid object name 'sys.server_principals'. MAS_Reports Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Inavlid object name 'sys.server_principals'."" If I test connection, I get the following: ""[Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'MAS_User'. Login failed for user 'MAS_Reports'. (err/ret=34/0) Appreciate the insight!

When playing with permissions, this is how I ensure they are set properly (on all the MAS_ databases): `use MAS_###; exec sp_changedbowner 'MAS_User'; exec sp_dropuser 'MAS_Reports'; exec sp_grantdbaccess 'MAS_Reports'; exec sp_addrolemember 'db_datareader', 'MAS_Reports';`

It looks like the sys.server_* fields don't exist in Azure SQL (replaced with sys.database_* (https://stackoverflow.com/questions/30674051/azure-sql-invalid-object-name-sys-server-role-members), so you'll probably need to maintain logins and passwords manually.

Kevin, did you ever get this to work in Azure? I managed to get MAS_System to work. I can create new users and other things fully contained in System files, but apparently Azure doesn't support cross-database queries so Company Maintenance which is MAS_System checking into MAS_ABX doesn't work. Likewise, MAS_ABX doing anything at all doesn't work due to not being able to read System settings. Microsoft is looking into a workaround for me, but at this point, it seems like this isn't an option.

(I've not worked with Azure... my advice was for SQL permissions in general).

My only experience with Azure was testing SQL Mirroring to see if I could have them work together which I was able to. The biggest difference with SQL Mirroring and Azure was I had to manually create the database - it wouldn't allow LMSQ to create it. I would agree with what @SteveIwanowski said. But with the things that I learned about Azure - I wouldn't be surprised if you ran into other issues also.