So the news here is that we can use Azure’s SQL services for Dynamics NAV data rather than creating a virtual machine and installing SQL as we would do on premise.
This means that we get a more scalable SQL service managed by Microsoft rather than having to manage it ourselves (or more likely your partner doing it for you).
In reality though, at this point, I believe that only the smaller standard Dynamics NAV installations will go this route. There is less flexibility, with no option to go direct to the data that is a get out of jail card sometimes with a standard SQL installation. How we can tune the performance parameters with Azure SQL services I not aware of yet but it’s still very early days. None of us has spent much time looking at these services because we had nothing to use them with.
My prediction is that in the future this will become much more significant but for 2016 I’d be surprised if one in ten used it.
This post is part of a 9-part series. A link to all the posts in this series are below (updated as published);
- Part 1: First Public Sight
- Part 2: Dynamics NAV 2016: Functionality
- Part 3: Dynamics NAV 2016: CRM
- Part 4: Dynamics NAV 2016 : Office 365 with PowerBI
- Part 5: Dynamics NAV 2016: Workflow
- Part 6: Dynamics NAV 2016: e-Everything
- Part 7: Dynamics NAV 2016: Windows
- Part 8: Dynamics NAV 2016: Engineering
- Part 9: Dynamics NAV 2016: Azure