Advantages and Disadvantages of the architectures

1-teir Architecture
Advantages
Easy to implement and optimize performance.

Disadvantages
Do not support remote/
distributed access for data
resources.
Do not have compatibility or Context switching
The cost of deployment is less.eg-development and
issues.
management cost.
The cost of deployment is less.eg-development and Monolithic manner of the code causes higher
management cost.
maintenance.
The cost of the central mainframe is high.
2-tier Architecture
Advantages
Applications can be easily developed due to
simplicity. (www.unmedu.com)

Maximum user satisfaction is gained with

accurate and fast prototyping of applications
through robust tools. (www.unmedu.com)

Since this contains static business rules its more

applicable for homogenous environments.
(www.unmedu.com)
Database server and business logic is physically
close, which offers higher performance.
(www.unmedu.com)

Disadvantages
Heterogeneous environments/Business environments
with rapidly changing rules and regulations are not
suitable since the database server has to handle the
business logic which slows down database performance.
(www.unmedu.com)
Since client beholds most of the application logic,
problems arise in controlling the software version and redistributing of new versions. (www.unmedu.com)

Security wise this is complicated as users need to have

separate login information for every SQL server.
(www.unmedu.com)
Client tools and SQL middleware implemented in 2-tier
environment is proprietary which remains cautious on
long term feasibility. (www.unmedu.com)
Scalability: The 2-tier model lacks scalability as it
supports only a limited number of users. When
simultaneous client requests increases application
performance degrades rapidly due to the fact that clients
necessitate separate connections and CPU memory to
proceed. (Thota 2010)
Minimal Logic Sharing: Since the application logic is
coupled with the client its difficult to re-use logic
dispersed among applications and tools. (Thota 2010)
Dispersion of Applications: Any change in an application
should reflect all clients. If higher number of users exists
in the system, it entails substantial administrative
overhead. (Thota 2010)
Change of Database Structure: Most applications used for
interaction is dependent on the database structure
creating an issue when re-designing, as they are intimate
with the prevailing structure. (Thota 2010)

3-tier Architecture
Advantages
Disadvantages
Improved Scalability: Due to the distributed
Complexity of Communication: Usually more
deployment of application servers, scalability of effort should be enforced when creating 3-tier
the system is enhanced since a separate
applications as the communication points are
connection from each client is not required
increased (client to middle tier to server, instead of
whereas connections from few application servers directly client to server) and the performance
are sufficient. Moreover TP monitors or ORBs is increased by tools like Visual Basic, PowerBuilder,
used for load balancing and in synchronizing
Delphi will be reduced. (Sarma 2010)
severs.(Sarma 2010)
Enhanced Re-usage: A similar logic can be
Fewer Tools: Additional effort is required due to
sustained in many clients or applications. In
increase of performance whereas the 2-tier model
appliance of object standards like COM/DCOM or can handle the particular function using an
CORBA, the language in the business-logic tier
automated tool. It also has productive tools like
can be made transparent. .(Sarma 2010)
reporting tools. Sarma 2010)
Improved Data Integrity: Data corruption through
client applications can be eliminated as the data
passed in the middle tier for database updations
ensures its validity. .(Woodger Computing Inc
2010)
Enhanced Security: Through the implementation
of several layers, enhances the data security on a
service-by-service basis. As clients do not interact
with the database directly, it provides less risk and
confliction with unauthorized data. The
placement of the business logic on a centralized
server makes the data more secure. .(Woodger
Computing Inc 2010)
Redundant Sever Availability: mission-critical
applications seek the use of superfluous
application servers and database servers as its
possible to create an application which will
recover the system from network or server
failures, with redundant servers. .(Woodger
Computing Inc 2010)
Hidden Database Structure: The actual structure
of the database often remains hidden from
requesters enabling any change of the database to
be transparent. Thus a process in the middle tier
which exchanges data with other applications can
sustain its current interface while a modification
of the underlying database structure.(Woodger
Computing Inc 2010)

n-tier Architecture
Advantages

Disadvantages

n tier architecture includes all advantages of the 3Due to the componentization of the tiers, the complex
teir model since its an expansion of the 3-teir
structure is difficult to implement or maintain.
methodology. Mainly the performance is increased
(Kambalyal 2010)
due to off-load from the database tier and the client
tier, enabling it to suit medium to high volume

industries (Kambalyal 2010).

Data Migration Steps From NAV 2013 to NAV 2013 R2 in brief

PREPARATION
1. Update the Application Code.

2. Export all the objects

3. Prepare for the data conversion.
4. Run a database test to determine the state of the customers

database.
5. Run the Adjust Cost-Item Entries. Run the job for each company
in the database.
6. run the Post Inventory Cost to G/L batch job. Run the job for
each company in the database.
7. Make a copy of the Microsoft Dynamics NAV 2013 database, or
create a backup.
8. In the Microsoft Dynamics NAV 2013 development environment, on the File
menu, point to Database, and then choose Alter.
In the Alter Database window, on the Integration tab, enter a check mark
in the Save license in database field.
9. Next, you will convert the Microsoft Dynamics NAV 2013 database
so that it can be used in Microsoft Dynamics NAV 2013 R2.
10. To convert the database
11. Tools menu, choose License Information.
UPGRADE STEP 1
UPGRADE STEP 2

Data Migration Steps From NAV 2013 to NAV 2013 R2.

Hi All,
This was asked to me from so many readers about the steps that we need to take for data
migration from NAV 2013 to NAV 2013 R2.

Yes those steps are listed in MSDN but at the same time they are so much confusing as they

have merged the steps of both Data Migration as listed below1. NAV 2009 / SP1 / R2 TO NAV 2013 R2.
2. NAV 2013 TO NAV 2013 R2.
So for those who are looking for steps that need to be executed to upgrade data from NAV
2013 to NAV 2013 R2, do read the post.

PREPARATION
1. Update the Application Code.
Any customization in the customers old database must be implemented in the new database.
2. Export all the objects in the new customized Microsoft Dynamics NAV 2013 R2 database
to an object file: objects. Fob.
3. Prepare for the data conversion.
a. Make sure that you are the only user connected to the database.
b. Back up the database and save the backup file in a safe place.
c. Make a copy of the customers database in SQL Server Management Studio. You will
upgrade the copy and keep the original.
d. Verify that both your partner development license file and customer license file have been
updated to Microsoft Dynamics NAV 2013 R2.
e. Identify a User ID and password for a superuser in the system or create a new superuser
that you can use for the upgrade process. Log in as the superuser when you perform the
upgrade.
f. Verify that you have the dbcreator and securityadmin Server Roles for the Microsoft
Dynamics NAV SQL Server instance, using SQL Server Management Studio. To manage
companies, objects, and licenses within a Microsoft Dynamics NAV database you must also
have the db_owner database permission.
g. Disable integration properties for the database.
h. Open the database in the Microsoft Dynamics NAV 2013 Classic with Developer
Environment.
4. Run a database test to determine the state of the customers database.
Note: The database test can require a significant amount of time, depending on the size
of the database.
5. Run the Adjust Cost-Item Entries batch job to ensure that the inventory cost data in

the customers database is up to date. Run the job for each company in the database.
6. If your organization posts inventory costs to the Microsoft Dynamics NAV general ledger,
run the Post Inventory Cost to G/L batch job. Run the job for each company in the
database.
7. Make a copy of the Microsoft Dynamics NAV 2013 database, or create a backup.
Open the Microsoft Dynamics NAV 2013 development environment, and connect to the
Microsoft Dynamics NAV 2013 database that you want to convert.
In the Microsoft Dynamics NAV 2013 development environment, on the Tools menu, choose
Build Server Application Objects.
In the dialog box that appears, choose the Yes button. If any errors occur, they are shown in
the Error List window. Make sure that you address all compilation errors before you continue.
8. In the Microsoft Dynamics NAV 2013 development environment, on the File menu, point
to Database, and then choose Alter.
In the Alter Database window, on the Integration tab, enter a check mark in the Save license
in database field.
9. Next, you will convert the Microsoft Dynamics NAV 2013 database so that it can be
used in Microsoft Dynamics NAV 2013 R2.
Before you start the following procedure, you can choose to uninstall Microsoft Dynamics
NAV 2013. However, you can install Microsoft Dynamics NAV 2013 and Microsoft
Dynamics NAV 2013 R2 in the same environment.
When you uninstall Microsoft Dynamics NAV 2013, the database is still attached to the
instance of SQL Server, which you can verify using SQL Server Management Studio.
10. To convert the database
Run the installation program for Microsoft Dynamics NAV 2013 R2. Choose to install the
Developer option.
Open the Microsoft Dynamics NAV 2013 R2 development environment, and then connect to
the Microsoft Dynamics NAV 2013 database that you prepared in the previous section.
In the dialog box that appears, read the instructions carefully because this action cannot be
reversed.
When you are ready, choose the OK button, and then confirm that you want to convert the
database.
Microsoft Dynamics NAV will now convert the database. This includes an upgrade of system
tables, and an upgrade of all reports to support Report Viewer 2010.
When you are notified that the conversion was successful, choose the OK button.

11. On the Tools menu, choose License Information. Choose the Upload button to upload a
valid Microsoft Dynamics NAV 2013 R2 license to SQL Server.
In the development environment, on the Tools menu, choose Build Server Application
Objects, and then, in the dialog box, choose the Yes button.

UPGRADE STEP 1
1. In the following step, you will be connecting a Microsoft Dynamics NAV Server instance
to the database.
2. Make sure that the service account that the Microsoft Dynamics NAV Server instance uses
has the db_owner role for the database. Connect the Microsoft Dynamics NAV Server
instance to the database, and then start the service instance.
3. Open the Object Designer, and then import Upgrade700701.1.fob. If the .fob file contains
objects with conflicting versions that are already in the database, the Import Worksheet
window opens. Choose Replace All.
4. Then, from the Object Designer, run Page 104001, Upgrade - Old Version. Choose the
Transfer Data button. Repeat this action for each company in the database.

UPGRADE STEP 2
1. In the Microsoft Dynamics NAV 2013 R2 development environment:
On the Tools menu, open Options, and then, make sure that the Prevent data loss from table
changes field is set to Yes.
You must also make sure that the Server Name, Server Instance, and Server Port fields are
filled in.This ensures that the Microsoft Dynamics NAV Server instance that is connected to
the database will verify that no operation will cause loss of data in the development
environment.
a. Import all customized objects in .fob format into the upgraded database. If the .fob file
contains objects with conflicting versions that are already in the database, the Import
Worksheet window opens. Choose Replace All.
b. Make sure all objects are compiled.
Import Upgrade Step 2 objects from the Upgrade700701.2.fob file. If the .fob file contains
objects with conflicting versions that are already in the database, the Import Worksheet
window opens. Choose Replace All.
2. Open the Microsoft Dynamics NAV 2013 R2 Windows client to verify that you are
connected to the Microsoft Dynamics NAV Server instance that is connected to the database
being upgraded.
Next, you will run Upgrade Step 2 in each company in the upgraded database.

You can get a list of all existing companies in the database by running the Get-NAVCompany
cmdlet and passing as an argument the Microsoft Dynamics NAV Server instance which is
connected to the upgraded database.
You will run objects directly from the development environment, so you must specify the
company that the objects must run in in the Options window.
3. In the Microsoft Dynamics NAV 2013 R2 development environment:
a. On the Tools menu, open Options, and then, in the Company field, specify the name of the
first company.
b. In the Object Designer, find page 104002 Upgrade - New Version, and then choose Run.
c. In the Upgrade - New Version window, choose Test Database Connection to make sure
that the C/AL code that is triggered by the actions on the page has access to the database.
If your database is on a named SQL Server instance, you must specify the full name in the
SQL Server Name field.
d. Choose Transfer Data.
If the process is successful, and you don't have to revisit the upgrade logs, you can clean the
content of the Upgrade Time Log table.
e. On the Navigate tab, choose Time Log, and then, in the Upgrade Time Log page, delete all
records.
Close the Upgrade - New Version window, and then close the Microsoft Dynamics NAV
Windows client.
4. Repeat step 3 for each remaining company in the database.

POST UPGRADE STEPS

1. When you have successfully transferred data in the last company, you must upgrade data
that is common to all companies in the database, such as permissions, permission sets, web
services, profiles and control add-ins.
2. Upgrade data common to all companies such as permissions, permission sets, web
services, profiles and control add-ins.
If the customer has changed the Read/Write/Modify/Delete/Execute settings for any of the
standard permissions, or customized default permission sets in any way, you must merge
these changes into the default permissions sets and permissions that are included in Microsoft
Dynamics NAV 2013 R2.
You can use XMLport 104001 Import/Export Roles and XMLport 104002 Import/Export
Permissions to export the new default roles and permissions from the CRONUS International
Ltd. demonstration database in Microsoft Dynamics NAV 2013 R2.

You can add control add-ins in the Control Add-ins window in the Microsoft Dynamics NAV
Windows client. For more information, see How to: Register a Windows Client Control Addin. For example, the following client control add-ins are available from the Microsoft
Dynamics NAV 2013 R2 product media:
a. Microsoft.Dynamics.Nav.Client.BusinessChart
b. Microsoft.Dynamics.Nav.Client.PageReady
c. Microsoft.Dynamics.Nav.Client.PingPong
d. Microsoft.Dynamics.Nav.Client.VideoPlayer
3. Delete the upgrade toolkit objects.
a. In the Upgrade - New Version window, choose Mark/Delete Upgrade Toolkit.
This deletes all upgrade toolkit objects, except tables. Tables need to be deleted manually
after data deletion.
4. In the Microsoft Dynamics NAV development environment, delete the upgrade tables by
setting a field filter for objects where the Version List contains Upgrade Toolkit Table marked for deletion.
Hope you find the information useful.