I have seen the edition comparison from Microsoft (
http://www.microsoft.com/sql/prodinfo/f ... tures.mspx) but I have heard a few more NAV related differences. Can anyone please confirm these differences:
* Ability to rebuild indexes and statistics without locking. (Guess this is the "Online Indexing" section)
* Better execution plan due to more intelligent usage of indexed views
* Additional datatypes to reduce the size of a database and even improve performance.
Anything else to consider before selecting edition?
Comments
1. Unlimited CPU-s, 4 only for standard
2. Table partitioning
3. Online indexing
4. Online restore
5. Fast recovery
6. SSIS Advanced Transforms
7. Oracle replication
8. Advanced Business Analytics
9. Advanced data mining
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
That is really the border line decider between the two in most NAV implementations.
As far as I know does MS consider one cpu for one cpu, no matter if it is a single or dual or quad core, right?
Peter
Someone can confirm this, but I think the change was from SQL 2000-2005, I think it was SQL 2000 where every core counted towards license. But now they count sockets, so 2 Dual core or 2 Quad core CPUs both count as two sockets for license purposes. Think sockets and its a lot easier to work it out.
I have a client with 8 Dual core CPUs, 16 gig of RAM and about 34 Hard drives. Its quite common to see the CPU usage MAX out, and for sure they would like more CPUs and RAM.
Keep in mind also that Eight Dual core CPUs is faster than four quad core CPUs.
The next thing to consider though is the TempDB. Theoretically that client also need 16 RAID 1 arrays just for their one tempdb per CPU. Currently we have just one RAID 1 for the TempDB and it seems OK though.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Using these feratures reduced an Axapta database by 90% and improved performance.
These changes are defined in DDL, so until Navision supports this, Navision users will see no benefit. Since these changes are transparent to the application, it should be simple for them to support IF they want to do it.
http://mibuso.com/blogs/davidmachanick/