More Training Titles Released for Microsoft Dynamics NAV 2009

Brand new training titles have been released and are available on PartnerSource and CustomerSource (account required). The trainings are available as downloads and as instructor-led training (ILT).

Upgrading Microsoft Dynamics NAV 2009 Native Database to Microsoft SQL Server

This training is designed for individuals preparing to upgrade Microsoft Dynamics NAV 2009 Native database to Microsoft SQL Server. This training covers the upgrade process from preparing existing data, configuring Microsoft SQL Server, troubleshooting data issues, to validating data after upgrade.

PartnerSource: https://mbs.microsoft.com/partnersource/communities/training/trainingmaterials/student/course80298.htm?printpage=false

CustomerSource: https://mbs.microsoft.com/customersource/training/trainingmaterials/student/course80298.htm?printpage=false

Microsoft Learning: http://www.microsoft.com/learning/en/us/Course.aspx?ID=80298A&Locale=en-us

Microsoft SharePoint Technologies and Microsoft Dynamics NAV 2009

This training is designed for individuals who want to integrate Microsoft Dynamics NAV 2009 with Microsoft SharePoint technologies.

PartnerSource: https://mbs.microsoft.com/partnersource/communities/training/trainingmaterials/student/course80297.htm?printpage=false

CustomerSource: https://mbs.microsoft.com/customersource/training/trainingmaterials/student/course80297.htm?printpage=false

Microsoft Learning: http://www.microsoft.com/learning/en/us/Course.aspx?ID=80297A&Locale=en-us

Microsoft Dynamics NAV and SQL Server Database Compression

Microsoft SQL Server 2008 introduces two new compression features (available in Enterprise Edition) that are of interest to users with large databases. Data compression applies to individual tables and indexes within a database and comes in two options: ROW and PAGE. Backup compression is a new option when backing up a database to external storage. Both compression techniques can be used to reduce the amount of online storage required for databases. Data compression can be configured for an entire heap (table with no clustered index), clustered index, non-clustered index, or indexed view. For partitioned tables and indexes, the compression option can be configured separately (and differently) for each partition. Compression can also reduce disk utilization and sql memory utilization as dead is stores on disk in a compressed state and also reads in the SQL cache in a compressed state. Compression can add 10 - 30% percent increased CPU utilization depending on what tables and indexes are compressed and what level of compression is used.

For Dynamics NAV we recommend only compressing tables and indexes that have a read to write ration of 80%/20% (This is a conservative threshold) or higher as compressing tables with a higher write ratio can actually decrease performance. We also recommend using ROW compression if the space saving between ROW and PAGE level compression is less that 10%; if the difference is over 10% then we recommend PAGE compression. This is because if the space savings from PAGE compression is close to or similar to ROW compression then it is not recommended to incur the additional overhead associated with PAGE compression. An example of NAV tables that would benefit greatly from compression are the large "Entry" tables such as G/L Entry, Value Entry, and Item Ledger Entry. An example for NAV tables that would not benefit from compression and where performance may actually decrease due to compression are "Line" tables where the data is temporary in nature such as Sales Line, Purchase Line, and Warehouse Activity Line. SQL Server compression is completely transparent to the Dynamics NAV application.

Compression is done on Table or Index basis. On tables with clustered indexes the clustered index is the table so compressing the clustered index is equal to compressing the table. Running the ALTER TABLE.. WITH COMPRESSION is only necessary on HEAPS for all tables with Clustered Indexes you can use the ALTER INDEX.. WITH COMPRESSION.

How to determine the read/write ratio of an index? Luckily SQL keeps track of this for us and all we need to do is extract this data. SQL Server stores this information in the sys.dm_db_index_operational_stats DMV. Remember DMV's are "recycled" each time the SQL Server service is restarted so if SQL has only been up and running for a day or a week this information will be of minimal use. Ideally you would want the server to be up any running for several weeks and through a month end close to get a true idea of actual data access patterns of your database.

The following query will tell you how long the SQL Server instance has been up and running:

select 'Sql Server Service has been running for about '
+ cast((datediff(hh, create_date, getdate()))/24 as varchar(3)) + ' days and '
+ cast((datediff(hh, create_date, getdate())) % 24 as varchar(2)) + ' hours'
from sys.databases where name = 'tempdb'

The following query will give the approximate read write balance of all the used indexes in the database.

SELECT o.id,
o.name,
x.name,
i.index_id,
x.type_desc,
s.rowcnt,
i.leaf_update_count * 100.0 /
(i.range_scan_count + i.leaf_insert_count
+ i.leaf_delete_count + i.leaf_update_count
+ i.leaf_page_merge_count + i.singleton_lookup_count
) as Writes,
i.range_scan_count * 100.0 /
(i.range_scan_count + i.leaf_insert_count
+ i.leaf_delete_count + i.leaf_update_count
+ i.leaf_page_merge_count + i.singleton_lookup_count
) as Reads,
FROM sys.dm_db_index_operational_stats (db_id(), NULL, NULL, NULL) i
JOIN sys.sysobjects o ON o.id = i.object_id
JOIN sys.indexes x ON x.object_id = i.object_id AND x.index_id =
i.index_id
JOIN sys.sysindexes s ON s.id = x.object_id and s.indid = x.index_id
WHERE (i.range_scan_count + i.leaf_insert_count
+ i.leaf_delete_count + leaf_update_count
+ i.leaf_page_merge_count + i.singleton_lookup_count) <> 0
AND objectproperty(i.object_id,'IsUserTable') = 1


You can also run a simulation with the sp_estimate_data_compression_savings stored procedure in SQL with will run a sample of the data through the chose compression level and give you the estimate of the space saved by enabling compression.

I strongly recommend reading the following MSDN article before engaging in database compression activities.

http://msdn.microsoft.com/en-us/library/cc280449.aspx

Note: You can use the following query to check to see if there are currently any compressed indexes in the database.

SELECT o.name Table_Name, p.index_id as Index_ID, i.name as Index_Name,
CASE
WHEN p.data_compression = 1 THEN 'ROW Compression'
WHEN p.data_compression = 2 THEN 'PAGE Compression'
ELSE 'ERROR'
END Compression_Type
FROM sys.partitions p
JOIN sys.objects o ON p.object_id = o.object_id
JOIN sys.sysindexes i ON o.object_id = i.id AND p.index_id = i.indid
AND p.data_compression in (1,2)
ORDER BY o.name, p.data_compression, p.index_id


Source:
http://blogs.msdn.com/b/nav/archive/2011/02/11/microsoft-dynamics-nav-and-sql-server-database-compression.aspx

Microsoft Announces the Availability of Management Reporter for Microsoft Dynamics ERP

Microsoft has now announced the general availability of Management Reporter for Microsoft Dynamics ERP. Management Reporter, formerly codenamed Management Reporter 2.0, will act as the replacement for Microsoft FRx,

www.newscom.com/cgi-bin/prnh/20000822/MSFTLOGO

Management Reporter extends the proven functionality of Microsoft FRx and enables people to quickly and easily create, generate, help secure and publish professional-looking financial statements, such as profit and loss statements, balance sheets, and cash flow reports, and will also allow them to take advantage of the following:

• Custom reports without IT assistance. These reports reduce the burden on the IT department by empowering the finance team to create its own financial statements.

• Deep cross-functional analysis. Management Reporter provides easy and accurate financial reporting, intercompany reconciliations and eliminations.

• Reduced training time and increased productivity. A familiar user interface and reporting tools minimize training time since users will easily be able to transition from Microsoft Office applications to the similar navigation pane and toolbars in Management Reporter.

• Strong data integrity and report accuracy. Management Reporter supports regulatory requirements, such as generally accepted accounting practices and international financial reporting standards.

"Management Reporter is like Microsoft FRx on steroids — it takes the familiar building blocks of Microsoft FRx and revolutionizes the way reporting and business intelligence can be delivered," said Les Wright, senior consultant, BDO Canada LLP, a Microsoft Dynamics partner. "This is something customers have been asking for and provides even more value to their Microsoft Dynamics ERP solutions."
Microsoft FRx customers making the transition to Management Reporter will experience a variety of new features including the following:

• Direct integration to the Microsoft Dynamics ERP general ledger. This integration aids in simplified, real-time reporting with greater accuracy.

• Reusable building blocks. Blocks of Report, Row, Column and Tree definitions can be mixed and matched to produce a wide variety of boardroom-quality reports.

• A Report Library. A Report Library is where reports can be secured, stored, and viewed

Management Reporter is available for Microsoft Dynamics GP 2010 customers at NO ADDITIONAL COST and will be available with future releases of other Microsoft Dynamics ERP solutions.

To assist customers currently using Microsoft FRx make the transition to Management Reporter, a migration tool, detailed guidance and information is available at

www.microsoft.com/dynamics/en/us/products/management-reporter.asp

Direction of Microsoft Dynamics NAV

Based on Microsoft Dynamics NAV Statement of Direction – April 2010

Microsoft has now announced that NAV is going to support for Unicode with the release of Dynamics NAV "7", which will be released next year - 2011. This will also mean that we are finally going to say goodbye to Navision's native database, which otherwise have served very well basically since the release of the first DOS version of Navision in 1987. It is a goodbye to this REALLY GREAT & SUPER STABLE database.

Unicode has been too much of a worry to the average Navision customer. But for international customers, who have been working with many different countries in the same database, then it's going to be a great help.

NAV "7" will also be another goodbye. With the release of NAV “7”, "Forms" are also going to be disappeared. "Forms" have been the data presentation object until NAV 2009; however with the introduction of the “Role Tailored Client” - “RTC”, it is now the "Pages" which is providing the data presentation to the user. The "Forms" are still used in the Classic Client, but now with the removal of the "Forms" then the typical NAV user will no longer be able to use the Classic Client. (Fortunately) Developers will still have to use the Classic Client, until new development tools will be available in the “Role Tailored Client” with NAV "8" in 2013.

Future of NAV Development Environment

The C/SIDE development environment is going to be replaced from Classic Client to RTC. As you know, still we have to depend on the NAV Classic Client for making any customization, even though we do the implementation in RTC, but this structure is going to replace with the upcoming versions of Dynamics NAV. Some of the highlights would be as follows;

1. No Object Designer! Simple. This will be replaced with Designer Home Center; it will be another role center which allows developers/consultants to make any changes to the standard objects of the application.

2. Page Designer will be replaced with another page where it will allow you to proceed with your table customizations. This feature will be brought into the other object types as well.

3. In the Object List, developer will find the all objects including data about where they used and information about the usage.



4. No Visual Studio! Own simple editor for making all changes in Code Units.



5. The structure of the Editor would be more towards to the look & feel of the Visual Studio. For example the Symbol menu is to be replaced; any parameter that you define will be available in the top of the code lines.

To be continued …

Source:
www.dynamicsuser.net/blogs/kine

Navision Employee Portal

Employee Portal provides a Web-based interface that gives employees quick access to mission-critical business information such as invoices, customer data, and some selected reports. Moreover, it real time integrates with the standard Microsoft Dynamics NAV database while collaborating with Microsoft® Windows® SharePoint® Services 3.0 (WSS 3.0) or Microsoft Office SharePoint Server 2007 (MOSS 2007) to provide you a browser based interface.

Depending on the volume of transactions and the number of concurrent users, you can setup Employee Portal to run with either WSS or MOSS. However with MOSS, you would get additional support for making further developments.

Employee Portal can also be identified as a Web Portal for Sales Persons who travels all over the country. In such instances, salesperson can logging to NAV and start creating Sales Orders or Sales Quotes as required by them.

Let’s look at some typical screens available in the default Web pages.

Item List /Product List Page
This page can be configured as a combination of List Web Part and Card Web Part page in such a way that Item List is available in the top side of the page. Once user clicks on the ‘Card’ hyperlink on the list then user is directed to the Item Card of the particular Item in the bottom of the page.


What is Employee Portal

There are number of options available in the Item Card where user can modify or even delete the existing items from the system. It also gives some reporting options such as ‘Quantity Explosion of BOM’, ‘Rolled-up Cost Shares’ and ‘Detailed Calculation’



Sales Order Page
As in Item Page, existing Sales Orders can be displayed in the top of the page. As and when user clicks on the particular Sales Order Number then user can be directed to Sales Order Card screen where both the header and the line information are displayed.



However there is no static principle in designing the web pages in Navision Employee Portal. With the given Web Parts, you always have the flexibility to for designing each web page according to the user requirement. For example, in the sales Order screen, instead of showing all existing sales orders in the system, you can display all existing customers in the system. From the Customer List you can filter respective sales orders list belongs to particular customer and then you display the card view of a selected sales order.

Since the installation and setup process takes a very sensitive path, it is recommended that you must strictly follow the standard Microsoft Installation and Configuration Guidelines without any change.

To be continued…

Upgrade from NAV 5 to NAV 2009 SP1 – A Quick Guide

Regardless of the version from which you are trying to do the upgrade, the whole process can be divided into two main phases as Object Upgrade and the Data Upgrade. Let’s first look at the Object Upgrade.

In Object Upgrade, you have to identify all the customizations done in the current live version of the customer database and implement the same in a new 2009 SP1 database. Please remember that there are no short-cuts for this process. This is entirely a manual process, but you can make use of the existing tools such as Developer Toolkit. Using the Developer Toolkit you can compare/merge the original version 5 db and the current customer database wherein you can identify the differences between the two databases and implement the modifications in a new 2009 SP1 fresh database. Once you complete this process, you are through with the phase no 1. Remember that this is the most time consuming phase in an upgrade project. If you make any mistakes then you have to suffer a lot in the subsequent processors.

Let’s look at the phase number two which is the Data upgrade. In this case, I am giving you the main steps for continuing with the data upgrade.

1. Prepare for the data conversion.
a. Make a copy of the database in which you will perform the conversion.
b. Verify that both your partner development license file and customer license file have been upgraded to Microsoft Dynamics NAV 2009 SP1.
c. Identify a User ID and password of a super user in the system or create a new super user in the system that you can use for the upgrade process. Log in as the super user when you perform the upgrade.
d. Make a backup of the entire database before you start.
e. Test the database for everything except table/field relationships.
f. Test the database for table/field relationships.
g. Compile all objects and resolve what to do with those objects that do not compile.
h. Uninstall Microsoft Dynamics NAV 5.0 from the developer computer.
i. Install Microsoft Dynamics NAV 2009 SP1 on the developer computer, and then start the Classic client.

2. Convert the database to Microsoft Dynamics NAV 2009 SP1.
a. Create a new database in Microsoft Dynamics NAV 2009 SP1 and restore the backup of the customer’s existing database into the new database.
b. You can also open a copy of the customer’s existing database with the Classic client in Microsoft Dynamics NAV 2009 SP1 and convert the database.

3. Delete all objects except tables.
Delete all forms, reports, dataports, XMLports, codeunits, and MenuSuites, from the database. Do not delete the tables.

4. Import the new customized objects that you created under the Object Upgrade Phase.
In this case, you are supposed to replace all objects using the Import Worksheet window. Once all the conflict objects are found, you can replace all objects by clicking the OK button.

5. Compile all objects in the new database.


6. Upgrade data common to all companies.
Upgrade Security Roles and Permissions
If you are upgrading Microsoft Dynamics NAV with Microsoft SQL Server®, then you must synchronize the security system. In the Classic client, on the Tools menu, point to Security, and then click Synchronize All Logins.

7. for each company, initialize the company in the upgraded database.
You can do this by running the codeunit 2, Company-Initialize.
Close the company and open it again.
Open form 531, Setup Checklist, to update the checklist for the Microsoft Dynamics NAV 2009 SP1 data structure.


8. Install the new clients.
Make a backup of the new upgraded database.
Remove all previous versions of Microsoft Dynamics NAV from the client computers. Install Microsoft Dynamics NAV 2009 SP1 on all client computers. Also install the other tiers in the Microsoft Dynamics NAV architecture.

9. This is the end of the upgrade process from NAV version 5 to the 2009 Classic Client, but before going into Live, TEST… TEST… TEST…

To be continued...