Database

When you spend more time in C# than C/AL, and you still tell yourself and the world around you that you are developing for NAV, then this post is for you. I already wrote a three-article series about “DLL hell” and how to resolve it, and in my last post in the series (…

If you are developing .NET assemblies for use with NAV, then sooner or later you’ll figure out that the new database deployment of add-ins in NAV 2016 is broken. I’ve just suffered through medieval torture of attempting to have my NAV forget about a database-deployed assembly.

Once upon a time, and really not such a long time ago, there was no such thing as a codenit type. In all honesty, there is still no such thing as a codeunit type – there is subtype , though. (Why we have subtypes, without having types, beats me, but let’s let the semantics go.) Nowadays, we have four codeunit types.

Last Friday, while enjoying a not-at-all healthy Salisbury steak with cheese, I had an interesting discussion with a partner: should NAV consultancies create default databases? A default database (in this context) is a packaged solution built upon standard Microsoft Dynamics NAV, where a…

[Updated] I had to update this post a little bit, see below for the details, but the killer feature had to go 🙁 [/Updated] Remeber that tool “ Automated Version Management ” that I published here and on Mibuso five months ago? It has just got an update: version 2.0.

I hate it when I don’t have time to blog. I’d like if I could tell you what I’ve been doing, but let’s leave it at this: I am enjoying my vacation, away from my office, my job, my projects, my customers, my partners, and obviously – my blog. You should take a vacation, too – great stuff!

I had no clue how good my laptop was. Seriously. Today it kicked ass of an 8-processor server. Tomorrow we have a go-live of a Microsoft Dynamics NAV deployment, with manufacturing customized to support configure-to-order functionality. Refreshing manufacturing orders now calculates dynamic BOMs and routings, and it takes time.

Early versions of SQL Server option for Microsoft Dynamics NAV (then called Navision) didn’t scale up as high as one would expect. Although SQL Server itself could scale up to thousands and tens of thousands of concurrent users, running a production environment of an ERP system is way different from running generic lab tests.

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.