Concurrency

SQL Azure is a very interesting service. It’s as interesting as it is misunderstood both in terms of how exactly it works, and what it’s intended to be used for. First of all, it’s not really the same thing as SQL Server that you install on your box, virtual or physical.

Ancient wisdom goes that you cannot have more than one write transaction going on at the same time in a single session in NAV. This is absolutely true, in and out. Some features, like Activity Log , will leave you wanting to be able to write to the database outside of the normally running transaction.

Today at NAV TechDays 2015 in Antwerp, I attended a presentation by Nikola Kukrika, Ciprian Iordache, and Gary Winter, at which Ciprian presented a new design pattern based on a new feature in NAV 2016: Activity Log.

One of the choices a customer interested in Microsoft Dynamics NAV must definitely make is the choice of the database platform. With NAV, there are two possible options: so called native database server, which is not really officially called that (the official name is Microsoft Dynamics™ NAV Database Server), and Microsoft SQL Server.