BE CAREFUL : NEVER IMPLEMENT A HOTFIX IF IT IS NOT NESSESAIRY THIS IS A VERY NEW HOTFIX AND IT MIGHT CONTAIN ERRORS For everyone who is involved in the art of performance tuning of the Dynamics NAV (Navision) product on SQL Server 2005 I would like to focus some attention on this hotfix. Slow performance...
I know that this blogpost is far from orriginal but I am always looking for this information so I am putting it in my blog The table $ndo$dbproperty has a field DatabaseVersionNo. This is a list of recent versions. With special thanks to Dean McRae! / Database versions for: 2.50 // 1 : Beta 1 data formats...
The link below lists build numbers, KB numbers and links to cumulative updates updates 1 to 9 for SQL Server 2005: List of build numbers and cumulative updates 1-9 for SQL Server 2005 Also see this post for relevance of SQL Updates to Microsoft Dynamics NAV: Overview of updates for SQL Server 2005 SP2...
Today we are installing SQL2005 on a VMWare environment. We already support several customers on VMWare but this is the first time we are actually doing the migration. This customer was looking for a failover system for the entire network which was easy to mangage since they do not have in house IT....
This post has the following three purposes: Give awareness that there are updates available for SQL Server 2005 SP2 Give an overview of what the available updates mean in relation to running Microsoft Dynamics NAV on SQL Server 2005 Help deciding whether a customer who runs Microsoft Dynamics NAV on...
The current release cycle for SQL 2005 SP2, is to release a new update every 2-3 months. Currently (November 19th 2007), the latest update for SQL 2005 SP2, is update 4, which is available here : http://support.microsoft.com/default.aspx?scid=kb;EN-US;941450 The updates for SQL 2005 SP2 are all accumulative...
I have seen a number of (good) arguments that some issues with Dynamics NAV on SQL2005 are caused by a bad query optimizer in SQL2005, and that the SQL teams need to fix this. After all, some issues we see on SQL2005 did not exist in SQL2000. This blog tries to argue that SQL2005 is maybe more clever...