Microsoft Dynamics NAV 5.

00
TM

Installation & System Management: C/SIDE Database Server for Microsoft Dynamics NAV
TM

Installation & System Management: Database Server for Microsoft Dynamics NAV
TM

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2007 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Application Server for Microsoft Dynamics NAV, AssistButton, C/AL, C/FRONT, C/SIDE, FlowField, FlowFilter, C/SIDE Database Server for Microsoft Dynamics NAV, Microsoft Business SolutionsNavision, Microsoft Dynamics NAV, Microsoft Dynamics NAV Debugger, Navision, NAV ODBC, SIFT, SIFTWARE, SQL Server, SumIndex, SumIndexField are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.

PREFACE

This book is a manual for Microsoft Dynamics NAV. This program is designed to run on the C/SIDE Database Server for Microsoft Dynamics NAV This book is part of a comprehensive set of documentation and Help materials for the Dynamics NAV enterprise business solution. The manual describes how to install and maintain Dynamics NAV. However, we recommend that the installation and customization process is carried out with the assistance of a Microsoft Certified Business Solutions Partner representative. You should also be familiar with the symbols and typographical conventions used in the Dynamics NAV manuals. In the list below, you can see how various elements of the program are distinguished by special typefaces and symbols:
Appearance Ctrl Element Keys on the keyboard. They are written in small capitals. Menu items and buttons in windows. They always start with a capital letter, and the access key is underlined. Field names. They appear in medium bold and start with a capital letter. Names of windows, boxes and tabs. They appear in medium bold italics and start with a capital letter. Text that you must enter, for example: "...enter Yes in this field." It is written in italics. File names. They are written with the Courier font and lowercase letters.

Design
Address Department Hansen

fin.flf

TABLE OF CONTENTS

Chapter 1

Installing Dynamics NAV. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Choosing the Installation Type and Equipment . . . . . . . . . . . . . . . . . . . . . . . . . 2 Installing, Maintaining and Removing Single-Users and Clients . . . . . . . . . . . 4 Installing C/SIDE Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Importing a Database into C/SIDE Database Server . . . . . . . . . . . . . . . . . . . . 21 Running More than One Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Installing Outlook Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Deployment in an SMS Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Service Packs and Security Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Chapter 2 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Microsoft Dynamics NAV Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Single-User and Client Setup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 C/SIDE Database Server for Microsoft Dynamics NAV Setup Properties . . . 45 Setting the Program Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Chapter 3 Working with Databases . . . . . . . . . . . . . . . . . . . . . . . . . . .57

The Standard Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Creating and Maintaining Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Testing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Deleting the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Database Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Expanding a Working Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Advanced Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Setting up Outlook Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Standby and Hibernation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 License Agreement Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Chapter 4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Authentication in Microsoft Dynamics NAV . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Active Directory and Microsoft Dynamics NAV . . . . . . . . . . . . . . . . . . . . . . . 112 Security within Microsoft Dynamics NAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Setting Up Logins, Passwords and Permissions . . . . . . . . . . . . . . . . . . . . . . . 114 Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 User Time Limits and the Time Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Selecting a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Chapter 5 Making Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Why, When and How to Make Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Table of Contents

Using the Microsoft Dynamics NAV Backup Function. . . . . . . . . . . . . . . . . . 132 Testing before Using Other Backup Methods. . . . . . . . . . . . . . . . . . . . . . . . . 135 Restoring Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Advanced Backup and Restore Information . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Server Based Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Chapter 6 Advanced Performance Issues . . . . . . . . . . . . . . . . . . . . .147

Checklist for Optimizing Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Selecting Hardware, Operating System and Protocols . . . . . . . . . . . . . . . . . 149 Detecting Bottlenecks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Appendix A Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Appendix B Network Communications . . . . . . . . . . . . . . . . . . . . . . .165

Setting Up Network Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Testing Network Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Chapter 1 Installing Dynamics NAV

Before installing Microsoft Dynamics NAV, you should give some consideration to the kind of installation that you want and the equipment that it requires. When you have decided which type of installation you want and you understand the hardware and communication requirements, you can install the program. The chapter contains the following sections: Choosing the Installation Type and Equipment Installing, Maintaining and Removing Single-Users and Clients Installing C/SIDE Database Server License Files Importing a Database into C/SIDE Database Server Running More than One Server Installing Outlook Integration Deployment in an SMS Network Service Packs and Security Updates

Chapter 1. Installing Dynamics NAV

1.1 Choosing the Installation Type and Equipment

Before installing Microsoft Dynamics NAV, you should carefully consider the needs of your organization as this will greatly influence the type of installation you will require and the hardware that this will involve.

Single-User and Multiuser Installations Dynamics NAV can be used in single-user or multiuser installations.
Single-User

In single-user installations, all the work is done on one computer and all the information (the database) is stored on this computer. Even if you purchase several single-user installations and run each on its own computer, the entire installation is still called "single-user" because the information is stored on each individual computer and not in one centrally located database. In a multiuser installation, many users share common information that is stored in one or more databases on a server. The computers that work with the data are called clients, and the way the server and the computers work together is called a client/server installation.

Multiuser

What You Should Know Before Installing the Program Regardless of whether you have chosen to work in a single-user or multiuser environment, you start by purchasing the same package. The program is installed from the same DVD and with the same installation wizard for both single-users and clients. For a multiuser installation, the DVD contains a C/SIDE Database Server for Microsoft Dynamics NAV package that is installed only on the server computer. However, the demonstration database that comes with a single-user installation is not included in the server package. You need some of the data in the demonstration database (and you need a client or single-user to modify a database), so you must always install a single-user somewhere in the network in a multiuser installation. The simplest way to do this is to install a single-user on the same computer as the server. You can read about this on page 21. The single-user can later be converted to a client by connecting it to the servers database. Once the program has been installed, you must customize it for your particular situation. Not all installations need the same size database. For example, a database server, which serves many users, probably needs a larger database than a single-user installation. With Dynamics NAV, you do not need to plan for the distant future when you purchase your installation or set it up. You can change or expand the installation whenever you like. To switch from a single-user to a multiuser installation, you purchase a server package and the number of session licenses that you need. You can place the database that you already have on a server so that several people can work with it. If, after a while, you need a larger database, you can expand the existing one.

1.1 Choosing the Installation Type and Equipment

Choosing Equipment Dynamics NAV does not require particularly sophisticated equipment, but as with all programs, the better your equipment, the better the results. You get the best solution with the optimal equipment and with the program settings optimized for that equipment. This section contains a brief description of the equipment we recommend for your Dynamics NAV installation. For more detailed information on the best choice of equipment, see the chapter called "Advanced Performance Issues" on page 147. You cannot specify the optimal settings until after you have installed the program. For more information see the chapter called "System Setup" on page 31.

Choice of Computers In a multiuser installation, you can, in principle, use the same type of computer for both the clients and the server, but there is a difference in how much CPU power, memory and disk space each will need. Details about required and recommended hardware and software, including operating system requirements, can be found in the chapter called "Advanced Performance Issues" on page 147. Computers for Clients and Single-User Installations Computers for clients or a single-user installation that run Windows XP, Windows Server 2003 or Microsoft Small Business Server 2003 must comply with the requirements specified by Microsoft. Because the client computers process the data they retrieve, they need a relatively large amount of computing power. If the client computers are too slow, they will take a long time to finish the calculations for a transaction. A slow computer working on a transaction that must update the database can delay all the other clients until it finishes. Computers for Servers Computers for servers that run Windows XP, Windows Server 2003 or Microsoft Small Business Server 2003 must comply with the requirements specified by Microsoft. For more information, see page 149.

Chapter 1. Installing Dynamics NAV

1.2 Installing, Maintaining and Removing Single-Users and Clients

You use the setup program to install, maintain and remove Dynamics NAV. Dynamics NAV can be installed as either single-user installations or as client installations in a network. The Dynamics NAV installation program also installs Commerce Portal automatically and allows you to determine whether or not the Commerce Gateway connectivity components are installed. These components must be installed with the Dynamics NAV client in order for it to connect with a BizTalk server. For more information about installing the E-commerce products see the manual, Installation & System Management: E-Commerce Solutions.

Installing Dynamics NAV Make sure that the operating system on which you will run Dynamics NAV is installed on the computer. If it is not, you will have to install it before you can install Dynamics NAV. If you are installing Dynamics NAV from a network drive, make sure that you are connected to the network server. Dynamics NAV supports the Microsoft AutoPlay feature, so it is not necessary to click the Start button. A menu appears automatically when the DVD is inserted. If you install from a network drive, type the path and name of the installation wizard on the network. Click OK to start the installation wizard. Windows allow you to use the Add/Remove Programs function under Settings, Control Panel.
Earlier version

If you have an earlier version of the program installed on the computer you can upgrade the old installation. For more information about upgrading, see page 11. The installation can be cancelled at any time. If you choose to cancel the installation, a dialog box appears asking you to confirm your decision. If you click No, the installation process will continue. If you click Yes, Microsoft Installer will perform a full rollback and restore the computer to the state it was in before the installation process began. This rollback functionality is a new feature provided by Microsoft Installer.

Cancelling the installation

1.2 Installing, Maintaining and Removing Single-Users and Clients

When the installation program starts the Welcome window appears informing you that you have started the installation wizard for Dynamics NAV.
Customer information

If you do not want to continue with the installation, click Cancel. To continue, click Next, and the Customer Information window appears:

You can enter your name and the name of your organization in this window. You can also specify to whom this installation belongs. The installation will also continue if you leave these fields blank. You can choose between the person who installed it and any user who logs onto this computer. This determines who is allowed to see the installation and therefore able to modify or uninstall it. It does not determine who is able to use the program from this computer.
Selecting the installation type

Click Next and the Setup Type window appears:

This window allows you to specify the type of installation that you want to install. You can choose between three types of installation: Minimum: this installation will only install a minimum of features (the demo database and the backup of the demo database will not be installed). This is the

Chapter 1. Installing Dynamics NAV

recommended installation, if you want to run Dynamics NAV as a client in a network. This installation includes the online Help. A client can be installed as a single-user, that is, with its own database, but this is not normally done because it takes up so much extra space on the client computer. Complete: this installation will install all of the program features except the Commerce Gateway connectivity components. This installation is recommended if you want to run Dynamics NAV in a single-user environment with a local database. Custom: this installation allows you to choose which program features will be installed. This option is only recommended for advanced users.
Note

In a multiuser installation, you must always install one single-user installation in the network because the server package does not include the standard database that is part of the single-user installation. You need some of the data contained in the backup of the standard database when you create a new database. You can always turn a single-user into a client by allowing it to access the database on the server. The simplest thing to do is to install a single-user installation on the same computer as the server package. This procedure is described on page 21.
Customized installation

If you select a complete or a minimum installation, the installation runs automatically. If you select Custom, the following window appears:

In the Custom Setup window, you can decide how and where each feature and subfeature will be installed. This window is divided into three sections: A feature selection area where you can select the individual features and specify how each feature will be installed. A feature description area that displays a short description of each feature as it is selected and an estimate of how much disk space the feature requires. It also gives you an estimate of the amount of space that its subfeatures require. An installation location area that tells you where each feature will be installed. You are able to change the location where the installation will be installed by clicking Browse.

1.2 Installing, Maintaining and Removing Single-Users and Clients

The Custom Setup window lists all the features that you can install: Help the online Help for Dynamics NAV. Demo Database a Dynamics NAV database that contains a demonstration company. This database will be opened automatically the first time you start Dynamics NAV. Backup of Demo Database a Dynamics NAV backup of the demonstration database. You can restore this backup into a new database. Commerce Integration the Commerce Gateway and Commerce Portal components. You must install these components if you want to run either Commerce Gateway or Commerce Portal. If you select this feature, the Microsoft .NET Framework is also installed. The .NET Framework is not removed when you uninstall the Dynamics NAV client. It is given an entry of its own in the Add or Remove Programs window and you can uninstall it from there. Business Notification Manager this feature allows you to automatically send emails to your employees and business partners informing them of business events. Employee Portal allows employees to access critical business information in Dynamics NAV from their company intranet using SharePoint Services. Outlook Integration this feature creates a toolbar in Outlook that allows you to synchronize contacts, appointments and tasks in Outlook with the corresponding items in Dynamics NAV. Dynamics NAV Gantt Server an ActiveX component that allows production managers to plan shop floor production with the help of Gantt charts and update their schedules in Dynamics NAV. All of these features are part of a complete installation.
Note

If you select one of the features, and the estimated space required is given as zero (or less than the original amount of space required), the file will not be copied to the target folder. This occurs because this feature or some of its subfeatures already exist in the target folder. This happens when you have had Dynamics NAV installed before and this feature was not removed when you uninstalled the program. No database files, database backup files or license files are removed when you uninstall Dynamics NAV.

Chapter 1. Installing Dynamics NAV

When you click Change, the following dialog box appears:

This window allows you to locate the folder you want or to create a new folder. You can also get an overview of your disk configuration. In the Custom Setup window, click Space and the following window appears informing you of how much space is available on your hard disk(s):

1.2 Installing, Maintaining and Removing Single-Users and Clients

When you click one of the feature icons in the Custom Setup window, the following drop-down list appears displaying the options that are available for that feature:

The options are: This feature will be installed on your local hard drive. This feature and all of its subfeatures will be installed on your local hard drive. This feature and all of its subfeatures will be installed when it is required. Note that its subfeatures will automatically have the same option. The current feature and all of its subfeatures will not be installed. If you click Help, a window containing a short explanation of the options appears. The most common installations are Stand-alone installation and Client installation. A Stand-alone installation requires you to install the demo database. To do this, click the icon next to Demo Database and select the option in the drop-down menu. The backup of the Demo Database is optional. The online Help is also optional. In a normal client installation you will install the online Help and ignore the other subfeatures.
Ready to install

The Ready to Install the Program window confirms that the installation wizard now has all the information that it requires to carry out the installation process. Click Install to start the installation. The Installation Progress window allows you to monitor the installation process and displays an overall status message that tells you what kind of action is currently being performed. Below that is a more specific description of the particular action that is being carried out, for example, the name of the file that is currently being copied. Finally, there is a progress bar that shows you the status of the installation process. After a few minutes, the Installation Complete window appears. This window informs you that the installation has been completed successfully.

Chapter 1. Installing Dynamics NAV

Maintaining Dynamics NAV Microsoft Installer is also used for changing, repairing and removing Dynamics NAV. 1 Open the Control Panel and select Add/Remove Programs. 2 Select Microsoft Dynamics NAV C/SIDE Client. 3 Click Change and the Installation Wizard opens. The Maintenance Welcome window is similar to the Installation Welcome window and informs the user that they can now change, repair or remove the program. 4 Click Next in the Maintenance Welcome window and the Program Maintenance window appears:

This window allows you to choose between changing, repairing or removing the product installation.
Changing the installation

If you select Change, the Custom Setup window appears. You are now able to select the features and subfeatures that you want to install. You are also able to uninstall all the features and subfeatures. You are not able to change the target path of the installation. You can only change the features that have been installed. If you select Repair, the Installation Wizard updates, installs or reinstalls any missing files, corrupt files, shortcuts, and registry entries. Windows Installer protects any license files, databases and database backups and will therefore not overwrite these files. If you select Remove, a window appears prompting you to confirm that you want to uninstall the product. If you choose to uninstall the product, a progress window similar to the Installation Progress window appears. You are able to cancel the uninstallation at any time. If you do so, Microsoft Installer will perform a full rollback returning the computer to the state it was in before the uninstallation process began. When you remove the program, any databases or database backups that are stored locally will not be deleted. If you store a copy of your license file locally, it will not be

Repairing the installation

Removing the installation

10

1.2 Installing, Maintaining and Removing Single-Users and Clients

deleted but the demonstration license file will be. If you want to remove these files, you will have to do it manually. A progress window appears when you are changing, repairing or removing the program. When the process is finished an Installation Finished window appears informing you whether or not Dynamics NAV has been successfully changed, repaired or removed.
Note

We recommend that you make a backup of any license files, databases and database backups that are stored locally before changing, repairing or removing the client installation. The installation program creates a log file (an ASCII file called delfin.log that lists the changes made by the installation program) in the Dynamics NAV folder. If you need to uninstall Dynamics NAV manually, you can look in the log file to see what must be removed or changed.

Upgrading an Old Installation If you have Navision Financials 2.50 or earlier installed on the computer, the Installation Wizard will ask you to uninstall the old version before you can install Dynamics NAV. If you have Navision Financials 2.60 installed on the computer, the Installation Wizard will ask you if you want to upgrade the old installation or install Dynamics NAV without upgrading the old installation.
Attention

The upgrade program only upgrades the client installation and not the database. To upgrade your database you must use the Upgrade Toolkit that is located on the product DVD. We recommend that you do not upgrade your database without first consulting your local Microsoft Certified Business Solutions Partner. If you have Navision Financials 2.60 installed on the computer, the Installation Upgrade Wizard will open. This wizard will guide you through the process of upgrading your installation. You can choose between three different types of upgrade: Typical: this upgrade will uninstall the old version of the program and install a new version. It will transfer any custom selections that you made in the earlier installation to the new installation. Any databases or database backups that are stored locally will not be deleted. If you store a copy of your license file locally, it will not be deleted. Custom: this upgrade will uninstall the old version of the program and install a new version. Any databases or database backups that are stored locally will not be deleted. If you store a copy of your license file locally, it will not be deleted. When the new version is being installed the installation program will stop at the Custom Setup window. This window allows you to specify which features are installed and

11

Chapter 1. Installing Dynamics NAV

how they are installed. For more information about the Custom Setup window, see page 6. New: this upgrade will install Dynamics NAV. It will not uninstall the old version of the program or make any changes to it. For more information about upgrading to Dynamics NAV, see the Upgrade Toolkit documentation on the product DVD or contact your local Microsoft Certified Business Solutions Partner.

12

1.3 Installing C/SIDE Database Server

1.3 Installing C/SIDE Database Server

The installation wizard for C/SIDE Database Server is like the installation wizard for Dynamics NAV. The installation process starts with a window informing you that the installation wizard has been initiated. After the Welcome window, the Customer Information window appears:

You can enter your name and the name of your organization in this window. You can also specify to whom this installation belongs. You can choose between the person who installed it and any user who logs onto this computer. This determines who is allowed to see the installation and therefore able to uninstall it. It does not determine who is able to log on to the server via the network. Click Next and the Setup Type window appears:

In the Setup Type window, you can choose between a typical installation and a custom installation. A custom installation allows you to specify which features will be installed and how they will be installed.

13

Chapter 1. Installing Dynamics NAV

If you select Custom, the following window appears:

In the Custom Setup window, you can select the features that you want to install. This is a standard Windows Installer dialog box where you can decide whether or not to install HotCopy the server based backup program for Dynamics NAV. For more information about HotCopy, see the section "Server Based Backup" on page 141.
Note

If you decide not to install HotCopy, you will not be able to install it later. If you want to install HotCopy at a later date, you must uninstall the C/SIDE Database Server and reinstall it along with HotCopy. If you want to install C/SIDE Database Server in a different folder, click Browse and the following dialog box appears:

14

1.3 Installing C/SIDE Database Server

If you click Disk Space in the Custom Setup window, the following window will appear informing you of how much space is available on the various drives to which you have access:

Naming the server

Click Next in the Custom Setup window, and the Server Name window appears:

In the Server Name window, you can type in a name for the server. By default it will select the name that the computer has in the network. This name must not contain any spaces. If you select Typical in the Setup Type window, the installation will use the computer name as the server name. If this name already exists, it will insert #1 at the end of the computer name. If this name also exists, it will try with #2, and so on. That means if the computer name is PC0515 and this server name already exists, the installation will try PC0515#1.

15

Chapter 1. Installing Dynamics NAV

Selecting the network protocol

Click Next after you have named the server and the Network Type window appears:

In the Network Type window, you can select which network protocol will be used for communication between the clients and the server (TCPS, TCP/IP or NetBIOS). If you have chosen Typical in the Setup Type window, TCPS will be selected as the network protocol. TCPS is the default setting.
Cache settings

Click Next after you have selected the network protocol and the Cache Settings window appears:

This window allows you to determine the amount of space that will be reserved on the server used for both the Cache and the Commit Cache. You can accept the default settings or adjust them to suit your needs.

16

1.3 Installing C/SIDE Database Server

License file

Click Next after you have specified the cache settings and the License File window appears:

In the License File window, you specify which kind of license file you want to install. You can choose between installing the demo license file or your personal license file. Install demo license is the default value. When you choose the Select personal license option the Browse button and the License file field will be enabled. You are now able to use the Browse button to locate your license file. If you have chosen to install a Typical installation in the Setup Type window, the Install demo license option is automatically selected. For more information about license files, see the section called "License Files" on page 20.
Selecting the database

Click Next after you have selected the license file you want to install, and the Database File window appears:

This window allows you to specify whether you want to select a database now or wait until the first client connects to the server. If you choose to select the database now, the Browse button and the Database File field become enabled and you can use them to locate the database that you want to be opened when Dynamics NAV is started.

17

Chapter 1. Installing Dynamics NAV

Click Next and the installation process will continue. It will display a progress bar that allows you to monitor the installation. The installation program will also inform you when the installation is complete and whether it has been successful or not.

Publishing C/SIDE Database Server in a Network In order for other server and client computers to be able to identify and connect with your C/SIDE Database Server, you must publish it in the network. Before you can publish a C/SIDE Database Server in the network, you must add a definition of a Dynamics NAV service connection point to the Active Directory. C/SIDE Database Server uses this service connection point to publish itself in the network and the clients use this information to locate the server and to find out how to connect to it. Only servers that have been installed as a service can be published in the network. To add a definition of a C/SIDE Database Server to the Active Directory, you must add a Schema Extension to Active Directory. This must only be done once for each forest of domains and domain trees, regardless of how many C/SIDE Database Server are in that forest. When you install C/SIDE Database Server, a file called schemaXt.exe is copied into the folder that contains C/SIDE Database Server. Run this file to add a definition of a Dynamics NAV service connection point to the Active Directory. Starting up a C/SIDE Database Server (running as a service) will publish a service connection point using the definition that has been added to Active Directory.

Maintaining C/SIDE Database Server The Maintenance Setup Type window for C/SIDE Database Server differs from that of Dynamics NAV in that you are not able to modify the server installation. If you need to change the server name, for example, you must uninstall the program first and then install it again and give it the new server name. If you install the server again in the same folder (for example, if you install an update), any existing database files, database backup files and license files will not be overwritten by the new installation. This means that if you want a new database or a new license file to be installed when you reinstall the program, you must delete these two existing files from the Dynamics NAV folder before you start.
Note

We recommend that you make a backup of any license files, databases and database backups that are stored on the server before modifying, repairing or removing the server installation.

Running as a Service If you want to run C/SIDE Database Server as a service or use the installasservice command line parameter when you start the server, you should ensure that the service is running as the NT Authority\Network Service account. The NT Authority\Network Service account only exists on Windows XP and Windows Server 2003. If you are running Windows 2000 Server, you should create an account with least privileges for

18

1.3 Installing C/SIDE Database Server

the service or else the service will be assigned a Local System account. This account should at the most have the same privileges as the normal Users account or be a domain account that is not an administrator either in the domain or on any local computer. To ensure that the service is running as NT Authority\Network Service: 1 On the C/SIDE Database Server computer open the Services window and locate the C/SIDE Database Server service, right-click it and click Properties. 2 In the Properties window, click the Log On tab. 3 In the Log On tab, under Log on as click This Account and enter NT Authority\NetworkService and click OK. You must also give the NT Authority\Network Service account or the user account that the server is running under write access to the database file(s) to ensure that the users can connect to the database. To give the NT Authority\Network Service account read and write access to a database file on Windows XP: 1 In Windows Explorer, navigate to the folder that contains the database file. Select the database file, right-click it and click Properties. 2 In the Properties window, click the Security tab and under the Group and user names field, click Add. 3 In the Select Users, Computers, or Groups window, enter Network Service and click OK. 4 NETWORK SERVICE has been added to the Group and user names field in the Properties window. 5 Select NETWORK SERVICE and in the Permissions field give it Read and Write permission.

19

Chapter 1. Installing Dynamics NAV

1.4 License Files

A single-user installation comes with a demonstration license file, cronus.flf, that allows you to see all the application areas in the demonstration company that is part of the accompanying standard database, database.fdb. To start working with Dynamics NAV, you will need a license file that contains permissions for the desired application areas and functions. You obtain the license file from your Microsoft Certified Business Solutions Partner. You can use your license file to work in the demonstration company as well as your own companies, but your permissions will be limited (even in the demonstration company) to those provided by the license file. On the other hand, your license file does not contain the restrictions of the demonstration license file, which are listed on page 58. Your license file is always named fin.flf, and you will receive a personal copy of it to keep. In a single-user installation, copy the license to your computer. In a multiuser installation, the license will be copied to the server during the installation process and does not need to be copied to the individual clients. The clients automatically work with the same license file as the server to which they are connected. After you have copied your license file to your computer or the server, keep a copy of it in a safe place until you need to use it again.

The Final Adjustments For both single users and clients, you may need to adjust the Dynamics NAV setup to match your computer and the rest of the system. There are a number of system setup tools to help you. They are described in the chapters called "System Setup" and "Advanced Performance Issues."

20

1.5 Importing a Database into C/SIDE Database Server

1.5 Importing a Database into C/SIDE Database Server

In a multiuser installation, in addition to installing one or more clients, you must install the server program and set up a database on the server. It is easier to start by setting up the database. The server program does not come with a database. If you already have a Dynamics NAV database, copy it to the same computer that your server will be installed on. If you do not already have a database, you can use the standard database, database.fdb, or a copy of it. For more information, see the section called "Using the Standard Database" on page 58. You can also create a new database. To do this, you need some of the information in the standard database. A single-user version must therefore be installed somewhere in the network so that you can transfer the database that comes with it to the server. To create a new database before you install the server: 1 Install a Dynamics NAV single-user. Remember to select the Complete Installation option. (See "Installing, Maintaining and Removing Single-Users and Clients" on page 4.) The standard database will be installed as part of the complete installation and comes with a demonstration company. It is not a good idea to leave the demonstration company in your working database (see page 58 for details). If, however, you want to leave it in, skip to step 6. 2 Click File, Company, Open to open the demonstration company. 3 Click File, Company, Delete. 4 Click Yes when you are asked (twice) whether you want to delete CRONUS International Ltd. 5 Close the single-user program. 6 Start the C/SIDE Database Server Setup program.

Starting the Server When installed as a service the C/SIDE Database Server starts automatically every time you start the server operating system.
Note

Remember to make a full backup of the database before deleting it from the hard disk. For more information, see the chapter called "Making Backups" on page 129.

21

Chapter 1. Installing Dynamics NAV

1.6 Running More than One Server

The following sections describe the possibilities for running more than one server with the same database or with different databases. Appendix B gives more detailed information about network communications.

Two or More Servers, Same Database It is possible to run two or more C/SIDE Database Servers with the same database provided that: each server has a different server name. all the servers are run from the same folder. With this configuration you could, for example, have one server running TCPS and another one running NetBIOS on the same database. See "NetType Selecting a Net Type" on page 40 for a description of TCPS and NetBIOS.

Two or More Servers, Different Databases It is possible to run two or more C/SIDE Database Servers with different databases provided that: each server has a different server name. the server programs are located in different folders. This means that to use two databases on the same computer, you must install the server program twice, in two different folders. The following examples describe how to configure your installation for running two servers with different databases, using TCPS and using NetBIOS. Two Servers on the Same Computer, Both Using TCPS To run two servers, both running TCPS, on the same computer, they must both be run as a service. Follow the procedure outlined below to configure the computer correctly. Install the C/SIDE Database Server in two different folders as follows:
The servers

1 Install the first server as described on page 13. 2 Make a copy of the folder where C/SIDE Database Server was just installed and rename it. You must do this because you cannot install two versions of C/SIDE Database Server on the same computer. 3 Select a unique server name for the second server. Once the two servers have been installed, proceed as follows: 1 Locate the SERVICES file. On Windows Server 2003 the services file is stored in:
C:Windows\System32\drivers\etc\

22

1.6 Running More than One Server

2 Edit the SERVICES file to include statements such as: ... ... servername1 servername2 ... ... The server names shown should be replaced with your actual server names. 3 Start the first server in the first folder, using the following parameters:
server servername=servername1, nettype=tcps, cache=xxx, commitcache=yes, database=AAAA, installasservice

2407/tcps 2408/tcps

4 Start the second server in the second folder, using the following parameters:
server servername=servername2, nettype=tcps, cache=xxx, commitcache=yes, database=BBBB, installasservice

In these examples, xxx represents the cache size, and AAAA and BBBB are the names of the databases. Remember to write out the full path for each database file. 5 Edit the SERVICES file on the client as follows: ... ... servername1 servername2 ... ... 6 Start the first client, using the following parameters:
fin servername=servername1, nettype=tcps

2407/tcps 2408/tcps

7 Start the second client by using the following parameters:

fin servername=servername2, nettype=tcps

You must also edit the HOST file on the clients. It is located in the same folder as the SERVICES file. Follow the same procedure when editing the HOST file. The system should now be up and running. For more information about running C/SIDE Database Server as a service, see the section "Install As Service" on page 48 and the Microsoft Dynamics NAV Security Hardening Guide manual that comes on the product DVD.

23

Chapter 1. Installing Dynamics NAV

Note

We do not recommend running two servers on the same computer when they are using NetBIOS as the NetType.

24

1.7 Installing Outlook Integration

1.7 Installing Outlook Integration

Outlook Integration allows you to synchronize items in Microsoft Outlook with records in Microsoft Dynamics NAV. In Dynamics NAV, synchronization applies to contacts and to-dos of different types such as salespeople or purchasers. These records can be synchronized with items in Outlook such as contacts, appointments or tasks. Outlook Integration is flexible and highly configurable. For example, it is possible to create your own synchronization schedule and choose to define other items that you want to synchronize. This makes it easy to optimize and extend the synchronization process to suit business requirements and it means that records in both Outlook and Dynamics NAV can be kept up-to-date simultaneously.
Examples of synchronization Example 1

Dynamics NAV contacts/salespeople synchronized with Outlook contacts: Synchronization of these entities with Outlook contacts is advantageous as it makes it possible to continue interaction even without being connected to the Dynamics NAV client. For example, a salesperson enters a new contact into Outlook. After running synchronization this entry is added to the contacts/salesperson list in Dynamics NAV without the need to connect to the Dynamics NAV client directly.
Example 2

Dynamics NAV to-dos synchronized with Outlook appointments and tasks: Salespeople and teams should be able to retrieve tasks and meetings from Dynamics NAV, import them into Outlook and then act upon them. Once they have completed a task in Outlook, the next time they go online all the relevant records in Dynamics NAV will be synchronized without the need to manually update data in both places.
Key features

Customization options: Synchronization settings and options can be configured via the synchronization toolbar. The Synchronization Progress window: This displays a summary of items synchronized, created, modified or deleted instead of sending E-mail notifications of changes made. Control over the synchronization process: The user has more control over options on both the Outlook and Dynamics NAV sides of the synchronization process. Also synchronization can be set periodically, say every 60 minutes or on a users request, not just when an item has been changed. Filters: Filters can be applied to items that you wish to be synchronized. This means that a more sophisticated level of synchronization is possible. Resolution of technical problems: If a technical problem occurs during synchronization, for example, a synchronization conflict occurs, it can be resolved quickly and effectively. Depending on the options chosen during the Synchronization add-in setup, a conflict can be resolved automatically or if the user requires greater control, manually. Improved field mapping: For an additional field to be synchronized it must be mapped directly to another field in the mapping schema. In previous versions of Dynamics NAV there were a number of many-to-one and one-to-many field mapping relationships.

25

Chapter 1. Installing Dynamics NAV

Note

To read more about new functionality and other changes in Outlook Integration see Upgrading from Navision 4.0 to Microsoft Dynamics NAV 5.0 on page 104

Installing the Outlook Add-in To enable synchronization an Outlook add-in must be installed on your Outlook client. The Outlook add-in and dll files are not included as part of the standard Dynamics NAV installation. They must be located on the product DVD and installed separately.
Installation prerequisites

Microsoft Outlook Client .Net Framework 2.0 Application Server for Microsoft Dynamics NAV (This can either be installed on a separate server or on your own computer) Select the components on the DVD that you wish to install and an installation wizard will guide you through the rest of the installation process. The following diagram shows the Outlook Integration architecture after installation of the add-in:

Installation scenarios 1 Installation of the C/SIDE client for Dynamics NAV together with the Outlook add-in.

(typical scenario.)

2 Installation of the add-in on its own. (e.g. for a salesperson) who may not have access to a Dynamics NAV Client but who may wish to synchronize his or her contacts by connecting to a Dynamics NAV server via Outlook. After installation is complete a Dynamics NAV synchronization add-in toolbar appears in Outlook. This can be used to set up, configure and remove the add-in.

26

1.8 Deployment in an SMS Network

1.8 Deployment in an SMS Network

If you are running a Windows network with SMS (System Management Server) installed, Microsoft Dynamics NAV can be distributed, installed and uninstalled within an SMS network. The computers in an SMS network are arranged in a tree structure. From the computer at the top of the tree, the system administrator can install software on other computers further down the tree to perform an organization wide installation. The administrator can also send a request to uninstall a program on a remote machine. This is very convenient in large networks where the various computers are located at different sites.
Advantages of using SMS

Reduced costs and shorter deployment time. The installation can be delivered during off peak hours, reducing the effect on users. Upgrades can be co-ordinated across multiple sites. Slow links between sites can be better managed. SMS 2.0 can compress package sizes, which minimizes bandwidth usage. It also allows administrators to throttle and schedule bandwidth use to reduce concurrent network usage. Dynamics NAV can be deployed to multiple clients simultaneously. It can be deployed to clients using different operating systems. Forced installation of Dynamics NAV for users on client computers is possible. SMS 2.0 comes with status reporting and troubleshooting tools. Refer to the Microsoft SMS website for further advantages of using SMS.

Package Definition Files

Microsoft Dynamics NAV comes with a number of different package definition files. A Package Definition File (.pdf) is a template that contains the SMS components necessary to create and distribute software to multiple users on a network. It specifies the setup program, and its command line parameters, the installation options and the execution command lines for each component required to install the software. The Dynamics NAV Package Definition File is supplied with the Dynamics NAV Installation program and should not be modified. It is located in the SMS subfolder on the Installation DVD.
Package Definition Files (PDF) supported: Microsoft Dynamics NAV Employee Portal Front End 5.00.pdf Microsoft Dynamics NAV C/SIDE Client 5.00.pdf Microsoft Dynamics NAV SDK 5.00.pdf Microsoft Dynamics NAV ODBC 5.00.pdf Microsoft Dynamics NAV Commerce Gateway Broker 5.00.pdf Microsoft Dynamics NAV Commerce Gateway Request Server 5.00.pdf

27

Chapter 1. Installing Dynamics NAV

Further Information For more detailed guidance on using SMS refer to System Management Server Version 2.0 on the Microsoft SMS website. The latest guide can be found by going to Technical Resources, Product Documentation.

28

1.9 Service Packs and Security Updates

1.9 Service Packs and Security Updates

The installation is not complete until you have installed the latest service packs and applied the latest security updates to your system. Keeping your system up-to-date by installing the latest service packs is one of most important things you can do in managing the security of your system. You should visit Microsoft Update and install all the relevant updates on every computer in your Dynamics NAV installation. We also recommend that you enable Automatic Updates on each computer so that they can receive security & critical updates automatically.

29

Chapter 1. Installing Dynamics NAV

30

Chapter 2 System Setup

Microsoft Dynamics NAV comes with a standard setup that enables it to be used immediately. However, different installations may require small variations in the setup. You can easily implement these changes yourself. Once you have changed the settings, the program uses them until they are changed again. There is no simple formula that specifies the setup selections that different users need or the order in which they must be defined. The chapter contains the following sections: Microsoft Dynamics NAV Installations Single-User and Client Setup Properties C/SIDE Database Server for Microsoft Dynamics NAV Setup Properties Setting the Program Properties

Chapter 2. System Setup

2.1 Microsoft Dynamics NAV Installations

Microsoft Dynamics NAV can be installed in several different configurations. The various program properties can then be used to determine the way the different types of installations perform. However, the program properties do not all apply to the different configurations and their effect can vary. Dynamics NAV can be configured to run as multiuser installations or as single-user installations.
Multiuser

In a multiuser installation, many users use common information that is stored in one or more databases on a server. The computers that work with the data are called clients, and the way the server and the computers work together is called client/server. There are, however, two different types of multiuser installation: A classic client/server installation, where the server is installed on one computer and the clients are installed on other computers in the network. A multiuser installation, where both the server and the client programs are installed on a file server and the clients are run remotely from other computers in the network.

Single-User

In single-user installations, all the work is done on one computer and all the information (the database) is stored on this computer. Even if you purchase several single-user installations and run each on its own computer, the entire installation is still called single-user because the information is stored on each individual computer and not in one centrally located database. Single-user installations are the easiest to set up and maintain.

The Setup File Dynamics NAV is able to remember the various settings that are used by different clients and single-users. This includes the server the client was connected to and the database and company the client was working with. It does this by saving these settings in a setup file. This setup file is called a zup file in Dynamics NAV. The different clients can all share the same zup file and thereby use the same settings, or they can all have individual zup files and thereby use their own customized settings. If the network administrator has decided to implement roaming users, you will not have to utilize setup IDs. With roaming users, Windows will save the personal settings of each individual user on the server, including their zup file. This file will be called fin.zup and will contain Dynamics NAV information that is specific to that user. If the network administrator has decided to implement local users, the zup file of each user will be saved on their local hard disk. Several users can also use the same computer and have their own zup files stored on the hard disk as long as they have individual Windows accounts. The zup file of each individual user is stored in C:\Documents and Settings\User Name\Application Data. All of these zup files will be called fin.zup unless you create individual setup IDs. You only have to implement setup IDs if the users are using the same Windows account.

32

2.1 Microsoft Dynamics NAV Installations

If you do not enter a setup ID, the program will use the setup file called fin.zup when you start the program. You will be prompted to save any modifications that you have made during the session when you close the program. These changes will be saved as fin.zup and will be recreated the next time the program is started. When several users are using the same zup file they will each be prompted to save the changes they have made in the fin.zup file when they close the program. The fin.zup file that was saved by the previous user who quit the program will be replaced. If you delete the zup file on a client or single-user installation Dynamics NAV will recreate the default zup file the next time the program is started. You can also make a standard setup created for a particular type of user available to other users with similar needs. To do this, copy the appropriate setup file to the folder from which the user starts the program, and enter the setup ID (file name) in the Target field (see page 54). Alternatively, you can store the setup file on a common drive in the network (but here it can be overwritten by other users). If you choose to place the setup file in a folder other than the one containing the program files, you must remember to specify the entire path name after id=. The setup ID is not the same as the user IDs in Dynamics NAV, but you can use the same names. In fact, it can be an advantage to do so because although you cannot see the name of the setup file in the program, you can always see the user ID on the status bar at the bottom of the program window. The following table lists the different program properties and the type of installation to which they apply:
Property ID Server Name Database Company NT Authentication Commit Cache Object Cache Net Type TempPath DB Test TestTarget Status Bar Close Forms On ESC Marquee Full Selection Quick Find Client X X X X X X X X X X X X X X X X X X X Server Described on page 35 page 36 page 36 page 37 page 38 page 39 page 39 page 40 page 40 page 41 page 41 page 42 page 43 page 43 page 44

33

Chapter 2. System Setup

Property DB Read-Only DBMS Cache Stoptime Sessions Install As Service Uninstall As Service

Client X X

Server

Described on page 44

X X X X X

page 45 page 46 page 47 page 48 page 49

34

2.2 Single-User and Client Setup Properties

2.2 Single-User and Client Setup Properties

This section describes all of the program properties that you can set for both clients and single-users.

ID Saving the User Setup

Program Property ID (clients only)

Purpose Saves the program setup

Where Specified By entering

ID=alice in the

Default Value Fin

Value Name of ID (including path if ID file is not located in Client folder)

Command line or the Target field.

Each user in a Dynamics NAV multiuser installation can choose the setup of windows and program properties that they want to use. Each user must have a unique ID, in order for the program to be able to save and use the setup selections of the individual users. You can create a user setup by starting the program with an ID. The information about the users setup will be stored under this ID. Here is an example in which the program starts with an ID called SUPER:
c:\Program Files\Microsoft Dynamics NAV\CSIDE Client for Microsoft Dynamics NAV\fin.exe id=SUPER

In a list of Dynamics NAV program files, you can see that each time you have started with a new setup ID, a file has been created that has the ID as the first part of the file name and.zup as the file name extension (for example, super.zup). This is called a setup file. Returning to the Original Setup You can always return to the standard setup file, fin.zup, by starting the program without specifying a setup ID.
fin.zup file will contain these changes. If you do not want to use this modified fin.zup file but would prefer to return to the original starting point of the program, delete the fin.zup file and start the program again without an ID. The program will create a new, clean setup file, named fin.zup.

If you have previously worked without a setup ID and made changes in the setup, the

For more information about zup files, see the section called "The Setup File" on page 32.

35

Chapter 2. System Setup

Server Name Choosing the Server

Program Property Server Name

Purpose

Where Specified

Default Value

Value Name of server

Specifies which Can be selected by None server to connect clicking File, to Database, Open or by entering
servername=My Server in the

Command line or the Target field.

This program property is used to specify the server that a particular client will connect to and does not apply in a single-user environment. You can set up the connection to the server in the Target field by entering the name of the server after servername=. You can connect to a server from within Dynamics NAV by clicking File, Database, Open on the menu bar. For more information about connecting with a server and opening a database, see the section called "Opening the Database" on page 65. Click File, Database, Information and click the Database tab to see which server you are currently connected to.

Database Selecting a Database

Program Property Database

Purpose Specifies which database to open. A C/SIDE Database Server can only have one database open at a time.

Where Specified

Default Value

Value Name of database (including path if database is not located in Dynamics NAV folder)

File, Database, Open None and Command line or by entering

database=My Database in the

Command line or the Target field. In a client/server installation this only works in combination with servername=

The Database program property is used to make the program start with a particular database open. (The database must already exist.) In the Target field or on the command line that starts the program, type the name of the database immediately after database=.

36

2.2 Single-User and Client Setup Properties

To open a database from within Dynamics NAV: 1 Click File, Database, Open. 2 In the window that appears, select the server and the database that you want to open. Click File, Database, Information to see which database is being used. For more information about databases, see the chapter called "Working with Databases" on page 57. C/SIDE Database Server can only have one database open at a time. If a client wants to open a database other than the one that is currently open, they will have to wait until the first database is closed before they can open the desired database. When you select a database for a client, you can also select the company you want to open automatically by using the Company program property.

Company Selecting a Company

Program Property Company

Purpose

Where Specified

Default Value

Value Company name

Specifies which File, Company, Open None company to open or by entering

company=CRONUS International Ltd. in the Command line or the Target field. In a client/server installation this only works in combination with servername= and database=

With this program property, you can select the company that will open automatically when a client starts Dynamics NAV. You must also specify the server and the database that contain the company before you specify the company in the Target field. Because Dynamics NAV can only have one database open at a time, you must connect to a server that already has the appropriate database open. If no other clients are using the system, you can select the server, database and company that you want. From within the program, you can select a company by clicking File, Company, Open. You can also select a company from the list displayed at the bottom of the File menu. You can see the current company on the title bar of the program window.

37

Chapter 2. System Setup

Windows Authentication Selecting the Authentication Mode

Program Property Purpose Where Specified File, Database, Open or by entering
ntauthentication =yes in the

Default Value Yes

Value Yes/No

NTAuthentication Specifies which type of authentication is to be used

Command line or the Target field.

This program property is used to determine which type of authentication is to be used when logging on to a server and opening a database. After selecting the server and the database in the Open Database window you must: 1 Select the type of authentication that is to be used. 2 Enter your user ID and your password, if database server authentication is being used. If Windows authentication is being used, you do not have to enter a password or user ID. 3 Click OK. Alternatively, you can enter yes or no after ntauthentication= in the Target field or on the command line that starts the program. If you are using Windows authentication, Dynamics NAV will start, automatically connect to the server and open the database that you have specified. If Database authentication is being used, Dynamics NAV will start and prompt you to supply your user ID and password before connecting to the server and opening the database. For more information about the types of authentication used in Dynamics NAV, see chapter 4 "Security".

38

2.2 Single-User and Client Setup Properties

Commit Cache Writing the Cache

Program Property Commit Cache

Purpose Makes the program run faster

Where Specified

Default Value

Value Yes/No

Tools, Options or by No entering commitcache= in the Command line or the Target field.

The Commit Cache program property allows Dynamics NAV to postpone writing the information stored in cache on the server to the database until later. Storing this information in cache allows Dynamics NAV to work faster. You must restart the program before any changes that you make to this parameter take effect.

Object Cache Improving Response Times

Program Property

Purpose

Where Specified Tools, Options or by entering

objectcache=8000

Default Value 8,000 KB

Value More than 0 KB and less than 1,000,000 KB

Object Cache (KB) Makes the (clients only) program run faster

in the Command line or the Target field.

The Object Cache property increases the speed of the program. Objects such as code, descriptions and windows that will be used on the client computer are stored in the object cache. This means that the client computer only needs to retrieve these objects once from the server, and then they will be stored in the object cache. The client computer must have enough memory to store the objects while they are being used in order to benefit from the object cache. Running out of object cache (that is, setting too small a value) does not cause any problems. The total size of all the objects used in the standard application is approximately 20 MB. If you have enough memory, set the object cache to 20 MB. The size of the most important objects, such as the table descriptions, is 1 MB. You should therefore, as a minimum, set the object cache to 1 MB. The upper limit is 1 GB. Click File, Database, Information to open the Database Information window and see how much space has been allocated in the Object Cache (KB) field. To change the amount of space allocated to the object cache, on the menu bar, click Tools, Options, and enter the setting in the Object Cache (KB) field.

39

Chapter 2. System Setup

NetType Selecting a Net Type

Program Property NetType

Purpose

Where Specified

Default Value

Value Netb, TCP, TCPS

Permits choice of Tools, Options or by TCPS network protocol entering NetType= in the Command line or the Target field.

To use Dynamics NAV in a network, you must select the network protocol that is used for communication between the server and the clients. There are three possible values:
nettype=tcps (for TCPS)

nettype=tcp (for TCP/IP) nettype=netb (for NetBIOS) TCPS is a secure version of TCP/IP and uses the Security Support Provider Interface (SSPI) with encryption enabled and Kerberos authentication. We recommend that you use the TCPS protocol. The same selection must be entered on all the client computers in the network as well as on the server. On the server, enter the net type you have selected in the Target field (see page 53) or on the command line after the start command. On the client computers, enter the selection in the Target field or click Tools, Options on the menu bar within Dynamics NAV. To check the setting when you are using the program, click File, Database, Information, and look at the Connection tab. For more information about the Database Information window, see page 73.

TempPath Location of Temporary Working Files

Program Property TempPath

Purpose

Where Specified

Default Value Windows XP:

<C:\Documents and Settings\User Name\Local Settings\Temp

Value Path to temporary files

Specifies location Tools, Options or by of temporary entering Temppath= in the Command line working files or the Target field. created automatically

When Dynamics NAV is running it creates a number of temporary files, which are automatically deleted when you close the program. As a default, the temporary files of each individual user are stored in the location listed in the previous table unless you specify a different working folder. If you do so, this working folder will be the default

40

2.2 Single-User and Client Setup Properties

location. You can specify the working folder in the Target field or by clicking Tools, Options. You must specify the full path, including the drive and all the folders.

DB Test Testing the Database

Program Property DB Test

Purpose Tests the database

Where Specified

Default Value

Value Min., Normal or Max.

File, Database, Test or None by entering dbtest=min in the Command line or the Target field.

You can use this program property to test the consistency and integrity of the database. You can also run the test from within the program by clicking File, Database, Test. You can specify exactly what you want to test in the dialog box that appears. When you enter the DB Test program property in the Target field, the database will be tested before the program opens. You can specify one of the following options:
dbtest=min dbtest=normal dbtest=max

You can read about the extent of these tests, as well as how to create a customized version of the database test, in the section called "Testing the Database" on page 68.

TestTarget

Program Property TestTarget

Purpose To specify how error messages generated by the database test are managed.

Where Specified File, Database, Test or by entering

testtarget=@scre en in the Command line or the Target field.

Default Value @screen

Value @screen, @eventlog, filepath

You use this program property to specify how any error messages that are generated during a database test are managed. They can be displayed on the screen or stored in the Event Log or in a text file. You can enter one of the following options:
testtarget=@screen testtarget=@eventlog

41

Chapter 2. System Setup

testtarget=filepath

You must enter the full path and the name of the text file. If you select event log, you can read the error messages that were generated during the database test in the Windows Event Viewer. If you select screen, the error messages will be displayed on the screen and the database test will require interaction from the user if any errors are found. Selecting screen can make the database test quite time consuming. For more information about testing the database, see Testing the Database on page 68.

Status Bar

Program Property Status Bar

Purpose Activates or deactivates the status bar

Where Specified Tools, Options

Default Value Yes

Value Yes/No

On the menu bar, click Tools, Options, and in the Options window you can specify whether or not the status bar will be displayed at the bottom of the program window.

The status bar contains the following information: The complete name of the active field and its contents. The work date. The current user ID. Whether or not any filters have been placed on the data (FILTER appears). Whether or not you are about to create something NEW (an account, for example). Whether you are working in Insert (INS) or Overtype (OVR) mode. When you make a visible change in the setup (such as making the status bar invisible), it is practical to use the ID program property and a setup file on your own computer. This makes the setup selections valid only for yourself. For more information, see the section called "ID Saving the User Setup" on page 35. This property can only be adjusted from within Dynamics NAV.

42

2.2 Single-User and Client Setup Properties

Close Forms On ESC

Program Property Close Forms On ESC

Purpose

Where Specified

Default Value Yes

Value Yes/No

Determines Tools, Options whether windows close when you press ESC

Click Tools, Options on the menu bar and you can choose whether or not the window you are working in will close when you press ESC. It is practical to use the ID program property and have a setup file on your own computer if you change the setup. This makes the setup selections valid only for yourself. For more information, see the section called "ID Saving the User Setup" on page 35. This property can only be adjusted from within Dynamics NAV.

Marquee Full Selection

Program Property Marquee Full Selection

Purpose

Where Specified

Default Value No

Value Yes/No

Determines how Tools, Options graphical objects are selected on the screen

With this setting, you can choose whether graphical objects must be completely within the frame in order to be selected, or whether it is sufficient for them just to touch the edges. This property is relevant for developers using the C/SIDE development environment. To make this selection, on the menu bar click Tools, Options and make your selection in the Options window. This property can only be adjusted from within Dynamics NAV.

43

Chapter 2. System Setup

Quick Find
Program Property Quick Find Purpose Quick search by letter in all windows Where Specified Tools, Options Default Value Yes Value Yes/No

This setting allows you to activate a quick search facility. When the Quick Find setting is enabled, you can search for an entry in any non-editable field, by typing a letter or number. You can also enter the entire name of the element you are looking for. When you enter a letter or number, the Find window opens automatically, and the first row that matches what you entered becomes the active row. When the Quick Find property is disabled, you can open the Find window by clicking Edit, Find on the menu bar or by clicking Find on the toolbar. This property can only be adjusted from within Dynamics NAV.

DB Read-Only

Program Property DB Read-Only

Purpose Determines that it is impossible to enter any data into the database

Where Specified By entering

dbreadonly= in the

Default Value No

Value Yes/No

Command line or the Target field.

This program property allows you to specify that the database has read access only. This prevents other users from entering data into the database.

44

2.3 C/SIDE Database Server for Microsoft Dynamics NAV Setup Properties

2.3 C/SIDE Database Server for Microsoft Dynamics NAV Setup Properties
Almost all the program properties for the server can be specified in the Target field or on the command line that is used to start the server. The following four properties apply to both the server and the client and have been described in the previous section:
Program Property Commit Cache Purpose Makes the program run faster Sets the name of the server Where Specified Command line, Target field During installation Default Value No Value Yes/No

Server Name Database

The name of the server computer None

Server name Name of database (including path if not located in Client folder) TCPS, TCP or Netb

Selects an existing Command line, database Target field

Net Type

Selects network protocol

During installation, Command line, Target field

TCPS

The server name is specified during the installation and the only way it can be changed is to uninstall the server and then install it again giving it a different name. The remaining setup properties only apply to the server and are described in this section.

DBMS Cache

Program Property

Purpose

Where Specified

Default Value

Value More than 100 KB and less than 1,000,000 KB

DBMS Cache (KB) Makes the program run faster

Tools, Options or by 8000 KB entering cache= in the Command line or the Target field.

This property only applies to server and single-user installations. DBMS Cache (Database Management System Cache or just Cache) is the name for a reserved space in the computers memory where data is stored temporarily, until it has been processed completely. After this, the commit cache transfers it to the hard disk. This system quickly frees Dynamics NAV for new work.

45

Chapter 2. System Setup

When the cache becomes full, old information in it is replaced with new. When you turn off the computer, everything in the cache is cleared from the memory. At that point, it has already been transferred from the cache to the database. The cache requires a minimum of 100 KB memory. The upper limit is 1 GB. To see how much cache has been allocated, click File, Database, Information and check the DBMS Cache (KB) field in the Database Information window. It is usually advantageous to specify as large a cache as possible. If the computer does not have enough memory, however, doing so can cause the operating system to "swap." Swapping means moving part of the cache to the hard disk to make more memory available. When this happens, the performance will be considerably slower because reading and writing take much longer when the hard disk is involved than when these operations are carried out in memory. To avoid swapping, you can add more memory to your computer, reduce the number of programs running simultaneously, or you can make the cache smaller. See page 155 to learn how to adjust the cache size. You must restart the program before any changes that you make to this parameter take effect.

Stoptime Closing the Program Automatically

Program Property Stoptime

Purpose

Where Specified

Default Value

Value hhmmss

Stops the server By entering None automatically at a stoptime= in the Command line or the particular time Target field.

You can set the server Stoptime program property in the Target field (see page 53) or on the command line. Enter the property as follows: stoptime=hhmmss, with hhmmss replaced by a time in hours, minutes and seconds. The server will stop automatically when the computers built-in clock reaches the specified time. You can use this function to make the database unavailable after a particular time. It is not necessary to stop Dynamics NAV in order to make backups. For more information see the chapter called "Making Backups" on page 129.

46

2.3 C/SIDE Database Server for Microsoft Dynamics NAV Setup Properties

Sessions Number of Client Sessions Allowed

Program Property Sessions

Purpose Specifies the number of client sessions that can be connected to the server at the same time

Where Specified By entering

Default Value

Value Number of sessions allowed by the license file

Maximum determined by Command line or the license file Target field.

sessions= in the

A session is an active (running) copy of Dynamics NAV. The term must not be confused with client, which refers to one connected computer. One client computer can run several sessions at a time if the client program is started more than once. Here are two different ways in which 10 sessions can be running: 2 computers, each with 5 sessions (each computer starts the program 5 times) 10 client computers, each started once The Sessions program property is set on servers and specifies the number of sessions that are allowed to be connected to the server at one time. When you obtain your license file, you obtain permissions for a specific number of sessions. These are automatically assigned to the server when you start it. To see how many sessions a license allows, click File, Database, Information. The Database Information window appears. Look on the Sessions tab, in the Licensed Sessions field. You use this program property to distribute the sessions efficiently either because you want to start several servers with the same license file or because you want to limit access to the current server. If a client tries to start a session that will exceed the number specified, a message will appear.

47

Chapter 2. System Setup

Install As Service

Program Property Install As Service

Purpose

Where Specified

Default Value Has no value

Value Has no value

Installs the server Target field or as a service on the Command line Windows server

C/SIDE Database Server is automatically installed as a service. When the C/SIDE Database Server is installed as a service, it starts every time you start the server computer without the user having to log on to the system. To manually install the C/SIDE Database Server as a service, enter the following after the command prompt:
server installasservice

Do not use the equal sign with this property. When you install C/SIDE Database Server 5.0 or NAV Application Server 5.0 as a service, they are assigned an NT Authority\Network Service account if the operating system supports this account.
Running as a service

If you want to run C/SIDE Database Server as a service or use the installasservice command line parameter when you start the server and use TCPS as the network type, you must ensure that the service is running as the NT Authority\Network Service account or the Local System account. The NT Authority\Network Service account only exists on Windows XP and Windows Server 2003. If you are running Windows 2000 Server, you should create an account with least privileges for the service or else the service will be assigned a Local System account. This account should at the most have the same privileges as the normal Users account or be a domain account that is not an administrator either in the domain or on any local computer. To have the highest level of security, we recommend that you run your C/SIDE Database Server on Windows XP or on Windows Server 2003, use TCPS as the network protocol and use the NT Authority\Network Service account as the service account. You must also remember to give the NT Authority\Network Service account or the user account that the server is running under access to the database file(s) to ensure that the users can connect to the database. To give the NT Authority\Network Service account read and write access to a database file on Windows XP: 1 In Windows Explorer, navigate to the folder that contains the database file. 2 Select the database file, right-click it and click Properties. 3 In the Properties window, click the Security tab and under the Group and user names field, click Add. 4 In the Select Users, Computers, or Groups window, enter Network Service and click OK. 5 NETWORK SERVICE has been added to the Group and user names field in the Properties window.

48

2.3 C/SIDE Database Server for Microsoft Dynamics NAV Setup Properties

6 Select NETWORK SERVICE and in the Permissions field give it Read and Write permission.
Note

If you install C/SIDE Database Server as a service and want to use Hotcopy to store the database backups on a remote computer, you must change the Log On options of the C/SIDE Database Server service. The C/SIDE Database Server service must use the credentials of a domain user that has the appropriate rights on the remote computer and not use the default value. For more information about HotCopy, see page 141.

Uninstall As Service

Program Property Uninstall As Service

Purpose

Where Specified

Default Value Has no value

Value Has no value

Target field or Uninstalls the server as a service Command line on the Windows
server

If you want to uninstall C/SIDE Database Server as a service, enter the following after the command prompt:
server uninstallasservice

Do not use the equal sign with this property.

C/SIDE Database Server Manager If the C/SIDE Database Server Manager Snap-in for the Microsoft Management Console is installed and C/SIDE Database Server is installed as a service, you can use the Microsoft Management Console to change the properties of C/SIDE Database Server using the C/SIDE Database Server Manager. The C/SIDE Database Server Manager is a Microsoft Management Console snap-in that makes it possible for you to manage C/SIDE Database Servers across a domain. With the C/SIDE Database Server Manager, you can see and reconfigure a number of C/SIDE Database Server properties. The C/SIDE Database Server can be started immediately after the installation of C/SIDE Database Server is complete. For more information about the installation, see the section Installing C/SIDE Database Server on page 13. The C/SIDE Database Server Manager interacts with C/SIDE Database Server the same way that the SQL Server Enterprise Manager does with SQL Server and requires that C/SIDE Database Server is installed. The C/SIDE Database Server Manager accesses the C/SIDE Database Server properties through the registry. If any changes are made to the properties, the C/SIDE Database Server Manager notifies C/SIDE Database Server about the changes, in order for it to respond accordingly.

49

Chapter 2. System Setup

You can change the properties at run-time, and they will be effective immediately. If C/SIDE Database Server is not running, the properties will take effect the next time you start C/SIDE Database Server.
Adding snap-in

To open the C/SIDE Database Server Manager for the first time: 1 Open Microsoft Management Console. The Microsoft Management Console consists of two panes. The left-hand pane displays the actual contents of the Manager, that is, an overview of the nodes that have been added to the view. The right-hand pane contains HTML pages that represent the server managers. 2 Click File, Add/Remove Snap-in. 3 In the Add/Remove Snap-in window, click Add. 4 In the Add Standalone Snap-in window, select C/SIDE Database Server Manager and click Add. 5 Click Close and OK to return to the console. You can now add C/SIDE Database Server to the server manager. In the following diagram, one C/SIDE Database Server node has been added to the C/SIDE Database Server Manager node.

Adding C/SIDE Database Servers

You can add as many C/SIDE Database Servers to the C/SIDE Database Server Manager as you want. They will be listed under the C/SIDE Database Server Manager node in the left-hand pane of the console. To add a C/SIDE Database Server to the server manager: 1 Right-click the C/SIDE Database Server Manager node. 2 Click New, Database Server Manager, and the following window appears:

3 The default value that you should enter in the Host Machine field is Localhost, but you have access to all computers in the domain.
Note

If you are using the TCPS net type, you must enter the real machine name of the server, for example, 'Server321'. If you are using TCP/IP, you can refer to the server as 'Localhost'.

50

2.3 C/SIDE Database Server for Microsoft Dynamics NAV Setup Properties

4 Enter the name of the C/SIDE Database Server that you want to add, for example DynamicsNAVDatabaseServer. This is the name that you gave the server when you installed it and must not contain any spaces. 5 Click OK to return to the console. C/SIDE Database Server Manager now contains one node, that is, one C/SIDE Database Server:

Properties

In the right-hand pane of the C/SIDE Database Server Manager window, you can define or change the properties of C/SIDE Database Server nodes. To see the configuration settings for a specific C/SIDE Database Server, click the C/SIDE Database Server node that you want to see the properties for. In the right-hand pane of the window, the properties are then displayed. You can enter new values for each of the shown properties for each C/SIDE Database Server node. You also have the option to start or stop C/SIDE Database Server as a service. In the Service Status field, you can see the current status of the server, that is, whether it is running or not. The field has the following three options: Stopped Starting Started When you have made your changes to the configuration (by editing the values) and confirmed the changes by clicking Apply These Settings, the C/SIDE Database Server Manager does the following: 1 Changes the properties for C/SIDE Database Server and places them in the registry. 2 If C/SIDE Database Server is running, the C/SIDE Database Server Manager notifies C/SIDE Database Server of the changes that have been made to the registry. The

51

Chapter 2. System Setup

changes take effect immediately. If C/SIDE Database Server is not running, the changes will take effect when you restart C/SIDE Database Server. If the configuration change fails, C/SIDE Database Server shuts down, and the program reacts in the following way: 1 The value in the Service Status field changes to Stopped. 2 An error message is then logged in the event log of the Windows server.

52

2.4 Setting the Program Properties

2.4 Setting the Program Properties

As explained in the previous sections, you can customize the system setup by changing the settings of the various program properties. Some settings must be entered in the Target field of the Microsoft Dynamics NAV Properties window (see the section called "Connecting Automatically" on page 54). You can also start a server from a command prompt. If the server has been installed as a service and the Startup Type option is set to automatic, the server will start automatically every time you start the operating system. You can specify the program properties in any order. Enter them after the programs start command, separated by commas. The name of each program property is followed by an equal sign (=) and the value to which the property is to be set, for example:
d:\fin\fin.exe servername=My server, company=CRONUS International Ltd., id=alice

This does not apply, however, to the two server properties: installasservice and uninstallasservice. For these properties, enter the parameter on the command line as follows:
d:\fin\server.exe installasservice

You can also set most of the program properties from the menu bar in the program for example, by clicking File, Company, Open (to set Company) and File, Database, Open (to set Database). To see the properties that do not exist as menu items click, Tools, Options and the Options window appears:

Note

Any changes made in this window are saved in the setup file and will be valid the next time the program is opened. If you do not want users to be able to make "permanent" changes in these options, you can set default values in the command line of a batch file (called fin.bat, for example) with which the user starts the program. The program properties that you can set depend on whether you are setting up a client computer, or a server.

53

Chapter 2. System Setup

Connecting Automatically Many of the properties that are described in the this chapter can be entered as command lines after the command prompt or included as program properties that are automatically set when you start Dynamics NAV. To carry out this procedure you must have administrative rights on the computer. To set them as automatic program properties: 1 Open Windows Explorer. 2 Open the folder C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft Dynamics NAV. 3 Notice that there are two identical Dynamics NAV icons on the right. You must select the icon for the version of Dynamics NAV that you are using. 4 Click File, Properties or right-click the CSIDE Client for Microsoft Dynamics NAV icon and select Properties. The Microsoft Dynamics NAV Properties window appears:

5 Click the Shortcut tab. The Start in field shows where Dynamics NAV is located. It contains the path for the start command fin.exe. After the start command, you can add other commands and settings for program properties. Here is an example:
servername=My Server, nettype=tcps, company=CRONUS International Ltd.

When you set the program properties in this way, the program performs certain tasks the next time it is opened. It will use TCPS to connect to the server called My Server and open the company called CRONUS International Ltd., if it exists in the database. If you dont enter the company parameter, you will have to open the company manually after the program starts.

54

2.4 Setting the Program Properties

You can change any of these selections while you are working. You can do this from within the program. For example, you can select a different database (provided it has already been created) or a different company, or you can create a new company. If you do not want a client to be able to do these things, you can set limits when you assign user permissions (by setting limits on the "system" object type). You can read about assigning user permissions on page 115.

55

Chapter 2. System Setup

56

Chapter 3 Working with Databases

The Microsoft Dynamics NAV database is the heart of the application. All the information, companies, modifications, reports, and so on are stored here. It is therefore important that you know how to manage the database and are familiar with the tools that Microsoft Dynamics NAV provides for doing this. This chapter describes the basic operations involved in working with a database, as well as some more advanced features. The chapter contains the following sections: The Standard Database Creating and Maintaining Databases Testing the Database Deleting the Database Database Information Database Efficiency License Files Expanding a Working Database Advanced Database Information Setting up Outlook Integration Standby and Hibernation License Agreement Setup

Chapter 3. Working with Databases

3.1 The Standard Database

You must have a database to be able to work with Microsoft Dynamics NAV. When you install a single-user installation, a standard database called database.fdb is automatically provided.

Using the Standard Database You can use the standard database (database.fdb) in two ways: with a demonstration license (cronus.flf) or with your own license (fin.flf). The standard database contains a demonstration company called CRONUS International Ltd. Using the Demonstration License File Cronus.flf If you choose to work with the demonstration license file, cronus.flf, you have access to all the Dynamics NAV application areas and can test all the functions including ones you have not purchased permissions for. The demonstration license file does, however, contain certain restrictions:
Restrictions of Cronus.flf

Posting is only possible in the period November to February. You are only allowed to make 4000 write transactions in a database. The maximum number of companies is two. You can only have stand-alone installations or run C/SIDE Database Server on Windows XP. You can have a maximum of two sessions running at any one time. Any company name must start with CRONUS (written in capital letters). This ensures that it will be clearly identifiable as a demonstration company and you will not accidentally create a "real" company with the wrong license file.

Using Your Own License File If you work with your own license file (fin.flf), you can use only the functions for which you have purchased permissions. This means that you can see only the data for those functions even in the demonstration company. On the other hand, your own license file does not limit posting dates. You can also create as many companies in database.fdb as you have purchased permissions for. If you create more than one additional company in the database, however, you will no longer be able to use the license file cronus.flf because it allows only two companies in the database. Thus, you will lose the benefits of using cronus.flf, for example, you will not be able to see all the functions in the entire demonstration company.

58

3.2 Creating and Maintaining Databases

3.2 Creating and Maintaining Databases

The demonstration database contains many limitations, which can be difficult to keep track of. Therefore, we recommend that you create a separate database for your own companies. Your license file specifies the maximum size for your database, and you can create as many new companies as you like within the allowed space. To create a new database for your companies, you must: 1 Create the new database. 2 Restore the backup of the original standard database (database.fbk) into the new database. The backup must include at least Data Common to All Companies and Application Objects. Data Common to All Companies includes the programs report list and permissions groups. Restoring Application Objects transfers the accounting application to the database. For more information about making backups, see "Making Backups" on page 129.
Note

Regardless of whether you choose to continue to work in the standard database or create a new one, make sure that you always have at least one copy of the database you are working with stored in a safe location. If you accidentally delete the folder containing Dynamics NAV, the database file will disappear, which means that all your data will be lost.

Creating a Database To create a new database from a client or from a single-user installation: 1 Click File, Database, New to open the New Database window:

2 In the Server Name field, enter the name of the server. You can use the AssistButton and select the server from a list of the C/SIDE Database Servers that are available within the current domain. 3 When you enter something in the Server Name field the AssistButton in the Database Name field will disappear, indicating that you must enter the name of the database manually. If you want to create a database that will not be stored on the server you must enter the entire path and the name of the database manually. If you want to create a database that is stored locally, you do not need to enter anything in the Server Name field and can use the AssistButton to open a standard Windows dialog box where you can create the database in the desired location.

59

Chapter 3. Working with Databases

4 Enter the desired size (KB) of the database in the File Size (KB) field. The minimum size (1000 KB) is already entered in the field. To the right of this field, you can see what percentage of the maximum size is being taken up by this database. 5 The Licensed Size field tells you the maximum size of your database. This information is contained in your license file.
Warning

Never create the database on compressed drives (this also includes the Compress property under the NTFS file system). A database located on a compressed drive can be corrupted by a power failure. Database Size The size depends on how many bookkeeping transactions will take place each day, week, and so on. Your Microsoft Certified Business Solutions Partner can help you choose a suitable database size. Do not make the database too large to begin with; you can always expand it, but you can never make it smaller (and the allocated space cannot be used for anything else on your computer). The maximum size of a database is 256 GB. The number of KB you have permissions for is displayed in the Licensed Size (KB) field. Database in Several Files When you create a database, it consists of only one file. After the database has been created, you can divide it into several files and place them on different hard drives. This process is described in the next section called "Expanding the Database" on page 61. Dividing your database into several files on several (physical) disks, lets you utilize disk space optimally. It also reduces the access time to the database, which improves the programs performance. You can read more about performance issues in the chapter called "Advanced Performance Issues" on page 147.
Using Commit Cache If you have divided your database into several files on several disks, it will be utilized

most efficiently if you start the program with the program property Commit Cache set to Yes. You can set this up under Tools, Options on the menu bar or in the Target field as described on page 54. In multiuser installations, where there is a network server available, it is possible to start the C/SIDE Database Server program from a computer in the network and at the same time have the database files located on the network server instead of on C/SIDE Database Server. This is not recommended, however, because it places a heavy load on the network, which will decrease performance. Normally, Dynamics NAV sessions communicate directly with C/SIDE Database Server, but if the database files are on a network server, all the database transactions must be sent from the server program via the network to the database files on the network server. Another reason for not having database files on the network server is that this increases the risk of introducing transmission errors into the data that is being sent back and forth. Data sent between the server program and the database in this way is not protected by the Dynamics NAV checksum system. Transmission errors in a network are

Multiuser installations

60

3.2 Creating and Maintaining Databases

much more common than disk errors or other computer errors, so the risk of introducing errors is sharply increased by putting the database files on the network server. Do not store database files on drives that are "shared" through the network program. If database files are located on shared drives, the programs performance declines drastically.

Expanding the Database You use the expand database function to divide the database into several database files and spread them over separate disks. You can also use it to increase the size of these files if the database is beginning to run out of space and to increase the size of a single file database. You do not need to expand your database until you are about to run out of available space. You can check this by clicking File, Database, Information and looking in the Database Used (KB) field in the Database Information window. The value in this field should not exceed 80% (rule of thumb). As soon as it reaches this level, it is a good idea to expand the database. The amount of free space in the database must reflect the amount of space required for the maximum number of updates that can be carried out by the other concurrent users, when one user is performing the lengthiest task that your installation contains. This is approximately 16 MB per user (rule of thumb).
Warning

Dynamics NAV does not give you any warning that you are about to run out of space in the database. You must keep track of the status of the database, including how much space is left and how much database space you have purchased permission for. However, Dynamics NAV displays an error message if there is not sufficient free space to perform the current task. It also displays an error message if you are performing a time-consuming task and all the available space in the database that contains your snapshot has been used by other concurrent activities.
Performance

The performance of the program depends only slightly on the size of the database. Unsatisfactory performance may be caused by problems with your equipment, by storing the database in an impractical location, or by setting the Cache and Commit Cache program properties without giving due consideration to your needs. You can read more about how to set the caches starting on page 155. To expand your database, you must have adequate space available on your hard disk(s), and you must have purchased permission for (at least) a database of the size you want to expand to. The Licensed Size (KB) field in the Database Information window shows the size database you have purchased permission for. If you dont have permission to expand the database further, an error message will appear when you try to do so. Remember that it is not always a good idea to simply expand your database to the maximum size possible; once space has been allocated to the database it cannot be used for anything else on your computer.

Requirements

61

Chapter 3. Working with Databases

Note

Before you expand your database, you should back up your database as described in the chapter called "Making Backups" on page 129. Ways to Expand the Database There are two ways to expand the database: Expand the existing database file. Create one or more new database files, possibly in different locations. This can be advantageous if there is more space on another disk. No matter which method you choose, start by clicking File, Database, Expand. The Expand Database window appears:

Expanding an To expand the database, enter the number of kilobytes you want to add in the Add existing database file (KB) field, or enter the new total number of kilobytes in the New Size (KB) field. Click

OK to expand the database.

Creating an extra database file

To create an extra database file in order to expand the existing database, click Advanced in the Expand Database window. The Expand Database (Advanced) window appears:

Here you enter information about the new database file or files you want to create. Each new database file must be set up on its own line. Enter the name (including the full path) in the File Name field and the size of the database file in the Add (KB) field. If the actual database name is db.fdb, for example, you could call one database file

62

3.2 Creating and Maintaining Databases

"dbpart1.fdb" and another "dbpart2.fdb" and place them in different folders on different drives. When you are expanding the database it is important to remember that: All of the database files must be approximately the same size. This improves performance. The database can consist of up to 16 physical files. Each database file can be between 1 KB and 256 GB. All of the files together cannot exceed 256 GB.
Name of a database with multiple files

The proper database name, that is, the one that will be referred to elsewhere in the program, appears on the first data entry line. This is the primary file and it points to the other files. As far as the user is concerned the database is one logical file. If you need to use the database name (to open the database or make a Dynamics NAV backup, for example), use this name and ignore the fact that the database consists of several files. At the bottom of the window, you can see the size of the complete database increase as you create each file. When you click OK, the information is saved, and you can continue to work in the database.

Moving a company from one database to another

If you happen to create a company in the wrong database, you can move it to the correct database by making a backup copy of just the company. (Select the appropriate company before you begin the backup.) When the backup is complete, you open the correct database and restore the company backup into it. Before you can use this database, you must restore a backup of the standard database.

Restoring the Standard Database The database that you have just created contains only a few basic tables and is not yet ready for use in Dynamics NAV. Before it can be used, you must restore the backup of the original standard database (database.fbk) into the new database. This backup comes with Dynamics NAV and is stored in the Dynamics NAV folder on the client computer if you have carried out a complete installation. The backup contains all the information necessary for using the database, including Data Common to All Companies and Application Objects. Data Common to All Companies includes the programs report list and permissions groups. When you restore the Application Objects, the accounting application is transferred to the database.

63

Chapter 3. Working with Databases

To restore the standard database: 1 Open the new database, and on the menu bar click Tools, Restore. The following window appears:

2 Select database.fbk and click Open. The Restore window appears:

3 Make sure that Custom is selected and that the Data Common to All Companies and Application Objects check boxes are selected.

64

3.2 Creating and Maintaining Databases

4 Click OK to start restoring the database. The following window appears:

The restore procedure will take a few minutes, and this window allows you to monitor its progress. For more information about making backups and restoring databases, see the chapter called "Making Backups" on page 129. When the restore process has been completed, your database will be ready for use in Dynamics NAV. You can now create your own companies in the database.

Opening the Database On clients and single-user installations, you can open the database from within the program. To open a database: 1 Click File, Database, Open. The Open Database window appears:

2 In the Server Name field, enter the name of the server. You can use the AssistButton and select the server from a list of the C/SIDE Database Servers that are available within the current domain. You can only use this function if you are running in a Windows network.

65

Chapter 3. Working with Databases

Note

If you are using the TCPS net type, you must enter the real machine name of the server, for example, 'Server321'. If you are using TCP/IP, you can refer to the server as 'Localhost'. 3 If you have selected a server, you will not have to enter any information in the Database Name field. If you want to open a database that is not stored on the server, you must enter the entire path and the name of the database manually. If the database is stored locally on your hard drive, you must enter the name of the database in the Database Name field. If you do not know the name of the database, you can use the AssistButton. A standard Windows dialog box will appear and you can use it to locate the desired database with the file extension .fdb. 4 In the Authentication field, specify the type of authentication you require. You can choose between Windows Authentication and Database Server Authentication. You can use the AssistButton to select the authentication type from a list. You can read more about authentication in the chapter called "Security" on page 109. 5 You must enter a user ID and password if you are using database server authentication. If you are using Windows authentication, you do not have to enter a user ID and password. 6 Click OK to open the database. You can specify the network type that will be used when you connect to the server. In the Open Database window, click the Advanced tab. However, it is not usually necessary to change the network type from the default setting.

You can use the AssistButton to select the net type from a list and then click OK to accept your selection. You can choose between TCPS, TCP/IP and NetBIOS.TCPS is the default network protocol. For more information about using TCPS, see NetType Selecting a Net Type on page 40 and Running as a service on page 48. If there is already a database open, it will be closed when you open the new one. However, if you are working in a multiuser setup you will not be able to close a

66

3.2 Creating and Maintaining Databases

database as long as one of the other clients is working with it. C/SIDE Database Server can only have one database open at a time. When you have opened the database, you can open a company by clicking File, Company, Open, or you can add a new company by clicking File, Company, New. You can only have one company open at a time. However, you can open and close companies regardless of whether other users are working with them. Information about the database and the company that are open when you close Dynamics NAV is saved in the .zup file, and that database and company will be used as a default database and company when you start the program again. You can also use the Database program property to specify the database you want when starting a server or changing to another (existing) database. You can set the Database property in the Target field (see page 54) or on the command line that starts the program, like this:
d:\finserv\server.exe database=db.fdb
Note

Dynamics NAV will automatically open the database and company that you were last working on when you reopen the program.
Automatic reconnection

Dynamics NAV can automatically detect if the connection to the server has been broken. It will do this the next time the client tries to access the server after having been inactive for at least 10 minutes. If the connection has been broken, for example, because the server has been stopped and then restarted, Dynamics NAV will attempt to reestablish the connection to the server and open the database with the same settings that were used when the database was last opened. The user can then continue to work with the database and will not notice that the server has been unavailable. This allows you to shut down the server temporarily, for example, for hardware upgrades or modifications to server properties and then restart it, without causing any serious inconvenience.

Closing a Database If you want to close a database (for example, before opening another), you can click File, Database, Close. However, you dont have to follow this procedure; Dynamics NAV will save all data and close everything down correctly when you select another database or quit the program. There can never be more than one database open at a time, but you can choose to close the database as an extra safety precaution if you want to delete a database or do something similar. On servers, you can use the Stoptime program property to stop the server at a specific time of day. After this, the clients will no longer be able to access the database.

67

Chapter 3. Working with Databases

3.3 Testing the Database

To safeguard against errors, you should frequently check the integrity and consistency of your database. You do this from clients or single users.
Without opening the You can also test the database without opening the program. You start the test by program setting the program property DB Test in the Start in field (see page 54). Here is an

example:

d:\Microsoft Dynamics NAV\CSIDE Client for Microsoft Dynamics NAV\fin.exe servername=My Server, ntauthentication=yes, database=database.fdb, dbtest=normal

The possible settings for DB Test in the Target field are min., max. and normal. You can customize the database test if you start the test from within Dynamics NAV.
From within the program

To start the test from within the program, click File, Database, Test. The Test Database window appears:

You determine the extent of the test by selecting one of the four option buttons at the top of the window (such as Minimum). When you select an option, the individual tests included in that option are run. The following table lists what the different tests involve:
Level Minimum Test Fields Test primary keys and data Features Checked All records in all tables can be read. Records are sorted in ascending order according to the primary key. All fields are correct in relation to the field type. All BLOBs (fields for pictures for example, on the item card) can be read. You can read about BLOBs in the Introduction manual and the Application Designers Guide.

Test BLOBs

68

3.3 Testing the Database

Level Normal

Test Fields All the fields included in the Minimum test, plus: Test secondary keys

Features Checked

All secondary keys in all tables can be read. Sorting is done correctly according to the secondary key. All fields in the sorting have the correct field type. All space in the database is either used by a sorting key or is available.

Test space allocation Maximum All the fields included in the Normal test, plus: Test relationships between primary and secondary keys Test field relationships between tables Custom

The connection between the primary and secondary keys is correct.

All fields that have relationships to other fields can be accessed from the field to which they are related.

The same fields as in the Whatever you select. Maximum test, but you can cancel the ones you dont want to run.

Primary and secondary keys, mentioned in the previous table, are sometimes described as indexes and are used, for example, when you sort information. The keys determine how information in a table is ordered. You switch keys to sort information in a table in a different way. For example, you might want to sort your customers by name or by number. See the Application Designers Guide manual for more information about sorting. For a more detailed description of keys, see page 89. How often you need to test the database depends on how secure the rest of the system (including the network) is and what level of security you need. It is a good idea, however, to test before you make a backup especially if you dont use the Dynamics NAV backup function.
Note

Test space allocation cannot be executed when there is more than one user on the system. If you select a test that includes it, Test space allocation will not be executed if there are other users on the system, but the rest of the test will be executed normally.

69

Chapter 3. Working with Databases

Click the Options tab to specify how the output from the database test is managed:

The output from the database test consist of the errors messages that are generated during the test. These can be handled as follows:
Option Screen Means The error messages are displayed on the screen. Each time an error message is displayed you must click OK before the test continues. This can be quite troublesome if the test generates a large number of messages. The error messages are written in the operating systems event log. For more information about the event log, see the operating systems documentation. The error messages are written to a text file. Use the AssistButton to specify the name and location of the text file.

Event Log

File

If you select Event Log or File the database test is not interrupted and will not take so long. You can then review any error messages that were generated and repair the things that caused them. While the test is being performed, the following status window is displayed:

If an error occurs, the program stops and displays an error message indicating what the error is and where it occurs. The following steps must then be taken: 1 Export a Dynamics NAV backup copy of the database. 2 Create a new database, and restore the backup into it. 3 Run a Maximum test on the new database to check it.

70

3.3 Testing the Database

4 If it is error-free, check to make sure that the company data is correct. Afterwards, you can continue to work in the new database. 5 If this does not work, contact your Microsoft Certified Business Solutions Partner for help.
Warning

Never delete a corrupted database (one that contains an error) before a new, tested database has functioned without errors for a period of time. It is important that you remember to make backups and make sure that they can be restored. You can read more about backups in the chapter called "Making Backups" on page 129.

71

Chapter 3. Working with Databases

3.4 Deleting the Database

Never delete a database without making a backup. Save one or more copies of the backup in a secure place. (See the chapter called "Making Backups," which discusses how to make backups as well as some of the legal requirements about saving old financial data.) After you have made the backup, you can click File, Database, Delete to remove the copy of the database that will no longer be used. Before the database is deleted, you will have to answer two messages like this one:

When you delete a database, everything in the database is deleted, including any customizations you have made. You are not able to delete a database that you cannot open from within Dynamics NAV. You cannot delete a database if other clients are connected to the database.

Deleting Part of a Database If you dont want to do anything quite so drastic as deleting the entire database, there are various other ways to delete information: To remove old information, use the Date Compress batch jobs. In the navigation pane, click Administration, IT Administration, Data Deletion, Date Compression and then click the relevant application area. To remove individual records, click Edit, Delete. There must be no open entries or nonzero balances for the records you want to delete. To remove a company, click File, Company, Delete. If you have access to the development environment for Dynamics NAV, you can delete individual objects. You can read about the development environment in the Application Designers Guide. If you need to delete almost everything except a couple of objects, such as some reports, you can save the objects by exporting them before you delete the database. You can then click File, Database, Delete to delete the database. Finally, you can restore the old objects to a new database.

72

3.5 Database Information

3.5 Database Information

To see information about the current status of the database in Dynamics NAV, click File, Database, Information. The Database Information window appears:

This is where you can check to see whether everything is set up correctly, whether there is enough space available in the database, how much cache has been allocated to the program, and so on. (You cant change anything in this window you can only view information.)

Database The Database tab contains information about the database that is currently open. The name of the database appears in the Database Name field. A database can be set up to consist of several individual files. You can see the names and sizes of the files if you click the AssistButton to the right of the field. The Database Files window appears:

If you click Tools, Zoom (CTRL+F8) from the menu bar while this window is displayed, you will get more detailed information about the database information that can be used for statistical purposes and to check the performance level. You can read more about performance issues in the chapter called "Advanced Performance Issues" on page 147. The Database tab also displays the following information about the database: How much of the total database is currently in use and what percentage of the total space in the database is being used. This should not exceed 90%. If it does, you can expand the database by clicking File, Database, Expand. See page 61 for details.

73

Chapter 3. Working with Databases

How large the total database is, and what percentage this is of the total database size you have permissions for. How much database space you have purchased permissions for. Whether DBMS cache has been allocated in the system and how much. The value affects the program speed. To specify cache size, use the program property Cache or click Tools, Options and enter the size as the value for DBMS Cache (KB). Whether Commit Cache is turned on (a check mark means that it is). The commit cache affects the program speed. To specify the size of the commit cache, use the program property Commit Cache or click Tools, Options and enter the size as the value for Commit Cache. Whether object cache has been allocated in the system. The Object Cache program property is used only on clients where it affects the speed of the program.
Note

Due to the size of the memory allocation blocks (8KB), the DBMS Cache field can display a slightly different figure than expected. The DBMS Cache rounds down to the nearest block, for example, if you have allocated 500 it will be rounded down to 496. You can read about the various program properties in the chapter called "System Setup"on page 31.

Connection On the Connection tab, you can see the following information:

Whether the database you are working in is located on your computer or on a server. If you are working in a database that is located on a server, the name of the server and the network protocol that is being used.

74

3.5 Database Information

Sessions The Sessions tab contains the following information:

The Current Sessions field tells you how many sessions (active Dynamics NAV programs) are presently connected to the database. The number is shown both as the number of sessions and as a percentage of the maximum number of sessions for which you have permissions. Each computer can have several sessions running at once. The Licensed Sessions field tells you the maximum number of sessions (active Dynamics NAV programs) that can connect to the database. If you need more, you must obtain them from your Microsoft Certified Business Solutions Partner. If you click the AssistButton to the right of the Current Sessions field, the Database Sessions window appears listing details of all the sessions connected to the server:

The window lists all the current connections to the database and the time when each user logged on. Each line represents one login. A user can appear more than once if they have started more than one session. The session that you are currently using has a check mark in the My Session field.
Terminating a session

You can terminate one of the sessions by selecting the line in question and deleting it. The session will no longer take up any resources on the server. This user will then be disconnected from the server and will have to restart the program if they want to continue working. To terminate a session, you must have permission to delete data from the Session table.

75

Chapter 3. Working with Databases

If you put the cursor on a line in the Database Sessions window and click Tools, Zoom on the menu bar, you will get more detailed information about a particular session. The following window appears:

The information here can be used for various statistical purposes. The Tables button at the bottom of the Database Information window opens a window displaying information that is used for analyzing where and how data is distributed in the database. You can read about this in the following section.

76

3.6 Database Efficiency

3.6 Database Efficiency

After you have been using Dynamics NAV for a while, it is a good idea to check how effectively the database is being utilized. There are a number of special tools for doing this. Click File, Database, Information, and then click Tables at the bottom of the Database Information window. A list of all the tables in the database appears:

All the information in Dynamics NAV is organized in tables. Each line in the window represents one table. You find the following information on each line:
Field Company Name Table No. Table Name Contents The name of the company to which the table on the line belongs. The number of the table. (Each table in Dynamics NAV has a unique number.) The name of the table. This is the name that is used in C/SIDE rather than the name of the window that displays the table on the screen (they are often the same). The number of records (entries) in the table. By keeping track of how many new records have been added in a certain period, you can estimate the number of records you can expect in the next period. The average number of bytes per record in a table. Combining this with the number of records in the No. of Records field enables you to estimate whether you will have enough space in your database. The total size of the table, in kilobytes. This is a percentage that tells how effectively Dynamics NAV uses this table in the database. The higher the percentage, the more effectively the table is utilized. To optimize the location of data in the table, click Optimize at the bottom of the window. (This column is not shown in the picture.)

No. of Records

Record Size

Size (KB) Optimization

The values displayed in the Database Information (Tables) window cover all the information linked to the individual tables in Dynamics NAV, both financial information and keys. The next section explains how to use this information to improve the utilization of the database.

77

Chapter 3. Working with Databases

Using Keys and Key Groups to Improve Performance To make the information in the tables as useful as possible, many of the tables have several predefined sorting keys. To view these predefined sorting keys, select a table in the Database Information (Tables) window and click View, Sort and the Table Information - Sort window appears:

You can change the sorting order for the table from ascending to descending. For more technical information about the keys, click File, Database, Information, and then click Tables in the Database Information window. In the Database Information (Tables) window, place the cursor on the table whose keys you want to see and click Keys. The Database Information (Keys) window appears:

Keys have several uses, but maintaining them (if, for example, one is renamed) places a large demand on the systems resources. You can therefore improve database utilization and performance by deactivating or completely removing keys that are not used in your installation. However, you should not remove or deactivate keys without giving it some thought because there are certain functions the program cannot run when certain keys are missing. Because of this, Dynamics NAV does not allow you to change the status of keys unless you have access to the C/SIDE development environment. If you do not have access to C/SIDE, you can have your Microsoft Certified Business Solutions Partner create a set of keys that makes a particular type of task easier, for example, running a lengthy report. These keys can be set up as a key group, which you can enable and disable without risk. The program will perform better when you have disabled the key group because the system does not have to maintain the keys included in the key group.

78

3.6 Database Efficiency

Adding a large number of keys to database tables decreases performance. However, by making the keys members of predefined key groups you can have the necessary keys defined and only activate them when they are going to be used. To enable or disable the key groups, click File, Database, Information, Tables, Key Groups. The Database Key Groups window appears:

Enter the key group names, and click Enable or Disable. You must remember the names of the key groups. Setting Up a Key Group To set up key groups (you must have access to C/SIDE), you must specify which key group each key belongs to. The keys are found in the definitions of the tables. To set up a key group: 1 Click Tools, Object Designer. 2 Click Table. 3 Select the table that contains the key, which you want to include in the key group. 4 Click Design. 5 Click View, Keys. You can now see the keys for the selected table.

79

Chapter 3. Working with Databases

This window shows the keys for the Customer table:

Disabling a Key Group If you do not often need to sort the Customer table by the Currency Code key, you could put the Currency Code key in a key group called, for example, RarelyUsed and disable it. The name of the key group must not be longer than 10 characters. To rename a key group and disable it: 1 In the Keys window (as shown in the previous example), select the line containing Currency Code. 2 Click View, Properties. 3 In the Properties window, enter RarelyUsed for the KeyGroups property. 4 Save the table definitions by closing the Table Designer. 5 Click File, Database, Information, Tables. 6 Select the Customer table, and click Key Groups. 7 To disable the key group RarelyUsed, type RarelyUsed in the Key Group field. 8 Click Disable. Now, if you click Sales & Marketing, Sales, Customers and then on the menu bar, click View, Sort, you are no longer able to sort the Customer table by currency code.
Note

When you re-enable keys that have been disabled, the program performs a sorting procedure that requires a certain amount of free space in the database.

Decreasing the Table Seek Time The Dynamics NAV database is organized in a tree structure. As this tree expands with new records, these records are distributed at the bottom level of the tree. The tree is designed so that data is placed only at the bottom level. For details of the tree structure, see page 89. It is possible to decrease the seek time in the tree by optimizing the table in question. Optimizing the table will make finding the specific record quicker by removing any empty space in the table and possibly minimizing the number of levels in the tree.

80

3.6 Database Efficiency

To minimize the number of levels in the tree for a particular table, select the table in the Database Information (Tables) window and click File, Database, Information, Tables, Optimize. On the other hand, if you often insert new records in the table, the program inserts the record in its proper place, between all the other records, by moving all the other records to make room for the new record. So inserting records in a table that is often used can take longer if its tree structure has been optimized and the empty space removed. You can read more about the database structure on page 89.

Finding Errors in the Tables If you suspect that there are errors in some tables, you can perform error tests. To perform a test on selected tables, click File, Database, Information, Tables. Then highlight the tables to be tested and click Test. The Test Tables window appears:

If you do not select any tables, the test will be carried out on all the tables. From this window, you can activate the same tests, (except the space allocation test), that you can by using the DB Test program property or by clicking File, Database, Test. If you choose to test only one table and select Test field relationships between tables, the relationships between the selected table and the related tables will be tested. If Commit Cache is turned on, the test will be speeded up significantly.

Creating Space in the Database The number of entries in the system will grow as you continue to use Dynamics NAV. At some point you must, therefore, choose between expanding the database or combining some of the old entries, so they take up less space. Date Compression Combining entries is called compression. Although you can only compress entries from closed fiscal years, you can compress them more than once.
Note

Date compression removes information from the entries, so you must always make a backup of the database before you run the function.

81

Chapter 3. Working with Databases

What Is Combined? During the compression process, several old entries are combined into one new entry. For example, G/L entries from previous fiscal years can be compressed so that there is only one positive and one negative entry per account per month (one each for debit and credit). After the compression process has been carried out, certain fields will always remain in the combined new entry. The contents of each of these fields will be set to a common or total value. In G/L accounts, for example, these are Posting Date, G/L Account No., Gen. Bus. Posting Group, Gen. Prod. Posting Group, Gen. Posting Type, Amount and VAT Amount. The contents of the other fields will be cleared by the date compression. You can also select other fields to be retained. If you select more fields to be retained, this will result in more new, compressed entries per time period. The fields that you can select are listed in the window that appears when you choose the Date Compression batch job. What Is the Result? The number of entries that remain after the date compression process has been completed depends on how many filters you set before you start the batch job, which fields you want to have combined, and the compression period you select. There will always be at least one combined entry. When the batch job is finished, the result is displayed in the date compression register in the area of the program where you ran the batch job. The amount of a date-compressed entry is the sum of all the entries that have been compressed into it. The date is set at the starting date of the compression period, for example, the first day of the month if you are compressing by month. After compression has taken place, you can still see the net change in each account for each compression period. Starting Date Compression There are date compression batch jobs for each type of entry that can be created in Dynamics NAV. The batch jobs are found in the Administration menu. For example, to find the batch job for date compression of G/L entries, click Administration, IT Administration, Data Deletion, Date Compression, G/L Entries and the following window appears:

82

3.6 Database Efficiency

Note

When you choose other date compression batch jobs (other than G/L Entries), a tab appears containing filters that you can set on the entries before they are removed for compression. You can use this facility if you only want entries with particular values in a field to be included in the compression. The Options tab contains the following fields, in which you can set up the conditions for the compression:
Field Starting Date Comments Enter the first date you want to include in the compression. The compression will include all (for example, G/L) entries from that date until the date in the Ending Date field. If you do not enter a date, the compression will begin with the first posting date in the program. Enter the last date you want to include in the compression. All (for example, G/L) entries from the starting date through this date will be compressed. Enter the time period over which you want to combine entries. To see the options, click the AssistButton to the right of the field: Entries Combined: From the same posting date From the same week (only entries with a common month and accounting period) From the same month (only entries with a common accounting period) From the same year (only entries with a common accounting period) From the same quarter (only entries with a common accounting period) From the same fiscal year and calendar year From the same accounting period (grouped within the same calendar year) Enter the description that will accompany the entry or entries created by the compression. Date Compressed is suggested as a default. Enter a check mark by the fields whose contents you want to save. Selecting a field here, means that when a group of entries for a period is compressed, a common or total value for the field will be retained in the combined entry. Thus, you will still have all the information about this field for each compression period. The more fields you select here, the more detailed the information is in each compressed entry. Click the AssistButton and the Dimension Selection window appears. In this window select the dimensions that you want to retain in the compressed entries.

Ending Date

Period Length Options: Day Week Month Year Quarter Year Period Posting Description Retain Field Contents

Retain Dimensions

83

Chapter 3. Working with Databases

Field Retain Totals

Comments Enter a check mark if you want each combined entry to include the total contents of the Quantity field. This option is available for G/L entries to allow you to retain the totals if you want to. In many cases, this total will be meaningless because the Quantity field is used in various contexts. However, you may want to retain the totals if you have used the field when registering purchases, for example, so you can choose to have it included in the combined entry.

Note

If you select Day, Week, Month, Quarter or Period as the time period, you will later be able to compile various statistics about the compressed entries by period. Example of Date Compression In the following scenario, a company has used Dynamics NAV since January 1, 1995 for five complete fiscal years that follow the calendar year. The company is now in the middle of the sixth fiscal year (2000). Until now, no entries have been deleted or compressed, but the company believes it no longer needs to have a complete historical record of everything that has happened. Here is a suggested compression strategy for G/L entries: 1 In the present fiscal year (Fiscal Year 6), save all entries (no date compression at all). 2 In the preceding fiscal year (Fiscal Year 5), create one combined transaction per account per day per department per project. It will still be possible to create statistics for each day based on department and project. 3 Fill in the fields in the window as shown here:

4 For the fiscal year before that one (Fiscal Year 4), create one combined transaction per account per accounting period. It is not necessary to preserve information about departments and projects. From now on, the statistics for this fiscal year can be printed only on the basis of period, without reference to departments and projects.

84

3.6 Database Efficiency

Fill in the window as shown here:

5 For fiscal years that are more than three years old, only one combined entry per account per fiscal year needs to be saved. For the three oldest fiscal years, you will be able to generate statistical information based only on totals for entire years. Fill in the window as shown here:

85

Chapter 3. Working with Databases

3.7 License Files

The Microsoft Dynamics NAV installation comes with a demonstration license file, cronus.flf. The demonstration license file allows you to use the standard Dynamics NAV program as a stand-alone application and gives you access to the demonstration company that is part of the accompanying standard database, database.fdb. To start working with Dynamics NAV, you will need a license file that contains permissions for the desired application areas and functions. This license file will be supplied by your Microsoft Certified Business Solutions Partner. You can use your license file to work in the demonstration company and in your own companies, but your permissions will be limited (even in the demonstration company) to those provided by the license file. Your license file is not subject to the same restrictions as the demonstration license file. These restrictions are listed on page 58. Your license file is always named fin.flf and is uploaded to the server during the server installation. The clients automatically work with the same license file as the server they are connected to.

Importing, Exporting and Changing License Files On the menu bar, click Tools, License Information. The License Information window appears:

The information displayed includes the license number of the current license file, the name of the owner and the functionality that the owner has purchased (along with any expiration dates). If at any time you want information about the current license file, you can open this window. The buttons at the bottom of the window allow you to import and export license files and to temporarily change the license that you are using. The license information that is displayed in this window will always be taken from the license information that is stored on the server, unless you have changed your license temporarily with the Change facility. Importing a License File In the License Information window, click Import, to use a different license file. The Import License File dialog box appears. Locate and select the license file that you want and then click Open. The program will then import the license file into the Dynamics NAV folder on your computer and it will be called fin.flf. The license file will automatically replace any other file called fin.flf without asking you to confirm that you want it to do so.

86

3.7 License Files

This new license file will be the active license file the next time you open Dynamics NAV. When you connect to a server, the license stored there will become the active license. Exporting a License File Click Export to export a copy of your license file, for example, to a disk. The Export License File appears. This is a standard Windows dialog box. Temporarily Changing the License File If, for example, you are a Microsoft Certified Business Solutions Partner representative visiting a customer, you may want to change the license file temporarily. To do so, insert the disk containing the license file and click Change. The Change License File dialog box appears. Select the license file to be read into the system. The information contained in it will be transferred to the client when you click Open. When you access any servers, this temporary license information will continue to be used instead of the license information stored on the servers. The server license will be reinstated when Dynamics NAV is closed and opened again. Dynamics NAV will warn you before your license expires. If you fail to notice the warning and the license on the server expires, you will not be able to access the server. However, you can use the Change facility to gain access to the server by using an alternative license file. When you receive your new license file, you should copy it to the server. Ensuring that You are Using a Valid Dynamics NAV License You may want to verify that you are using a valid Dynamics NAV license that has been issued to your company. To check the validity of your license file: 1 Click Help, About Dynamics NAV to open the About Dynamics NAV window. 2 Click Check your license information and your web browser opens a web page that will help you check the validity of your Dynamics NAV license.

87

Chapter 3. Working with Databases

3.8 Expanding a Working Database

You will need to expand your database from time to time. This might be because your database has grown too big and it no longer has the recommended 20% free space. You might also want to expand your because you want to add an extra hard disk. To expand a working database we recommend that you follow this procedure: 1 Use the backup function in Dynamics NAV to make a complete backup of your database. 2 Make sure that you are the only client connected to the database. 3 Create the new database that you want to restore the backup into. Remember that you cannot restore a backup into a database that contains data. 4 Create all the other database files on the other hard disks. Remember that all the database files must be the same size. 5 Close and reopen the database. This will ensure that the server rebuilds the list of free blocks in the database. 6 Restore the database backup that you created earlier. The database is now spread evenly across all the database files and you will get the best performance from your database.

88

3.9 Advanced Database Information

3.9 Advanced Database Information

In order to understand how a table is optimized in Dynamics NAV, you need to understand how the database is constructed. The next section explains this. In a multiuser installation, Dynamics NAV handles the problem of several users accessing the database concurrently (at the same time) with a technique called optimistic concurrency, which uses the database version principle. Optimistic concurrency and the database version principle are explained on page 91.

Optimizing a Table A database table contains a primary key and several secondary keys. There must be a primary key, and there can be a maximum of 40 keys (both primary and secondary keys) in all. The keys determine how data is sorted.
Keys

The keys are arranged in so-called B+ trees (balanced trees). A balanced tree is one in which the program always passes through the same number of levels to access data at the bottom of the tree, regardless of which branch of the tree the data is located on. A tree data structure is made up of nodes (see the figure on the next page) where each node in the tree, except for a special node called the root, has one parent node and may have one or more child nodes. The root node has no parent. A node that has no child node is called a leaf; a nonleaf node is called an internal node. The level of a node is defined as the level of its parent plus one. The level of the root node is defined as zero. Searching for a record in a B+ tree is very fast because it is not necessary to search the entire tree to find the record.

89

Chapter 3. Working with Databases

The following figure illustrates a B+ tree: Leaf node

Andy John Mark Internal node M Robi Root node

Robert Robin

San Sally Sandy Ti Thomas Timothy

Free block Data is only found in the leaf nodes, not in the internal nodes.The internal nodes and the root node only contain dividers (San, M, Robi and Ti in the diagram) and pointers (arrows in the diagram) to the next nodes in the tree. A divider contains information that separates the data in the levels below it. Depending on whether the value of the data you are searching for in the level below is smaller than or greater than the value in the divider, the search path goes either to the left or to the right (up or down in the figure). For example, consider the search for the name Sandy. Sandy comes after San in alphabetical order, so the search path would go from the root node to the internal node containing the divider labeled Ti. Sandy comes before Ti, so the search would go to the left (up in the diagram) of the divider to the leaf node containing Sandy. One internal node can contain several dividers. This minimizes the number of levels in the tree and ensures that the path to the record is as short as possible and the tree can be said to be balanced. As you insert more data in the tree, the leaf nodes may be only partly filled. When you optimize a table in Dynamics NAV, the leaf nodes are packed together in order to save space in the tree. When more information is inserted, data will be moved to new nodes to make room for the insertion.

90

3.9 Advanced Database Information

How the Database Works What if two or more users are reading the same record at the same time? And what if two or more users working on the same record try to save the record at different points in time? Dynamics NAV uses several strategies to deal with these problems. They are explained in the following sections. Optimistic Concurrency Dynamics NAV uses a technique called optimistic concurrency. With optimistic concurrency, you always have access to the record you want to work with. Thus, if two or more users try to access the database at the same time, they will all be allowed to do so. This is possible because the Dynamics NAV database is based on the databaseversion principle. Every time a user commits something to the database, a new version of the database is created. (A transaction is said to be committed when it is physically written to the database or to commit cache if it is turned on. See the section called "Commit Cache Writing the Cache" on page 39.) When you enter new data, your changes are private. It is not until you commit the changes that the new data becomes public, and the newest version of the database is established. The DBMS (database management system) enables several Dynamics NAV clients to access and modify the database concurrently by letting them work on individual versions, which are merely snapshots of the database at the time when they first accessed it. Read Consistency and Concurrency The following figure shows three Dynamics NAV clients accessing the same database. Imagine that the first access is made by a report. The second access is made by a user who inserts new entries in the database, and the third access is made by a backup procedure. Version A B C D Time

(A) Report User 1 (A) Entry User 2 Backup User 3 (B) (B) (C)

The generation of the report is based on version A of the database. It is a time consuming process, and while the report is being generated, User 2 enters or modifies records in the database. After each entry is committed, a new version of the database is created. These are versions B, C and D. However, a snapshot of the database (version A) was made when the report started, and the report continues to work on version A of the database. User 3 starts a backup procedure. When this process starts, the most recent version of the database is B, created by the completion of the first entry by User 2. A snapshot of this version is made, and this version (B) is backed up. The backup process is unaffected by User 2, who continues to enter new data during the backup

91

Chapter 3. Working with Databases

process. This example shows that working with data versions makes it possible for many users to access the database without interfering with each other. If, however, two or more users access the same record at the same time the user who first tries to write the changes to the record will be allowed to do so. The other user(s) will receive the following message from the system when they try to commit their changes to the database (if they are trying to modify customer number 10000):

In this case, the user has to repeat his or her work using a new snapshot of the latest (modified) version of the database. The implications of the database-version principle approach are many; most important is that different Dynamics NAV clients may read different versions of the same database. These versions are snapshots of the database at the point in time when the clients start to access the database. In this way, the DBMS allows for concurrency (that is, for more than one user to have access to the database at the same time) while still maintaining read consistency. If the accesses to the database involve only data retrieval and no changes, then the newest version will persist for all clients until a write transaction is performed. Database Versions The following figure illustrates the concept of database versions. The data in the Dynamics NAV database is stored in the data structure mentioned previously, the B+ tree. Imagine that the tree structure in our database contains a branch with customers A, B and C. Furthermore, there are two free database blocks available. Assume that you need to modify customers A and C. When you modify the records, the DBMS makes a copy of the original customers A and C from database version 1. These copies use two

92

3.9 Advanced Database Information

free database blocks. You then perform your modification on the copies (they are now named A1 and C1), and the system creates a new internal node. Data Versions Database Version 1

C Free

Free

Database Version 2

C A1

C1

If an error occurs during the transaction, or the user decides to abort the changes, the database blocks occupied by the copied branch will be released and be available for new database updates. If the transaction is committed, this new internal node will replace the old node, and the database blocks used by the old versions of customer A and C will now be available as free database blocks which can be used by database updates. Now, the newest database version is version 2 in the figure.

93

Chapter 3. Working with Databases

3.10 Setting up Outlook Integration

Outlook Integration allows you to synchronize items in Microsoft Outlook with records in Microsoft Dynamics NAV. In Dynamics NAV, synchronization applies to contacts and to-dos of different types such as salespeople or purchasers. These records can be synchronized with items in Outlook such as contacts, appointments or tasks. See Installing Outlook Integration on page 25 for more information on Outlook Integration.

Setting Up Synchronization in Dynamics NAV Before configuring the synchronization toolbar in Outlook, entities (items for synchronization) must be setup in Dynamics NAV. This task should be carried out by a Dynamics NAV administrator or super user. 1 Firstly open the SQL Server option for Microsoft Dynamics NAV 2 Click the Administration button on the Navigation pane and open the Application Setup Folder. 3 Click on the Microsoft Office Outlook Integration Folder and open the Outlook Synch. User Setup window. Outlook Synch. User Setup window:

In the Outlook Synch. User Setup window enter your User ID and Sync Entity Code, the remaining fields are completed automatically. 4 In the User ID field click the AssistButton p to see the Logins window:

94

3.10 Setting up Outlook Integration

If you are using Windows authentication your domain and user name details are completed automatically. Select your user name and click ok. 5 Now select the Synch. Entity Code field and choose which items you want to synchronize with Outlook. Outlook Synch. Entity List window:

Choose the Dynamics NAV entities that you want to synchronize. The following table shows Dynamics NAV synch entity codes and their corresponding Outlook items:
Synch Entity Code APP CONT_COMP CONT_PERS CONT_SP TASK Microsoft Dynamics NAV item Meetings Contacts of the Company type Contacts of the Person type Salespeople Tasks/to-dos Corresponding Outlook item Calendar appointments/meetings Contacts Contacts Contacts Tasks

6 Select a synch entity code, for example APP. The other fields in the User Setup window are completed automatically on selection of a synch entity code. 7 When you have completed set up of the first Dynamics NAV entity that you wish to synchronize, click Setup and Register in Change log setup in the drop down menu (Outlook Synch. Change Log Set. window). If your Dynamics NAV entities have been set up correctly a pop-up message appears confirming that the change log settings have been registered successfully.

95

Chapter 3. Working with Databases

These steps should be repeated for each Dynamics NAV entity that you want to synchronize with Outlook until the Outlook Synch. User Setup window looks something like this:

Note

After setting up synchronization items in Dynamics NAV, you should then choose which folders in Outlook you want to store your synchronized items. This should be done as part of the configuration and setup of the Synchronization toolbar. See the next section for further details: Setup and configuration of the Synchronization toolbar.

Setup and Configuration of the Synchronization Toolbar After you have installed the Outlook add-in a Synchronization toolbar appears in your Outlook client. This section looks at configuration options available from the buttons on the Synchronization toolbar: Settings Troubleshooting Synchronize Connection State The Dynamics NAV Synchronization Toolbar You can use this to set synchronization options and resolve conflicts. The Synchronization toolbar:

The Settings Window The Settings window allows you to select a number of different options before running synchronization. It contains the following five tabs: General Connection Folders

96

3.10 Setting up Outlook Integration

Filters Customize The General Tab

The General tab is used to set the primary synchronization options which are divided into two main areas: Synchronization process Synchronization conflicts resolution.
Synchronization process

There are three options here that can be chosen by selecting the appropriate check box: Schedule automatic synchronization: Select this option to decide how often synchronization should run. You can insert a value in the text box to determine how often synchronization should take place. When Outlook starts, synchronization starts automatically if this value is set. Show synchronization progress: Select this to display the Synchronization Progress window. Show synchronization summary: Select this to display synchronization statistics. A synchronization summary is displayed after synchronization.

Synchronization conflicts resolution

These settings make it easier to solve synchronization conflicts before they occur. Only one option can be chosen at a time by selecting the appropriate radio button. When a synchronization conflict occurs you can choose to carry out one of the following actions: Replace all Outlook items with Dynamics NAV records Replace all Dynamics NAV records with Outlook items Automatically replace older entities with newer ones Log all conflicts that occur in the Troubleshooting window (for later manual resolution)

97

Chapter 3. Working with Databases

The Connection Tab

The Connection tab is for setting up a new server connection between Outlook and Dynamics NAV. There are three types of server information you need to provide; Company name, Server type and Connection type.
Company Name

Enter the name of your Dynamics NAV company here: e.g. CRONUS International Ltd.

Server type

Select the server type that you want Dynamics NAV and Outlook to communicate with. Choose from the following: C/SIDE Database Server for Microsoft Dynamics NAV Microsoft SQL Server

Connection type

This area allows you to select the type of transport for the server that you have selected in the Server type area. The Connection type area settings are dependent on which server you have selected. C/FRONT If you have selected the C/SIDE Database Server as your server type, you can use the Connection type area to adjust your C/FRONT.NET settings. If you are using C/FRONT.NET, you must specify the name of the server that you want to connect to. Select this from the drop-down list. You must also import a Dynamics NAV license. Click Import to locate your license file. If you have selected Microsoft SQL Server as your server type, you must select a server name and a Dynamics NAV database name in the Connection type area. Use the dropdown list to make your choice.

98

3.10 Setting up Outlook Integration

Note

After you have provided all the required connection information, click Test Connection. If the connection fails, synchronization does not happen. Further configuration, such as setting filters and folders, is not possible until the correct information is provided. The Folders Tab It is very important to specify folders when synchronizing Outlook items with Dynamics NAV records. Synchronization does not function correctly without firstly specifying a location to store all your synchronized items. The controls on this window are added dynamically, but only if synchronization has already been set up in Dynamics NAV. One folder should be specified for every synchronization item. For example, you could create folders for Salespeople, Meetings and Tasks. Folders can be created in Outlook to correspond with each synchronization entity in Dynamics NAV. These can be created by clicking Browse, New on the Folders tab. The Folders tab:

Note

Specifying folders is crucial. Without them synchronization will not work. The Filters Tab Filters are used to reduce the number of Outlook items synchronized with Dynamics NAV items. If a filter is applied on an item then that item is not synchronized. For example, you might want to prevent private contacts from appearing in Dynamics NAV. The items to be filtered are based on the folders selected in the Folders tab.

99

Chapter 3. Working with Databases

Each filtered item has a filter criteria applied to it. These filter criteria can be edited in the Filter window by clicking the Edit button on the Filters tab. If an item matches the Filter criteria set in the Filter window then it is not synchronized. In the Filter window you can define new filter criteria and remove old filters. The Filters tab:

The Edit button allows filter criteria to be set in the Filter window:

Defined Filter criteria This is where defined filter criteria is displayed. You can also remove unwanted filters

from here.

Filter criterion

Set filter criteria here by selecting a field name, condition and value from the dropdown menus. Click Add to List to see your selection added to the Defined Filter criteria list.

100

3.10 Setting up Outlook Integration

The following data type values can be selected from the drop-down menus when defining filter criteria:
String Boolean Date Numeric Is, Is not, does not contain, contains, is empty, is not empty equals, not equal to on, on or after, on or before equals, not equal to, is at most, is at least, is more than, is less than

Enumeration equals, not equal, exists, does not exist

The Customize Tab The Customize tab controls how the synchronization toolbar is displayed. Synchronize, Troubleshooting and Connection State are selected here by default but Settings cannot be selected as it must always be visible on the toolbar. Full synchronization is a another option that can be added to the toolbar but this is not selected by default. If the Customize option is not used the default toolbar displays the standard options; Synchronize, Settings, Troubleshooting and Connection State. The Troubleshooting Window If errors or conflicts occur during the synchronization process these are displayed as a list in the Troubleshooting window in either the Errors or the Conflicts tabs. Errors tab - A list of all the errors that have occurred. There can be several errors displayed here for the same Outlook item. Conflicts tab - There is only ever one conflict per Outlook item so only one entry can be shown at a time. Every time a conflict occurs the conflict list is updated. The Troubleshooting button (on the Synchronization toolbar in Dynamics NAV) has two states. These are displayed in different colors: White - No errors or conflicts have been logged or Green if it has been disabled. Red - At least one conflict or error has been logged. The Errors tab The Errors tab displays all errors; synchronization and technical Technical errors- For example, connection problems. Contact the system administrator to resolve these kind of errors (they do not relate to the business logic of synchronization between Outlook and Dynamics NAV items). Synchronization errors - For example, trying to perform synchronization without specifying a synchronization folder first. These type of errors can be manually corrected. The following is a list of fields displayed in error records: Occurrence Time - displays the time when the synchronization error occurred Description - contains a brief description of the error

101

Chapter 3. Working with Databases

Outlook Item Type - shows the type of Outlook item Outlook Entry ID - displays the item ID Microsoft Dynamics NAV Entity Type - shows the type of Dynamics NAV entity Microsoft Dynamics NAV Record No - shows the Dynamics NAV record ID After correcting an error delete the error record manually by clicking the Delete button on the Errors tab. The Delete All button allows you to delete all the records in the Error log. You are asked to confirm your intention when you delete an error, click OK to confirm your choice. The Conflicts Tab The Conflicts tab contains entities from both the Outlook and the Dynamics NAV side that have been modified after running synchronization. These conflicts cannot be resolved automatically by rerunning synchronization. Conflicts here should be resolved manually by deciding which information is more valuable.
Note

A record of synchronization conflicts is only displayed in the Conflicts tab if the Log Conflicts option (default option) has already been selected on the General tab of the Settings window. If any other option for conflict resolution has been selected then the conflict is resolved automatically according to the options chosen at the time. Drop-down menu items in the Conflicts tab: Replace Outlook item - Replace the Outlook item with the corresponding Dynamics NAV record Replace All Outlook items - All Outlook Items are replaced with Dynamics NAV records Replace Dynamics NAV record - Replace the Dynamics NAV record with the corresponding Outlook item Replace All Dynamics NAV records - All Dynamics NAV records are replaced with Outlook items Delete - Delete the selected conflict Delete All - Delete all conflicts Refresh - Checks whether conflicts are still unresolved. If a conflict has been resolved it is removed from the list automatically. Apply to all - This allows you to apply changes to all conflict records. The Conflict Details window appears when a row in the Conflicts window is double clicked. This window allows you to compare field values in Dynamics NAV and Outlook records making it easier to decide which value should be replaced.

102

3.10 Setting up Outlook Integration

The Connection State button This displays a pop-up message with connection state information. If synchronization has been set up correctly on your computer the following window will appear:

The Synchronization Progress Window The Synchronization Progress window is rather similar to the Send/Receive window in Outlook. It shows the current status of the synchronization process. You see it when the Synchronize button is activated. The Synchronization Progress window:

It only appears if Show Synchronization Progress has already been selected in the Settings window. If you have set Schedule Automatic Synchronization every ... mins on the General tab then the Synchronization Progress window is not shown. If you click the Synchronize button while synchronization is already running in the background then the Synchronization progress window appears displaying the current status of the synchronization process. In the Synchronization Progress window the details of synchronization can be shown or hidden by clicking on the Details button. Details include the following: Status of the synchronization process Synchronization of Outlook and Dynamics NAV items Synchronization finalization On completion of synchronization a summary of the performed actions is displayed in the Synchronization Progress window. This is only shown if Show Synchronization Summary has already been selected in the Settings window. Removing the Outlook Add-in The procedure for removing Outlook Synchronization is the same as for any other Windows program. Simply go to Control Panel, Add and Remove Programs and remove the Microsoft Dynamics NAV Add-in program.

103

Chapter 3. Working with Databases

Upgrading from Navision 4.0 to Microsoft Dynamics NAV 5.0 The following table outlines the main differences in functionality between Outlook Integration for Navision 4.0 and Dynamics NAV 5.0:
Navision 4.0 Event based synchronization. Synchronization only takes place if an item has been changed. Limited options available when resolving errors or synchronization conflicts Limited customization options Dynamics NAV 5.0 Synchronization can be based on periodic requests (e.g. every 60 minutes) or on user demand Conflicts and errors can be automatically or manually resolved from either the Outlook or Dynamics NAV side. Highly customizable from Outlook or Dynamics NAV side particularly when deciding which items should be synchronized.

It is not possible to choose which Outlook items should Filters make it possible to choose which be synchronized Outlook items take part in synchronization. It is not possible to choose which Navision items should take part in synchronization. Contacts in Navision 4.0 can only be synchronized according to their corresponding Salesperson Code It is easier to choose which Dynamics NAV records take part in synchronization. Synchronization is based on user ID and settings made during synchronization setup. Contacts in Dynamics NAV are no longer just referenced by their salesperson code but can also be chosen according to other criteria such as area code or correspondence type. It is possible to synchronize entities without any dependencies e.g. only contacts or only customers However, if an entity has dependencies then those dependencies must also be synchronized (e.g. a to-do may have a contact assigned). Use the standard Dynamics NAV Synchronization toolbar installed with Dynamics NAV Synchronization add-in. Use Synchronization window summary instead to see how many items were synchronized, created, modified and deleted. All fields must map to individual fields. In order to synchronize an additional field, it should be mapped to another field in the mapping schema.

It is not possible to synchronize entities with dependencies

You cannot create your own customized tool bar

Emails and appointment invitations can be sent to notify users about changes after synchronization

Many to one and one to many field mapping was possible between and Navision and Outlook entities

104

3.10 Setting up Outlook Integration

It was possible to review details of all synchronized items from the Outlook window and vice-versa

It is no longer possible to review the details of synchronized items and entries in this way.

105

Chapter 3. Working with Databases

3.11 Standby and Hibernation

Microsoft Dynamics NAV supports the standby and hibernation facilities provided by Windows. Putting your computer on standby means that the entire computer switches to a low power state. When on standby, all devices, such as the monitor and hard disks, turn off and your computer uses less power. When you want to use the computer again, it comes out of standby quickly, and your desktop is restored exactly as you left it. Standby is particularly useful for conserving battery power on portable computers. Because standby does not save your desktop state to disk, a power failure while on standby can cause unsaved information to be lost. Putting your computer in hibernation means that before shutting down your computer saves everything that is currently in memory to disk, turns off your monitor and hard disk, and then turns off your computer. When you reactivate your computer, your desktop is restored exactly as you left it. It takes longer to bring your computer out of hibernation than out of standby.
Shutting down

Individual workstations can go to standby or hibernate after being idle for a certain length of time. It is also possible to force the computer to go to standby from the Windows Shut Down dialog box. However, Dynamics NAV will not allow Windows to go into hibernation or standby in the following situations: Carrying out a transaction, for example, posting an order Printing a report Making a backup If you attempt to make the computer go to standby or hibernation from the Windows Shut Down dialog box during any of these situations, a window will appear informing you that Dynamics NAV is busy and that shutting down is not yet possible. When you click Cancel in this window, the hibernation or standby procedure will be postponed. If you ignore this window, the computer will go into hibernation or standby when Dynamics NAV has completed its task.

Restarting

When you restart your computer after it has gone to standby or is in hibernation, it will restart with the desktop exactly as it was when you left it, and you will see the same Dynamics NAV windows that were open. However the information displayed in these windows will also be the same as before and is therefore not necessarily up to date. The window will not be updated until you use the program and actively update the window in question.

Using a laptop

If you are using a laptop computer and close the lid, Windows will shut down. However, an active Dynamics NAV client will force Windows to wait until the operation it is carrying out is finished before shutting down. When the user reactivates Windows, the Dynamics NAV client will be exactly as it was when you left it.

106

3.12 License Agreement Setup

3.12 License Agreement Setup

When customers use Microsoft Dynamics NAV for the first time, they are required to accept an electronic version of the license agreement. It uses the following standard license agreements: EULA - End User License Agreement IPLA - International Product License Agreement The effective date of the license agreement can only be set or amended by a Microsoft Certified Business Solutions Partner or Dynamics NAV administrator. The effective date should be set to start after installation and configuration of Dynamics NAV is complete. The first user to access the product after the specified date must then accept or reject the license agreement. Acceptance of the license agreement should be the final step before the product is released to the customer. However, if after setting the license agreement date further changes to the configuration are needed then this date can be changed again.
Summary of steps

A Microsoft Certified Business Solutions Partner installs and configures Dynamics NAV and then sets the effective date of the license agreement. The first user to access the system after this date is presented with a license agreement dialog box. The user can choose to accept the license agreement by clicking Accept or reject it by clicking Close, to cancel. If cancel is selected then the next user to access the system is asked to accept and so on until the license agreement is finally accepted.
Note

Delaying acceptance of the license agreement or resetting the license agreement date does not affect the duration of the customer license agreement. The aim of this feature is to make the deployment experience as smooth as possible.

Changing the License Agreement Date 1 Open the C/SIDE Client for Microsoft Dynamics NAV. 2 Open the Object Designer. 3 Run the License Agreement Setup Card (Form 180).

107

Chapter 3. Working with Databases

License Agreement Set Up Card:

4 Enter new (correct) license agreement date in the Effective Date field. 5 Add some text to the Message for Accepting field. 6 Close the object designer and C/SIDE Client.

First user experience The first user to start Dynamics NAV after the license agreement date has been reset is presented with a dialog box asking if they are willing to accept the EULA license agreement:

The dialog contains a link to the full text of the license agreement. If the user wishes to read this, they can do so by clicking on the link. If the user wishes to accept the license agreement, they must click the Accepted check box and then click the Accept button. Clicking to Accept the license agreement means that Dynamics NAV opens as normal. If Close is selected the program closes and the next user is asked the same question until the license agreement is finally accepted.

108

Chapter 4 Security
This chapter explains how the security system used by Microsoft Dynamics NAV works. It also explains how to set up an effective security system that controls the access that each user has to the program as well as the rights that they have within the program. The chapter contains the following sections: Authentication in Microsoft Dynamics NAV Active Directory and Microsoft Dynamics NAV Security within Microsoft Dynamics NAV Setting Up Logins, Passwords and Permissions Changing Passwords User Time Limits and the Time Register Selecting a Printer

Chapter 4. Security

4.1 Authentication in Microsoft Dynamics NAV

An enterprise business solution must have a built-in security system to ensure that only people with the appropriate authorization can gain access to the information contained in the system. A minimum level of security requires that users be assigned user IDs and passwords, thereby limiting access to the program. Microsoft Dynamics NAV satisfies this requirement by integrating its own security system with the active directory security system and with the single sign-on system. But before explaining how the Microsoft Dynamics NAV security system works it is necessary to clarify some of the concepts that are involved: Authentication: the process by which the system validates the users identity. This can be done having the user enter an ID and password when they log on. Dynamics NAV supports two kinds of authentication: Windows authentication and database server authentication. Login: when a user has identified themselves and been recognized by the system, they are granted access to the parts of the system for which they have permissions. If the user has used Windows authentication to log on to the system, they have been assigned a Windows login. If the user has used Dynamics NAV or database server authentication to log on to the system, they have been assigned a database login.

Windows Security One of the main features of Windows security is the single sign-on system. Dynamics NAV supports this feature and can also use more of the features contained in the Active Directory security system. The Windows single sign-on and the unified login system are the same. In this manual, we will refer to both of these systems as Windows authentication. With the Windows authentication system, Dynamics NAV checks whether the user in question, who has already logged on to the network, is a member of an Active Directory security group or has a valid Windows account. When a user opens Dynamics NAV and tries to connect with a server and open a database using Windows authentication, they will not have to supply a user ID or password. Dynamics NAV will automatically ask Windows to confirm whether or not this user, who has already logged on to the network, has a valid Windows account and whether this account gives them the right to access this particular server. If the user is allowed to access the server, then Dynamics NAV will check to see if the user has been assigned a Windows login within Dynamics NAV. If the user has a Windows login, they will be granted access to the database. The user will be granted access to Dynamics NAV and be given the permissions specified for that Windows user and those specified for any Windows groups of which they are a member. The user will also be granted any other specific permissions that they have been granted within Dynamics NAV. If the user does not have a valid Windows account, or if their account does not include permission to log on to server

110

4.1 Authentication in Microsoft Dynamics NAV

on which C/SIDE Database Server is running, authentication fails and the user receives an error message.

Database Server Authentication If the server does not support Windows authentication, then database server authentication must be used. It is also used when the network administrator has chosen not to use Windows authentication. The Dynamics NAV administrator decides which kind of authentication each individual user should use by assigning each user or group a Windows login or a database login. If the Dynamics NAV administrator has decided to use database server authentication, they must assign each user a database login. This entails creating a user ID and password for the user within Dynamics NAV. The user will have to enter this user ID and password when they try to access a database. The user ID and password must be created by a system administrator, superuser or somebody else with permission to create Dynamics NAV users. If the user has a valid user ID and supplies the correct password, access will be granted to the relevant areas of the system. If the user ID does not exist or if the password supplied by the user is not valid then authentication fails and the user receives an error message.

Active Directory Service Security The Active Directory Service gives Dynamics NAV several new security features. These include allowing administrators to: grant or deny users access to Dynamics NAV by simply adding them to or deleting them from a Windows security group. grant other people in the organization, for example heads of departments, the power to create and administer users and groups. Active Directory Security also supports Windows authentication and provides you with: secure validation and encryption of passwords. a time limit on passwords. minimum password length. account lockout after an invalid password is entered.

111

Chapter 4. Security

4.2 Active Directory and Microsoft Dynamics NAV

Active Directory makes Microsoft Dynamics NAV even more flexible and easier to administer. To take full advantage of features provided by Active Directory, the domain controller must be running on Windows 2000 Server or on Windows Server 2003 and the clients must be running on Windows XP or Windows Vista or have been Active Directory enabled. The features that will not be available are the Windows Users and Groups window (see page 115) and the Available C/SIDE Database Server window (see the chapter called "Working with Databases"). Active Directory allows the administrator to give administrative permissions to other users, thereby delegating large areas of responsibility to other members of the organization. Others users, for example department managers, can administer all the groups that they need within their department from the Microsoft Management Console. This allows them to make Windows users members of specific security groups that have been given roles within Dynamics NAV. They can control access to and permissions within Dynamics NAV without having to open Dynamics NAV, provided that the Windows security groups have been given the appropriate roles within Dynamics NAV. Dynamics NAV administrators can also manage database security for Windows logins from within Dynamics NAV without having to use the Microsoft Management Console. Dynamics NAV also allows you to create Dynamics NAV users, give them roles and modify the rights of these users and roles from within Dynamics NAV. All the Active Directory security groups will be visible within Dynamics NAV. It is possible to give these Active Directory groups roles within Dynamics NAV.

112

4.3 Security within Microsoft Dynamics NAV

4.3 Security within Microsoft Dynamics NAV

Microsoft Dynamics NAV allows you to control the access that individual users have to the information contained in the database. You do this by giving the users roles within the database and granting sets of permissions to these roles and to the individual users. In this way, users have access to only those areas of the program for which they have been granted permissions. The database that comes with the program includes a number of predefined roles. (See the list later in this chapter.) You can use the roles as they are, change them or create new ones. Dynamics NAV allows you to create two different kinds of login database logins and Windows logins.

Database Logins If you are using database server authentication to control access to the system, you can choose the level of security that you want to use: user permissions, user IDs and passwords, or no user IDs. The ways in which Dynamics NAV user IDs can improve security are described in the following section.
Time-limited permissions

Passwords in Dynamics NAV do not have time limits, but you can put time limits on user IDs. If you yourself have the required permissions, you can always delete a user ID from the system or cancel all its permissions. If this is too drastic, you can specify a limited time period in which a particular user ID is allowed to post in the system. You set up this limitation under General Ledger, Setup, Users as explained on page 126 in this chapter. Under General Ledger, Setup, Users, User Setup, you can specify that you want the program to register the amount of time each user works with a company. This can be used, for example, by accountants who post for others, to document the amount of time spent working on the accounts of the various companies. To see the time use that has been registered, click General Ledger, Setup, Users, User Time Registers. The User Setup table is described on page 125 and the User Time Register table on page 126. User IDs can be used to determine which printer an individual user will be connected to. You can set this up under General Ledger, Setup, Printer Selections. You can read more about this on page 128.

Registering time use

Default and fixed printer selections

User IDs on all entries All G/L entries and most other entries in Dynamics NAV contain a field displaying the

user ID of the user who made the entry.

Identifying individual The current user ID always appears on the status bar at the bottom of the program system setups window. If you save individual setup files for different users, it can be helpful to use the

user ID as the setup ID. This is the only way that you will be able to see in the window which setup file has been used to start the program.

If you are using Windows XP, you will only have to set up user IDs if users are using the same Windows account, because Windows XP store each users individual setup file in their Windows account directory. You can read more about setup files on page 35.

113

Chapter 4. Security

4.4 Setting Up Logins, Passwords and Permissions

The Microsoft Dynamics NAV security system is company specific and contains information about the permissions that have been granted to each individual user with access to each particular company. This includes information about what roles the users have been given as well as any particular rights that they have been granted as individual users. In order to create Dynamics NAV users, you must give them an identity within the database that allows them to log on to the system. When the user has logged on to the database, they are able to perform tasks in accordance with the permissions that they have been allocated.
Initiating the security The Dynamics NAV security system is initiated when you create the first login this can system be a Windows login or a Database login. You should assign this login to a superuser.

The superuser then owns and administers all access to this database from within Dynamics NAV. Until you create a superuser, any user with access to the system can carry out any transactions that they want to in a Dynamics NAV database. One of the first things that the superuser should do is create user IDs for the other people who will have access to the database and assign roles to these users. Permissions are allocated at company level in Dynamics NAV.

Who can grant permissions in Dynamics NAV?

Dynamics NAV only allows specific users to administer security and grant permissions. Only users who have been given the Super and Security roles are allowed to administer security. These Dynamics NAV users can only grant permissions to other users that they themselves possess.

Creating Logins In order to add new users to the system, you must create a database login or a Windows login for them. Creating a Database Login Creating a database login involves giving the new user a user ID and one or more roles that contain the permissions that are appropriate to their position within your organization. To create a database login, click Tools, Security, Database Logins on the menu bar. The Database Logins window appears:

114

4.4 Setting Up Logins, Passwords and Permissions

To initiate the security system, you must start by creating a login for a superuser. To do this you must set up the user ID of a superuser who has permission to perform everything that is possible in the entire program. The following example illustrates how to set up such a superuser. You can use the same procedure to create the database logins for the other users. To create a database login for a superuser: 1 Open the Database Logins window. 2 In the User ID field, enter the user ID of one of the people who will administer this database, in this case SUPERUSER. You can type uppercase and lowercase letters as you like the program will convert all letters to uppercase. You can change the user ID in this field at a later time. 3 In the Name field, enter the name of the user to whom this ID belongs. 4 If you want to be able to use database server authentication you must enter a password. It is encrypted as you type, so neither you nor anyone else can see it. A Dynamics NAV password can contain a maximum of 10 characters. It is important to remember where you have used uppercase and lowercase letters because passwords are case-sensitive. The password can be used for as long as you want. In a multiuser installation, however, where a system manager has set up all the user IDs, each user should change their own password immediately after logging on for the first time so that no one else knows their password. It cannot be seen anywhere in the system. If you set up passwords for other users, remember to tell them that passwords are case-sensitive. Users do not need passwords if they are going to use the unified login supported by Windows servers. 5 In the Expiration Date field, you can enter a final date on which a user will be able to log on to the program. As a security precaution, superusers should not be given a date limitation. Giving the Superuser a Role You must grant the SUPER permissions to your superuser before you grant permissions to any other users. Dynamics NAV requires that at least one user is assigned this role in each database. You grant permissions to users by giving them roles or by granting them specific permissions.
Assigning roles

In the Database Logins window, make sure that the current record symbol t on the left side of the window is next to the login of the superuser that you have just created

115

Chapter 4. Security

and click Roles at the bottom of the window. The SUPERUSER - Roles window appears:

This window lists the roles that this user has been given, but it is empty now because you have not yet given this superuser a role. To see a list of the roles that have been set up, click the AssistButton at the right of the Role ID field. The Roles window appears:

If you have not changed them, these will be the standard roles that come with the program. You must give the superuser the role named SUPER:
SUPER Read, use, change and delete all data and all application objects (if you have purchased a license to do so).

To add the role to the SUPERUSER Roles window, scroll down to the line containing the desired role and double-click it or select it and click OK. As a default, permissions apply to all the companies in the database, but they can be restricted to a particular company. To do this, enter the name of the company (or use the AssistButton) in the Company field on the right side of the window. For permissions to apply to several companies, you must set up one line per company (each line starting with the same role ID). If you specify that the permissions a user has only apply to a particular company in the database, the user in question will only be able to see that company.

116

4.4 Setting Up Logins, Passwords and Permissions

Note

The standard roles come with the standard database. When you create a new database, the roles will be copied into it when you make a backup of Data Common to All Companies and Application Objects in the old database and restore them into the new database. Creating a Windows Login It is also possible to create a Windows logins for a Windows user or group that allows them to access the system. To create a Windows login: 1 Click Tools, Security, Windows Logins to open the Windows Logins window. 2 In the ID field, click the AssistButton to open the Windows Users & Groups window:

This window lists all of the Windows users and groups that are available in the current forest of domains and domain trees. This window is only available if both the domain controller is running on Windows Server 2003 and the clients are running on Windows XP or have been Active Directory enabled. However, if you are running a Windows NT network, you can type in the names of the Windows users and groups in the Windows Logins window. Remember to use the Domainname\Username format. 3 Select the Windows user or group for which you want to create a Windows login. 4 Click OK and the Windows user or group will be added to the Windows Logins window. You have created a Windows login and can now give it a role within Dynamics NAV.

Roles and Permissions Before granting permissions to the users, you should look at the standard roles that come with Dynamics NAV. You can use the roles as they are, you can modify them, or you can set up completely different ones.

117

Chapter 4. Security

Each role describes a set of access permissions to tables, reports, functions, and so on. Various permission types allow the user to: Read (information in a table, for example) Insert (information in a table, for example) Modify (information in a table, for example) Delete (information in a table, for example) Execute (functions or reports, for example) You can give each user one or more roles as needed by following the procedure described above. There is no point in granting permissions to areas that your license file does not permit you to use. However, granting such permissions does not cause any problems. If you have the program customized or purchase additional application areas, however, remember to change or add to the permissions.
Permissions and FlowFields

Furthermore, in Dynamics NAV a table can contain a FlowField that generates sums based on values that are stored in another table. In this case, the user must have permission to read both tables or they will not be allowed to read the first table.

Creating a Dynamics NAV Role If the existing roles do not meet the needs of your organization, you can always create new ones. To create a new role: 1 Click Tools, Security, Roles. The Roles window appears. 2 Click Edit, Insert New (or use F3) to get an empty line on which to create the new role. 3 Enter an ID for the role in the Role ID field and a description of it in the Name field. 4 Press Enter or click the next line to accept the new role. Then click the new role again. 5 Click Role, Permissions. The Permissions window for this new role appears. See the picture on page 121. Because this is a new role, the window will be empty. 6 In the Permissions window, you can use the AssistButtons to select the type of object that you want to grant permission for and then the specific instance of that object. Enter Yes under the permissions you want to assign to the role, or select Yes with the help of the AssistButton to the right of the field. These permissions will then be granted to the new role. 7 Alternatively, if you want to grant the role extensive permissions, you can click All Objects at the bottom of the window. A list of all the objects in the application appears. Enter Yes under the permissions you want to give the role, or select Yes with the help of the AssistButton to the right of the field. When you click OK in the Permissions (All Objects) window (see page 122), the lines marked Yes will be copied to the Permissions window for this role, where you will subsequently be able to see them.

118

4.4 Setting Up Logins, Passwords and Permissions

Giving a Database Login a Role To see which users or logins have been given a particular role, click Tools, Security, Roles to open the Roles window. Select the role you are interested in and click Role, Database Logins. The following window appears listing the database logins that have been given this role in the database:

If you have already set up the database logins and user IDs, you can easily give a number of new users this role. To do this, you must be a superuser or at least have the permissions you want to give to others, as well as access to security. Click the AssistButton in the User ID field and select the user in the Database Logins window that appears and click OK. You have to add each user individually. This window is the same as the one that appears when you click Tools, Security, Database logins. It is described on page 114. Giving a Windows Login a Role To see the Windows logins that have been given a particular role in Dynamics NAV, open the Roles window and select the role you are interested in and click Role, Windows Logins. The following window appears listing the Windows logins that have been given this role in the database:

To give a new Windows login this role, click the AssistButton in the Object ID field and the Windows Logins window that appears. Select the Windows login that you want to give this role to and click OK. Modifying the Permissions Granted to Dynamics NAV Roles To view, modify, create or delete permissions for existing Dynamics NAV roles, click Tools, Security, Roles on the menu bar. The Roles window appears. It lists the IDs and

119

Chapter 4. Security

names of all the Dynamics NAV roles:

For detailed information about the permissions that have been granted to each role, select the role (ALL is selected in the picture) and click Role, Permissions. Some of the special roles are described in the following table:
Group SUPER Permissions This role can read, use, change and delete all data and all application objects (that your license permits). Dynamics NAV requires that at least one user is assigned this role in each database. You cannot alter the permissions that have been granted to this role. This role can read, use, change and delete all data. This is a role that you will normally assign to an accounting manager or another person who can work with all the data but does not need to make changes in the program. This role has access to the tables and functions related to security information (users, permissions and passwords). Users who have been given this role can grant permissions to others, but they can only grant those permissions they themselves have. Therefore if you want to create an "area superuser," you should give that person the SECURITY role plus permissions for the areas (such as Purchases & Payables) in which they can grant and revoke permissions for other users. This allows them to create new logins and to grant and revoke permissions for other users within the area of Purchases & Payables. This role can use fundamental (but not high-security) tables and functions. Assign this role to all users (except SUPERUSER), because this is a prerequisite for all other roles you will assign to them.

SUPER (DATA)

SECURITY

ALL

Modifying permissions for individual objects

To modify a role, open the Roles window and select the role (there should be a t to the left of the line). Click Role, and then click Permissions. The Permissions window

120

4.4 Setting Up Logins, Passwords and Permissions

appears. This window allows you to see which permissions are granted to each role. The following window is for the role ALL (All users):

Each line represents an object (table, report, form, dataport, codeunit, system and so on) in Dynamics NAV. You can modify, delete or insert lines. In the Object Type field, you can click the AssistButton to view or select the types of objects to which you can grant permissions. In the Object ID field, use the AssistButton to select the object that you want to grant permission to. The Object Name field is filled in automatically when you select an object ID. There are five permissions fields where you can see whether the role has permission to read, insert, modify, delete or execute for the table, report, and so on. The following options appear in the permissions fields:
Permission Yes Indirect Meaning This permission is granted and you have full access to this object. You can always, for example, read this object. This permission is granted indirectly. An indirect permission allows you to, for example, read table data via another object that you have permission to use, such as, a codeunit or a form. Example: You have permission to run Codeunit 80, Sales-Post. The Sales-Post codeunit performs many tasks. One of these is to modify Table 39, Purchase Line. When you run the Sales-Post codeunit, Dynamics NAV checks whether or not you have permission to modify the Purchase Line table. If you do not have permission to modify the Purchase Line table, the codeunit will not be able to complete its tasks and you will receive an error message. If you have permission to modify the Purchase Line table, the codeunit will run successfully. However, you do not need to have full access to the Purchase Line table in order to run the codeunit. If you have indirect permission to modify the table data in the Purchase Line table, the Sales-Post codeunit will run successfully. When you have indirect permission, you can only modify the Purchase Line table when you run the Sales-Post codeunit or another object that has permission to modify the Purchase Line table. Not selected (the field is empty) and you do not have this permission.

121

Chapter 4. Security

Modifying permissions for multiple objects

You can also grant permissions for multiple objects to a role. This is a useful time saving feature if you want to radically modify the permissions that apply to a role. To see all the objects for which you can grant permissions, click All Objects. The Permissions (All Objects) window appears:

Enter Yes in the fields for the permissions that you want to add. (When you return to the window containing the list of permissions, it will include all of the items for which you entered Yes.) Click OK to save your selection.

Additional Security Features Provided by Active Directory Active Directory allows you to give Windows users and groups roles within Dynamics NAV. You will also be able to make Dynamics NAV roles members of Windows security groups. This can only be done from within Dynamics NAV and the individual permissions that are granted to the roles can only be administered from within Dynamics NAV. Giving Windows Users and Groups a Dynamics NAV Role Active Directory allows you to give Windows users and groups a Dynamics NAV role. To give a role to Windows user or group: 1 Click Tools, Security, Roles on the menu bar to open the Roles window. 2 Select the Dynamics NAV role you want to modify and click Role, Windows Logins and the Windows Logins window for this role appears:

122

4.4 Setting Up Logins, Passwords and Permissions

This window lists all the Windows users and groups that have already been given this role in Dynamics NAV. To add a Windows user or group to the list, select an empty row or create one by clicking Edit, Insert New (or use F3). 3 Click the AssistButton in the Login ID field. The Windows Logins window appears:

This window contains a list of all the Windows users and groups that can log on to Dynamics NAV. 4 Select the Windows user or group that you want to give this Dynamics NAV role to and click OK. This user or group will now be added to the list shown in the Windows Logins window for this role. Adding Dynamics NAV Roles to a Windows Security Group Active Directory also allows you to make Dynamics NAV logins and roles members of Windows security groups. Click Tools, Security, Windows Logins to open the Windows Logins window. This window lists all the of the Windows users and groups that can currently access the system. Select the Windows login to which you want to add a Dynamics NAV role. Click Roles and select the relevant role from the Roles window that appears. This role and all the individual users that have been given this role will now be added to the Windows login that you selected earlier.

123

Chapter 4. Security

4.5 Changing Passwords

If you work in a multiuser installation and have been given your user ID and password by the system manager, it is a good idea to change your password the first time you use the program. That will ensure that you are the only one who knows your password. This is not necessary if you work in a single-user installation and have set up your own user ID.
Note

Passwords in Dynamics NAV do not have time limits. If you want to set time limits for access, you can place an expiration date on the user ID or you can specify an allowed posting period for each user (click General Ledger, Setup, Users, User Setup). To change your program password, click Tools, Security, Password and the Change Password window appears:

The user ID and user name, which appear in the two uppermost fields, cannot be changed here. To change them, click Tools, Security, Users. Enter your current password in the Current Password field (remember to distinguish between uppercase and lowercase letters). Enter your new password in the New Password field. You must then confirm the new password by entering it again in the Reenter New Password field. This verifies that you entered it correctly the first time and that you can remember it. The password will not appear when you enter it, and you cannot see it anywhere else in the program. If a message appears informing that the password is incorrect, there are two possible causes: You typed it wrong the second time try again. The password that you created is not what you think it is. Perhaps you made a typing error the first time, or maybe you used uppercase and lowercase letters differently in the two fields. Enter the password in the New Password field again, and then reenter it again. Click OK if you want to change the password; click Cancel to stop the password from being changed.
If you forget your password or user ID

If you forget your password or user ID, you will be allowed an unlimited number of attempts to enter it. You can also request a new password from a user who has permission to change other peoples passwords.

124

4.6 User Time Limits and the Time Register

4.6 User Time Limits and the Time Register

Microsoft Dynamics NAV allows you to put time limits on user IDs. If you are using Windows authentication, you can also put a time limit on passwords within a Windows Server 2003 network. If you have the required permissions, you can always delete a users ID from the system or cancel all their permissions. Alternatively, you can specify a limited time period during which a particular user ID is allowed to post in the program. After you have created a user ID, you can specify that the user with that ID can post only during certain time periods (for example, June 1 June 15) and that the program must keep track of the amount of time the user has been working in each company. This can be used, for example, by accountants who post for others, to document the amount of time spent working on the accounts of the various companies. The User Setup and User Time Register windows are used for putting time limits on user IDs. They are both found under General Ledger, Setup, Users.

User Setup In the User Setup window, you define when each user will be allowed to post and whether the program will record the amount of time that they were logged on. You can also assign responsibility centers and warehouse locations to the user. Click General Ledger, Setup, Users, User Setup and the User Setup window appears:

Fill in the fields in the User Setup window according to these guidelines:
Field User ID Comments Enter the user ID for which you want to set up conditions. The user must have been set up already. If you cannot remember the user ID, click the AssistButton to the right of the field to see a list of the user IDs that have been set up in the current database. Enter the date on which the user will be allowed to start posting. Enter the last date on which the user will be allowed to post. If you want to register the amount of time a user works on the company, enter a check mark by clicking the field or pressing the spacebar.

Allow Posting From Allow Posting To Register Time

125

Chapter 4. Security

Field Sales Responsibility Center Filter

Comments Enter the code for the responsibility center to which you want to assign the user. Click the AssistButton to the right of the field to see the responsibility centers that have been created. This responsibility center will be the default responsibility center when the user creates new sales documents. The user will only see sales orders that are created from their responsibility center. If you leave this field blank, the default responsibility center in Customer or Company Information (in order of priority) will be used. Enter the code for the responsibility center to which you want to assign the user. Click the AssistButton to the right of the field to see the responsibility centers that have been created. This responsibility center will be the default responsibility center when the user creates new purchase documents. The user will only see purchase orders that are created from their responsibility center. If you leave this field blank, the default responsibility center in Customer or Company Information (in order of priority) will be used. Enter the code for the responsibility center to which you want to assign the user. Click the AssistButton to the right of the field to see the responsibility centers that have been created. This responsibility center will be the default responsibility center when the user creates new service documents. The user will only see service orders that are created from their responsibility center. If you leave this field blank, the default responsibility center in Customer or Company Information (in order of priority) will be used.

Purchase Responsibility Center Filter

Service Responsibility Center Filter

For more information about responsibility centers, see the online Help.
Note

Other fields for posting periods are found under General Ledger, Setup, General Ledger Setup, but those periods refer to the entire company and thus apply to all users. Anything that you enter for a particular user under User Setup will take precedence over the general choices you made under General Ledger, Setup, General Ledger Setup, for that user.

User Time Register If the Register Time field in the User Setup window contains a check mark , the User Time Registers window will contain information about when and how long individual users have been logged on to the company.

126

4.6 User Time Limits and the Time Register

In the Navigation pane, click Administration, IT Administration, Users, Time Registers to open the User Time Registers window:

This window displays the time use registered for a number of users. The lines are generated automatically, but you can also enter information in them. Time use is registered in whole minutes, rounded to the nearest minute. The program creates one line per user, per day. If the same user uses the company more than once on a day, the line displays the total time used on that day. If a user finishes using the company after midnight, the time use will be registered to the date when work began not the date it was completed.
User IDs on all entries All entries in Dynamics NAV contain a field displaying the user ID of the user who made

the entry.

Identifying individual The current user ID always appears on the status bar at the bottom of the program system setups window. If you save individual setup files for different users, it can be helpful to use the

user ID as the setup ID. This is the only way that you will be able to see in the window which setup file has been used to start the program. For more information about setup IDs, see page 35.

127

Chapter 4. Security

4.7 Selecting a Printer

When you want to print from Microsoft Dynamics NAV, you can use the printers you have installed on your computer. The printer that has been designated as the default printer in Windows will be used as the default printer in Dynamics NAV.
Individual printer selection

If you want a particular user to always use a specific printer, or if you want a particular report always printed on the same printer, you can set these options as fixed printer selections. A fixed printer selection will apply no matter what printer selections or other changes have been made in the program. The fixed printer selection does not determine options such as paper format. To select fixed printers, in the Navigation pane, click Administration, IT Administration, General Setup, Printer Selections and the Printer Selections window opens:

Fill in the fields in the Printer Selections window according to these guidelines:
Field User ID Comments Enter the ID of the user for whom the printer selection applies. The user ID must have been created in the User table already. To see a list of all the users, click the AssistButton to the right of the field. If you would like the selection to apply to all users, leave the field blank. Enter the ID of the report to which the printer selection applies. To see a list of all the reports, click the AssistButton to the right of the field. If you would like the selection to apply to all users, leave the field blank. This field is filled in automatically when you enter the report ID. Enter the name of the printer that will be used for both the user ID and the report specified on this line. To see a list of all the available printers, click the AssistButton to the right of the field. The Printers window appears and you can select the printer you want from there.

Report ID

Report Name Printer Name

128

Chapter 5 Making Backups

This chapter contains guidelines for why, when and how to back up your Microsoft Dynamics NAV data. It describes various methods of making backups and the advantages and disadvantages of the various storage media. The chapter contains the following sections: Why, When and How to Make Backups Using the Microsoft Dynamics NAV Backup Function Testing before Using Other Backup Methods Restoring Backups Advanced Backup and Restore Information Server Based Backup

Chapter 5. Making Backups

5.1 Why, When and How to Make Backups

You make backups so that there is always an extra copy of your company data to restore into the application if a problem should arise with the working copy. You should make backups for your own sake, but in most countries/regions it is also a legal requirement. This means that if you upgrade to a new version of Microsoft Dynamics NAV or change the installation in another way, you must still keep at least one copy of your company data in a readable format (and in a safe place). If you upgrade to a new version of the accounting system, it may be necessary to save the old system in order to be able to access the old information. You do not need to have the old system installed you can just save it and install it if you need to.

Determining When to Make Backups Determining a procedure for creating backups is a vital part of maintaining your database. If you make frequent entries in your database, you will need a backup procedure that guarantees the reliability of your data and will allow you to fully recover your data after any failures that may occur. We also recommend that you always make a backup before: expanding the database. deleting a database. (You cannot retrieve it after it has been deleted unless you have saved a backup.) installing or removing equipment from the computer or computers on which the Dynamics NAV database is stored. performing date compression (see the section called "Creating Space in the Database" on page 81) and optimizing tables (see the section called "Optimizing a Table" on page 89). copying the database or parts of it with an operating system command. using programs to optimize your hard disk. It is always a good idea to have an up-to-date copy of your company data in a secure place (a bank box, for example) in case of fire, theft, computer viruses, and so on. Procedures for Making Backups There is no formula for how often you should make backups, but remember that if you restore a backup that is a week old, you will have to reenter all the information for the past week. A backup is no more secure than the original data, so you must also protect yourself against errors in the backups. One way to do this is to create a system of backups at several levels: Every day, back up the company. If you have made design changes, make backups of the application objects or database. Every week, back up the database. Store the results so that the five most recent backups are in different locations. (About every month or so, put a backup copy in the companys safe or other secure place.) If a problem occurs in one place, the previous backup can probably be used. Every six months, restore the latest backup onto a different computer than the one you normally work on. Then test the contents of the hard disk. If there are no errors, put the copy in the companys safe or another secure location outside the company.

130

5.1 Why, When and How to Make Backups

Using this backup procedure, you will at most lose only a limited amount of data, because you should be able to restore data from a previous backup without any problem. Backups in a Network If you work with Dynamics NAV in a network, a good procedure is to make a backup to the local hard disk, copy it to the network server, and compare the copy on the server to the backup on the local hard disk.

131

Chapter 5. Making Backups

5.2 Using the Microsoft Dynamics NAV Backup Function

You can make backups by copying the database with an operating system command, but there are several important advantages to using the Microsoft Dynamics NAV backup function:
Advantages of using Dynamics NAV backup function

The system tests the database for errors, so incorrect information is not copied to a backup. The data is compressed, so it takes up as little space as possible. The system calculates how much space the backup will use. You can keep working in Dynamics NAV while you are making a backup. Whenever you create a new database, you must always use a Dynamics NAV backup to restore the Data Common to All Companies and the Application Objects into the new, empty database. Data common to all companies includes the report list, permissions groups, user IDs and printer selections, but no real company data. For more information, refer to page 138.
Tip

You can make a backup while other users are using the database because when you do, the program backs up the latest version of the database. If a user writes something into the database, a new version of the database will be generated, but the backup program will continue to back up the version that existed just before this new version of the database was created. However, if the clients are entering large amounts of data, an error can occur in the database backup. We therefore recommend that you make your database backups when no clients are using the system.

Preparing for a Backup To make a backup, click Tools, Backup and the Backup window appears:

132

5.2 Using the Microsoft Dynamics NAV Backup Function

You can now specify how extensive you want the backup to be. Click the option button next to the type of backup that you want to make: Entire Database (including all companies in the database, data common to all companies, and application objects) All Companies (that is, only the companies) Custom (whatever you select) If you select Custom, you must place a check mark next to the companies that you want copied. You do this in the list of companies under Selected Companies. You can make a backup of any item or combination of objects that you like. For example, the application objects and one company. You cannot make a backup of part of a company. It is best to make an complete backup. If you need to restore a backup later on, you dont have to restore the entire backup you can choose how much of the backup to restore.
Description, name and location of the backup

You must give the backup a unique description in the Description field at the bottom of the window. In the File Name field, enter a name for the backup. Dynamics NAV will suggest file names containing consecutive numbers and the file name extension .fbk. It is a good idea to use the default because Dynamics NAV will use the same default when you restore backups. It will also help you get a quick overview of the backups you have. The file name of the backup includes the path (location on the disk or network). If you enter only a file name, the backup will be saved in the current folder on the current drive. This will normally be in the same place as Dynamics NAV. If you want to save the backup in a different location (because it takes up too much space, or because you want to save it on disks, for example), enter the path and the name in the File Name field. To save the backup with the correct name and location, click the AssistButton to the right of the field. A standard Windows dialog box appears and you can use this to select a target drive and directory where you want to store the backup. Type the file name of the backup. Click Save when you have finished. The File Name field now contains the name of the backup. Click OK to start making the backup, and the following window appears:

133

Chapter 5. Making Backups

While the backup is being made, you can see how much of the database has been copied so far on the top status indicator. You can see the status of the disk or disk location it is being copied to on the bottom status indicator. To stop the backup, click Cancel. If you do not cancel it, the backup will proceed, and you will receive a message when it has finished.

Verifying a Dynamics NAV Backup To verify that a backup is consistent, simply restore it to a new, empty database. If you are able to read the data in the database, the backup is consistent. If you have only backed up a company, restore the backup to a database that contains only the Application Objects and Data Common to All Companies, and see if you can read any data in the company.

Automatic Backup on Windows Server If you want to make an automatic backup of the database at a specific time on the Windows server, and you run a client/server installation with the server running as a Windows service, you could use the built-in AT and net start/stop command. The AT command runs a given batch file at a given time. Type "AT" after a command prompt to get further help for this command. The batch file could look like this:
net stop <myserver> backup <path and databasename> net start <myserver>

where myserver is the name of the C/SIDE Database Server running as a service on Windows. Backup is the name of the backup program that backs up your database named "databasename." Store these three lines in a batch file, and supply this batch file as a parameter to the AT command. Remember to supply the full path to the batch file. The AT command requires that the Windows Schedule service is running.

134

5.3 Testing before Using Other Backup Methods

5.3 Testing before Using Other Backup Methods

The Dynamics NAV backup function makes a backup by creating a file containing the most basic information from the database. When the backup file is restored back into the system, Dynamics NAV recreates the rest of the information from this file. The larger the database, the longer it takes to back it up and to restore the backup. Because of this, users of installations with large databases often choose to back up onto tape, using the tape stations backup program. You can also use the Dynamics NAV backup function to make frequent backups to the hard disk, and then back up the entire hard disk onto tape. Doing this backs up both the working database and the Dynamics NAV backup of the database.

Testing the Database before Copying It to a Tape Station If you choose to make backups without using the Dynamics NAV backup function, you must first test the database for errors. To do this, use the DB Test program property or click File, Database, Test on the menu bar. Testing the database is described starting on page 68. If you choose to use the built-in backup function, you do not have to run the test. While the backup is in progress, the backup program checks the database for errors. It tests primary keys and data.

135

Chapter 5. Making Backups

5.4 Restoring Backups

Before you can restore a Dynamics NAV backup you must create an empty database into which you can restore the backup. This is because you cannot restore data over existing data. Creating a new database is described in detail starting on page 59. Remember that all the database files should be the same size. Although you do not want the new database to be too large, it must be large enough to contain the backup. If the backup was made using the Dynamics NAV backup facility, it will be packed, and you may not know its size when it is unpacked. In this case, start with the size that you think you need. If that is not large enough, you will get an error message when you try to restore, and you can expand the database a little at a time. (Expanding the database is described starting on page 61.) Then you can try to restore the backup again. When you have created the database and restored Data Common to All Companies and Application Objects, proceed in one of the following ways: If the backup was made with the Dynamics NAV backup function, click Tools, Restore to restore the backup. If the backup was exported to a tape station using the tape stations backup program, use the tape stations corresponding restore program. Remember that using the tape stations own restore program will probably overwrite the entire existing database. When you click Tools, Restore, a standard Windows dialog box appears and you can use this to locate the backup on the disk, hard disk or network. Find the folder containing the backup, and select the backup file. Click Open to open the Restore window:

The name of the backup appears in the File Name field with its description and the time and date of its creation in the two fields above it. In the lower part of the window, you can select how much of the backup will be restored: Entire Backup (including all the companies in the database, Data Common to All Companies and Application Objects)

136

5.4 Restoring Backups

All Companies (that is, only the companies) Custom (the Selected Companies, and can also include Data Common to All Companies and Application Objects). Remember that whenever you have a completely empty database, you must start by restoring a backup that contains at least these two options. You cannot restore the data common to all companies into a database that already has other tables in it. You can limit the amount of the backup that you want to restore. To do this, remove some of the check marks in the window. After you have made your selection, click OK to start the restore. A status window appears allowing you to monitor the progress of the restore procedure:

If you restore from disks, you will be prompted to insert new disks. The amount of time it takes to restore a database depends on the size of the database.

137

Chapter 5. Making Backups

5.5 Advanced Backup and Restore Information

Description of a backup file

The backup file is a slightly compressed copy of the database. The backup program copies small blocks from the database, compresses them and gives them a header. Among other things, the header has a header checksum, which ensures data integrity. When the backup program has written all the small blocks, it calculates and writes a master checksum. These two checksums have two purposes: To verify that data in the backup is consistent and not corrupted. To protect the backup from modifications.

The header in the backup file

At the beginning of the backup file you will find a header in ASCII format containing a list of all the objects in the file. To see a list of the objects included in the backup (named, for example, backup.fbk and located in the folder d:\backup\), go to a command prompt and type the following:
type backup.fbk | more

The backup file contains an end of file marker after the list, so you do not see the binary content of the file. For each object, the list will show you its type, number, name, date and time of creation, size in bytes and a version number. If the object is table data, the version number is replaced with the name of the company to which the data belongs. This list is useful for seeing which objects are included in the backup, without restoring the entire backup.

Constraints on Restoring a Backup There are certain constraints when you restore a backup into a database that is not empty. When you create an empty database, it is actually not completely empty. An empty database is defined as a database that contains only an empty security system and the company table definition. You can define and limit user access permissions to the database in the security system. An empty security system is identical to the security system that is automatically generated when you generate an empty database in Dynamics NAV. An empty security system consists of the tables listed below:
Table User Group Permissions User Member Of Defines... the user groups that you want in your system. which rights the different user groups have. the individual user and his or her password. which groups the individual users belong to.

Of the tables here, only the User Group and Permission tables, where a superuser has been set up, hold data. If you change the contents of the four security tables, the security system is no longer empty. The contents of the backup can be divided into the following data types: Application Objects, which comprise the application, such as the Customer table, the Item table and the G/L Account table.

138

5.5 Advanced Backup and Restore Information

Data Common to All Companies, which includes the report list, permissions groups, user IDs and printer selections and the security system tables. Company Data, which is all the data in the tables. The following table contains answers to questions or problems that may arise during the restore process:
Question or Problem Answer

Can I restore everything into All data types can be restored into an empty database. an empty database? Can I restore objects of the No. Objects of type Application Objects can only be restored into an type Application Objects into empty database. a non-empty database? I cannot restore my company You cannot restore a company if there is another company with the into the database. same name in the database. If, however, you want to restore the company that is in the backup, rename the existing company in the database, and then restore the company in the backup. I cannot restore objects of If the database contains objects of type Data Common to All the type Data Common to All Companies other than the security system tables, it is not possible to Companies. restore objects of type Data Common to All Companies. I am prompted to confirm overwriting of the existing security system while restoring. What does that mean? If all objects of type Data Common to All Companies in the database are security system tables, then all objects of type Data Common to All Companies can be restored. If neither the security system in the database nor the security system in the backup is empty, you will be prompted to confirm whether the existing security system in the database should be overwritten by the security system from the backup.

To restore data from three different backups into an empty database: 1 Restore the objects of type Application Objects from one backup. 2 Restore the objects of type Data Common to All Companies from another backup. 3 Restore Selected Companies from yet a third backup. To calculate the amount of free space that is required in the database to restore a backup, use the following formula:
The minimum size needed to restore

Free space needed in database = twice the size of the selected items to be restored + the size of the generated secondary keys + twice the amount of the data in the largest table. The last term represents a worst-case scenario, and you can usually manage with less space than this formula calculates. The generated secondary keys are those keys that were active when the backup was made. Changed Table Definition Compared to Backup If a field in a table definition has changed its type or number compared to the backup, it is not possible to restore data into the corresponding table. If you have changed some of a fields properties in a table definition, the restore program will try to fit the

139

Chapter 5. Making Backups

data into the table anyway. If, for example, you have shortened a text fields length from 80 to 40 characters, and there is no data in that specific table in the backup that is longer than 40 characters, the backup will be successfully restored. Otherwise the restore will stop, and you will have to increase the length of that particular field. After that, you can continue the restore from where it stopped.

140

5.6 Server Based Backup

5.6 Server Based Backup

Microsoft Dynamics NAV also has a server based backup program, called HotCopy. This program is installed with C/SIDE Database Server and is stored in the same directory as C/SIDE Database Server. HotCopy can only be run from the server location and can only create backups on hard disks. You cannot make incremental or differential backups. The backups are file copies of the database and are not compressed. You can make a backup of a database while clients are using it. However, if these clients are entering large amounts of data, an error can occur in the database backup. We therefore recommend that you make your database backups when no clients are using the system. Furthermore, if HotCopy is the first 'user' to connect to the server it will place an exclusive lock on the database and no other users will be allowed to login while HotCopy is running. This is done for performance reasons. If other users are already logged on the server, HotCopy runs as an ordinary session. HotCopy will then apply the version principle and copy its own version of the database. Running HotCopy as a session places a greater burden on the server.

Using HotCopy You can only create a backup from the command prompt. You must specify a number of parameters:
hotcopy source=databasefile1 (databasefile2databasefile16) destination="backup directory1" ("backup directory2""backup directory16") [description="This is the backup for Monday"] [[email protected]] [servername=myserver] [user=myname password=mypassword | osauthentication=yes] [dbtest=normal] [cc=yes] [nettype=tcps|tcp|netb]

The parameters are case sensitive and those that are enclosed in [ ] are optional. Every entry that contains a space must be placed inside quotation marks. The following example only uses the mandatory parameters. The database is stored in the same directory as the server based backup program and the backup is stored on another computer:

141

Chapter 5. Making Backups

hotcopy source=database.fdb destination=\\backupcomputer\backup\Monday

The following example uses all the parameters and the database is divided into two files:
hotcopy source=C:\database\database1.fdb C:\database\database2.fdb destination=\\backupcomputer\backup\Monday description="This is the backup for Monday" [email protected] servername=myserver user=myname password=mypassword dbtest=normal cc=yes nettype=tcps

Note that you must enter the path to each database file.
Backup description file

Alternatively, you can refer to a backup description file that contains all the relevant parameters. We recommend that you use the backup description file.
hotcopy source=backupdescription.txt

You can give the backup description file any name that you like. The parameters are:
Parameter source Explanation The database file to be used for the backup. You must use this parameter. This can be either the name of the database or the name of a database file. If you want to make a backup of several database files, you must specify all of the file names. If you are using a backup description file, you must enter the name of the backup description file. You must enter either the absolute path or the relative path to the database file(s). When no path is specified the database file(s) must be stored in the same directory as HotCopy.exe. You can also enter the full path of the backup description file. If a backup description file is specified as the source file, all the other command line arguments are ignored. The format of the backup description file is described below.

142

5.6 Server Based Backup

Parameter destination

Explanation The path of the directory to which the database file is to be copied. You must use this parameter if you are creating the backup with the command line arguments. If only one path is specified for the destination but several files are specified as the source, all the files will be backed up in the same destination. If all the database files have the same name, the backups must be created in different directories. The database file(s) that you backup will be saved in the destination directory with the same name as the original(s). If the destination path is the same as the source path, the database file will be saved with a new suffix ".bak". For example, database.fdb will be saved in the source directory as database.fdb.bak. If you have previously made a backup in the destination directory, HotCopy will overwrite it. HotCopy will not inform you that it is overwriting the previous backup. Furthermore, if you want to overwrite the existing database backup, you must ensure that the destination is at least twice the size of the database that you want to backup and that half of this space is free. The extra space is required because HotCopy creates a temporary file before overwriting the previous backup. This temporary file is the same size as the database that you are backing up. A database test is performed before the backup is made. You can choose between three different tests that correspond to the standard Dynamics NAV database tests. The possible values are: minimum, normal and maximum. For more information about database tests, see Testing the Database on page 68. A consistency check should be performed after the backup files are saved. The consistency check is a bit for bit comparison of the original database with the backed up one. The possible values are: yes and no. This is a free text that describes the backup. This text is displayed as the subject in the E-mail that the administrator can receive and as the "source" entry in the Event Viewer. The E-mail address of the person who is to be informed about the final status of the backup procedure. The E-mail message contains the following information: Subject: This is the backup for Monday (The description of the backup). Backup started at 2001/03/15 10:02:50. Backup ended successfully at 2001/03/15 10:06:06. If the backup failed the E-mail will only contain the description of the backup and a message informing you of the error that caused the backup to fail.

dbtest

cc

description

email

143

Chapter 5. Making Backups

Parameter servername

Explanation The name of the C/SIDE Database Server that HotCopy should connect to when you initiate the backup procedure. If you omit this argument, HotCopy will try to create a connection using the "local host" name. If this also fails because C/SIDE Database Server is not running HotCopy will create a "local" connection. In other words you can create a backup when the database server is not running. We recommend that you only use HotCopy when C/SIDE Database Server is running. Whether or not the person creating the backup can use single sign-on (NT authentication). The only value you can enter is yes. You can either enter this parameter or the user and password parameters. If Windows authentication is not used this is the user ID of the person performing the backup. If Windows authentication is not used this is the password of the person performing the backup. The network protocol that is used for communication between the server and the clients. The possible values are: tcps (TCPS), netb (NetBIOS) and tcp (TCP/IP).

osauthentication

user password nettype

The Backup Description File The backup description file contains information that HotCopy will use to perform the backup. The file has two section containing one or more entries. The backup description file can include comments any text string that begins with a semicolon and does not take up more that one line. The backup description file must have the following format:
[Backup Files] \\backupcomputer\backup\Monday\database.fdb=\\computer\shareName\Bac kupDirectory \\backupcomputer\backup\Monday\database1.fdb=\\computer\shareName\Ba ckupDirectory \\backupcomputer\backup\Monday\database2.fdb=\\computer\shareName\Ba ckupDirectory [Options] ;This is the description of the Monday backup description=This is the backup for Monday dbtest=normal cc=yes [email protected]

144

5.6 Server Based Backup

servername=myserver user=myname password=mypassword osauthentication=no nettype=tcps

You must fill in the section called [Backup Files]. In this section you specify the database name on the left hand side and the backup directory on the right hand side. You can only specify a directory as the destination for the backup.
Output

The outcome of the backup procedure is always specified in the Event Log of the computer that was used to start the backup procedure. The backup administrator can also be notified of the result of the backup procedure by E-mail.
Note

If you have set up C/SIDE Database Server as a service and want Hotcopy to store the database backup on a remote computer, you must change the Log On options of the C/SIDE Database Server service. You must give the C/SIDE Database Server service the credentials of a domain user that has the appropriate rights on the remote computer and not use the default value (local system account). Restoring a Copy of the Database To restore the database: 1 Stop the server. 2 Replace the database files with the backed up versions. 3 Start the server. The backup must be restored to the same directory that the original database was stored in. If the original database has been deleted or the disks on which it was stored have been destroyed, you must recreate the original configuration with the same directory and exactly the same path as the original database before restoring the backup. Alternatively, can start the server and specify the location of the new database and all of the database files in the command line.
Important

The backup that HotCopy makes is a snapshot of the database. It does not contain information about any transactions that were carried out after the backup procedure was started. Dynamics NAV cannot create a transaction log. If you want to have a transaction log, you should migrate to the SQL Server Option for Microsoft Dynamics NAV.

145

Chapter 5. Making Backups

146

Chapter 6 Advanced Performance Issues

Performance issues are important for the system administrator. The system must be optimized to make it as effective as possible. This chapter describes how to tune your system and what equipment to buy to obtain an optimized system. It also describes how to detect bottlenecks at both a software and a hardware level, and how the Windows Performance Monitor can help you. The chapter contains the following sections: Checklist for Optimizing Hardware Selecting Hardware, Operating System and Protocols Detecting Bottlenecks

Chapter 6. Advanced Performance Issues

6.1 Checklist for Optimizing Hardware

There are many factors that must be considered if you want to get the best performance out of your enterprise business solution. It is not possible to define a single optimal solution, because there are many individual requirements that have to be considered. The information in this chapter will help you assess your requirements, and select the appropriate hardware and software. Once you have established the network, you can optimize the system by tuning the various parameters described in the following sections. The following table can be used as a checklist when you optimize your installation:
Item Hard Disk Controller RAID Memory Network Adapter CPU Network Protocol Recommendation As fast as possible Fast, secure and battery backed, able to control several hard disks simultaneously RAID 1 is preferable As much as possible, of ECC type or with parity As fast as possible As fast as possible TCPS You can read more about this on: page 149 page 149 page 150 page 151 page 151 page 152 page 153

148

6.2 Selecting Hardware, Operating System and Protocols

6.2 Selecting Hardware, Operating System and Protocols

When deciding what kind of network configuration to use, there are several points that are worth considering: Security level Quality Price Required performance level Number of users The networks ability to be expanded The optimal network configuration is very dependent on individual requirements because it represents a balance of these criteria. Therefore, identify you network requirements before configuring it.

Choosing the Computers In a multiuser solution, you can, in principle, use the same type of computer for both the clients and the server. There is a difference, however, in how much CPU power, memory (and memory type) and disk space each will need. Computers for Clients and Single-User Installations An important factor to consider is that, in a network, it is the client computers that process the data they retrieve from the database. Consequently, a slow client computer working on a transaction can delay all the other clients until it finishes because it locks certain parts of the database. Thus, it is important to buy powerful client computers with enough computing power not to slow down the network. The faster the computer, the faster the transactions will be processed. Computers for Servers The database is stored on the server, making it a critical area of the application since several users can access it at the same time. It is therefore important to select a powerful computer for the server. In addition, there are certain aspects of the server that require further consideration: The hard disk and controller The RAID system The memory The network adapter The CPU The Hard Disk and Controller The hard disk is the slowest component in a computer because it consists of mechanical parts. Access times to the hard disk are long compared to those to memory (normal access time to memory is less than 60 nanoseconds and access time to a hard disk is faster than 10 milliseconds). All of the programs and information are stored on the hard disk, so data is continuously read from and written to the disk. Since there is only one read/write head in a hard disk, only one read or write operation can be carried out at a time.

149

Chapter 6. Advanced Performance Issues

By using more than one disk in your system, you can increase performance dramatically. You must, however, use a hard disk controller that supports control of more than one hard disk at a time without increasing access time to the disks. Furthermore, it is important for the controller to have a high transfer rate so data can travel quickly between the memory and the hard disk. The use of CPU per disk transfer must also be minimized. An example of a controller with these features is the Fast Wide SCSI 2 (Small Computer System Interface) controller.
Warning

Do not use the write-back or lazy-write caching systems that are built into your hard disk controller unless the disk controller has a battery backup. Using a batterysupported hard disk controller will prevent loss of data that might otherwise result if the system suffered a power failure. You should also be aware of the write-cache facility that most of todays hard disks use. When you buy a hard disk, be sure that you can disable its write-cache (using software or a jumper on the disk). If a power failure occurs when data is still in this cache, you could lose the data. It is also necessary to have some sort of error detection unit implemented to allow the controller to determine when a byte of data in the cache is corrupted for example, from a single-bit error or a defective memory chip. Furthermore, any errors that occur must be corrected, so some sort of correction scheme must be implemented in the controller. An ECC (Error Correction Code) RAM is an example of this kind of correction scheme.
Speed and hard disk capacity

You can increase performance by several hundred percent by expanding your system from one to six hard disks. To avoid poor performance in your daily work, you should add more than one hard disk to your system and divide the database among these hard disks. Four relatively slow hard disks (for example of 5 GB each) perform much better together than one super hard disk (of 13 GB). Tests have shown that the fourhard-disk configuration allows more than twice the number of transactions per second than the one-hard-disk configuration. Each hard disk that you add will improve performance. As a rule of thumb you could say that each time you double the number of hard disks you increase performance by 100%. Several "intelligent" controllers exist, which can control several hard disks simultaneously, for example, RAID (Redundant Array of Independent Disks) systems. RAID Systems If you have a very large Microsoft Dynamics NAV installation, you should consider using a RAID system. This system consists of several disks. The key feature of a RAID system is that the failure of one disk does not bring the entire system down. You can recreate the lost data from parity information or from a direct copy stored on the other disks.

150

6.2 Selecting Hardware, Operating System and Protocols

Several RAID configurations exist and are described in the following table:
Item Raid 0 RAID 1 Description Called striping. The data is broken up into chunks as it is written across all the drives. This provides the highest performance, but no redundancy is provided. Called mirroring. The data is written redundantly to pairs of drives and can be read independently from each drive. This is fast and provides full redundancy, but the disk capacity required is doubled. The read performance can be up to twice as fast as a single drive because both drives can process the read request simultaneously. Write performance is nearly unchanged. RAID 1 is best for transaction processing, where many small I/Os are required. Called redundancy through Hamming code. The data is bit-interleaved across groups of drives with some of the drives storing error correction codes. This provides full redundancy and more error correction capability, but is often slow due to the hardware overhead. Called parallel transfer disks with parity. The data is bit-interleaved across groups of drives with only one drive dedicated to storing parity. This provides full redundancy and high transfer rates when large blocks of data are transmitted. Called independent access array. The data is broken up into chunks and written across the drives with one drive dedicated to parity. This provides full redundancy, but the single parity drive causes a bottleneck when the parity has to be updated. Called independent access array with rotating parity. The data is broken up into chunks and written across the drives. The parity for the stripes of data is also spread across all the drives, so no one drive is dedicated to parity.

RAID 2

RAID 3

RAID 4

RAID 5

C/SIDE Database Server is a program that requires high security and good disk performance. RAID 1, mirroring, best satisfies these criteria with its combination of high performance in read processing and very high reliability resulting from a constant, online backup of the database. RAID 1 is, however, the most expensive configuration because every megabyte of disk storage requires two megabytes of actual disk space. The C/SIDE Database Server program can handle up to 16 disks (32 disks in a mirrored configuration). Memory and the Server It is important for the server to have enough memory for all its tasks. There cannot be too much memory in your server. Because a C/SIDE Database Server has to serve several users and must put some memory aside for each user, the amount of memory should be proportional to the number of users. Normally a user "takes up" 2 to 8 MB of Dynamics NAV cache, depending on the task, so you can estimate the requirements for your configuration. Remember to include the memory requirements of the operating system (at least 128MB for Windows Server 2003), the C/SIDE Database Server program (1 MB), 50 kilobytes per user connected to the server and add to this the memory requirements of other programs that are running. It is also important that the memory has a parity bit or is of the ECC (Error Correction Code) type. The Network Adapter Communication to and from the client passes through the network. If messages are to be delivered quickly, you must have a fast network adapter. This also ensures that the

151

Chapter 6. Advanced Performance Issues

CPU use per network send/receive activity is minimal, which reduces the load on the CPU. The physical connection (the cabling) between the server and the clients must also be able to support the high speed. The CPU The speed of the CPU is also an important performance factor. It is the CPU that performs all the calculations involved in Dynamics NAV the faster the CPU, the more calculations per second. It is also important to have as much level 2 cache in the system as possible. This increases the speed with which the CPU gets data from and saves data to RAM. However, it should be noted that adding more hard disks gives a greater improvement in performance than increasing the speed of the CPU.

The Operating System The C/SIDE Database Server can run on the following operating systems: Windows Vista Windows XP Windows Server 2003 The Dynamics NAV client (or a single-user) installation can run on the following operating systems: Windows Vista Windows XP Windows Server 2003 The C/SIDE Database Server program and Dynamics NAV clients can only run on 32-bit platforms.

Network Protocols Dynamics NAV can use three protocols: TCPS TCP/IP NetBIOS

152

6.2 Selecting Hardware, Operating System and Protocols

The most important advantages and disadvantages of each protocol are: TCPS is the recommended protocol and is a secure version of TCP/IP that uses the Security Support Provider Interface (SSPI) with encryption enabled and Kerberos authentication. TCPS
Advantages More secure than TCP/IP Faster than NetBIOS Can be routed Is used on the Internet Disadvantages Difficult to configure

TCP/IP
Advantages Faster than NetBIOS Can be routed Is used on the Internet Disadvantages Difficult to configure

NetBIOS
Advantages Easy to configure Disadvantages More difficult to route Not as fast as TCP/IP

The advantages of TCP/IP make it the preferred protocol, even though configuring it is more complicated.
Tip

If you experience problems connecting the Dynamics NAV client to the C/SIDE Database Server in a network that runs TCP/IP and you have a DNS (Domain Name System) server or DHCP (Dynamic Host Configuration Protocol) server, try starting the C/SIDE Database Server with the property servername=<the machine name>.Then connect the Dynamics NAV client to the C/SIDE Database Server with that server name. The machine name can be found in the network configuration program. The name you use for the C/SIDE Database Server must be registered in the HOSTS file on the DNS or DHCP server. The machine name is registered in this HOSTS file. If your network does not have a DNS or DHCP server, you can use the TCP/IP command PING to verify that

153

Chapter 6. Advanced Performance Issues

the server name exists. PING simply tries to make contact with the specified machine. Type ping <servername> after the command prompt. If you get a reply, the server can be reached. If not, you must reconfigure your TCP/IP network to include the server in the host file.

154

6.3 Detecting Bottlenecks

6.3 Detecting Bottlenecks

A bottleneck causes the system to run slowly and perform poorly. Bottlenecks can occur in the software or in the hardware.

Software Bottlenecks A bottleneck in the software may result from the system being poorly adjusted. There are three relevant properties to adjust in Dynamics NAV: DBMS (Database Management System) Cache Commit Cache Object Cache You can find a detailed explanation of these caches starting on page 39. If the DBMS Cache is set too high and if there is not enough of the faster physical memory for the systems requirements, the system will begin to swap (using the slower hard disk as memory). If the DBMS cache is set too low, there may not be enough DBMS cache for Dynamics NAV to operate. Both situations cause the system to run slowly. Turning off the Commit Cache can also slow down the system. Database Management System (DBMS) DBMS Cache/Commit Cache

Database

DBMS Cache and Commit Cache

As the previous diagram shows, the DBMS cache and commit cache are database related. Therefore, in a client/server environment these two caches are on the server along with the database, and the object cache is on the client machine. (In a standalone installation, all three caches are together.) The system may perform badly if these caches are not optimally sized for your system. The following formula is a way of calculating the amount of DBMS cache you need: Size of DBMS Cache = + Amount of physical memory Memory requirements of the operating system 50 kilobytes x number of workstations 1 MB for the C/SIDE Database Server memory requirements of other programs running The maximum size of the DBMS cache is 1000 MB. The commit cache takes up space in the DBMS cache (but it does not take up additional space in memory). It can use up to 2/3 of the allocated size of the DBMS cache.

155

Chapter 6. Advanced Performance Issues

Object Cache

Object cache is used on the client computer to store the objects (code, descriptions and windows) retrieved from the server. The client needs to retrieve these objects only once from the server and can then store them in the object cache. The total size of all the objects used in the standard application is around 20 MB. If you have enough memory, set the object cache to 20 MB. The size of the most important objects (the table descriptions) is 1 MB. You should set the object cache to 1 MB as a minimum. This is the default value. When you install the server program in a network, you can choose to install it on the file server or on a dedicated server. Installing the program on a dedicated server gives better performance because a dedicated server doesnt have to do other things. Remember to place the database on the same server as the server program so the server program doesnt have to use the network to get information from the database.

Hardware Bottlenecks To test whether a bottleneck occurs at the hardware level, you can use the Performance Monitor. This tool monitors the different sections of the computers memory. Alternatively, you can use two virtual tables in Dynamics NAV that contain various types of information about the performance of the computers hardware. These are the Database File table and the Performance table. You can also use the Session table to find out how many database connections are currently open. To access the Database File table, click File, Database, Information. On the Database tab, click the AssistButton next to the database name. Select the database, and click Tools, Zoom. The following window appears:

The most important pieces of information here are the mean read and write times. In an optimized system, these should be no more than 10-13 milliseconds (ms). If these figures are significantly higher, try to optimize the disk system according to the recommendations given earlier in this chapter. The Reads in Queue and Writes in Queue fields show whether there are any blocks (of size 8 kilobytes) of information waiting in the commit cache. Finally, the disk load is shown as a percentage of maximum load.

156

6.3 Detecting Bottlenecks

To see how the network is performing, create a form containing the (virtual) Performance table. Doing this requires a developer license because you can only see the Performance table from the Object Designer.

This table performs a net test with packets of 100 and 4000 bytes. The net test measures how many of these packets it is possible to send and receive per second. For the system to be fast, the number of packets per second should be greater than 400 for the 100-byte packets and greater than 70-80 for the 4000-byte packets. If the test results are less than this, the network should be optimized (by changing from NetBIOS to TCPS, for example). This table also shows how much of the CPU power on the client and on the server is currently used (0.00 percent means that the CPU is currently idle).

The Performance Monitor Another way to get similar information about CPU, disks, net and memory is to use the Performance Monitor.
Tip

To see the disk performance with the Performance Monitor, make sure that the device named diskperf has been started. The following table illustrates the ways in which the Performance Monitor can help you deal with bottlenecks that can occur when running Dynamics NAV:
Problem Pages/sec shows that the memory has been swapping to the disk when the C/SIDE Database Server is running. (You add Pages/sec to the Performance Monitor by clicking Edit, Add To Chart and in the Add to Chart window, selecting the Object Memory and the Counter Pages/sec). Solution Buy some more RAM for the computer, or try to decrease the Dynamics NAV cache size according to the formula given earlier in this chapter.

157

Chapter 6. Advanced Performance Issues

Problem % Disk Time is more than 80% over a long period (not peak value), and you are sure that the system is not swapping. Remember to select the correct instance (that is, the correct disk), and make sure that the diskperf device is started. (You add % Disk Time to the Performance Monitor by clicking Edit, Add To Chart and in the Add to Chart window, selecting the Object PhysicalDisk and the Counter % Disk Time.)

Solution Buy faster hard disks, or divide the database among several disks. Try to increase the cache size according to the formula given earlier, and follow the other recommendations given in this chapter.

% Processor Time for the server process is 80% Buy a faster CPU for the machine. or more over a long period (not peak value), indicating that the CPU is used all the time for the Server process. (You add % Processor Time to the Performance Monitor by clicking File, Add To Chart and in the Add to Chart window, selecting the Object Process not Processor and the Counter % Processor Time and then selecting the Server process in the Instance field.)

158

Appendix A Glossary
This appendix contains an alphabetical list of useful technical computer terms used in this book.

A.1 Glossary
Active Directory Active Directory is the directory service used in Windows Server 2003. It allows any object on a network to be tracked and located. Active Directory provides the ability to build applications that give a single point of access to multiple directories in a network environment. backup To keep your data safe, you should frequently make a copy of it. This copy is called a backup. BLOB Binary Large Object an object that can store anything but is normally used to store bitmaps and memos. cache Cache means a store or hiding place. As a computer term, it refers to part of the computers memory. The cache serves as a way station for data that is on its way to or from the hard disk and needs to be processed by the CPU. The advantage of using cache is that it is a quickly accessible memory that can keep the hard disk from having to work too hard. The larger the cache, the better the performance. The Microsoft Dynamics NAV program property called Cache represents the programs database cache and must not be confused with the Commit Cache program property. (See the separate entries for commit cache and object cache.) client A client is one of the computers in a network from which an individual user works with the common data that is found on the server. See single user. client/server This is the term for a particular way in which several computers (a server and some clients) work together in a network. Each computer does some of the work itself (in contrast to old-fashioned systems, in which the server did all the work and was therefore heavily loaded and slow). A client/server system is faster than one in which all the work is done by the server. command line You can type command lines (such as copy, del, and rename) in response to a prompt from an operating system (MS-DOS) and specify parameters for running programs. A C/SIDE Database Server for Microsoft Dynamics NAV can be started from a command line. commit cache When the Microsoft Dynamics NAV database is updated by write transactions or deletions (for example, when you are posting), the screen is locked for a certain period. When you use commit cache, Dynamics NAV can register write transactions as soon as they are logically present in the database, before they are physically written to the disk. In this way, the screen is not locked as long as it would otherwise be, and your work is speeded up. The function is especially useful in larger networks. Commit cache is described in the chapter called "System Setup" on page 39. Configuration See setup.

CPU The CPU (Central Processing Unit) is the "brain" of a computer. It is the element that contains all the computing power and makes it possible to run programs. C/SIDE (Client/Server Integrated Development Environment) C/SIDE is the name of the development system in which Microsoft Dynamics NAV is programmed. It is partly a programming language and partly a collection of tools that standardize routines, functions and codes, and in other ways take care of trivial tasks. database login An entry in the User table that Microsoft Dynamics NAV uses to verify the user ID and password that the user enters in order to gain access to the

160

A.1 Glossary

Dynamics NAV database. A database login can give the user access to a Dynamics NAV database that is stored in either SQL Server or C/SIDE Database Server. database server The computer in a network that contains and manages a shared database is called a database server. database server authentication The process by which the information (user ID and password) entered by the user is verified. This can be done having the user enter an ID and password when they log on or by using a smart card to identify themselves to the system. DBMS (Database Management System) A layer of software between the physical database and the user. The DBMS manages all requests for database action (for example queries or updates) from the user. In addition, a DBMS permits centralized control of security and data integrity requirements. dedicated server A dedicated database server performs only tasks involving the database and no other network tasks. disk cache This is a portion of the computers memory that is set aside to temporarily hold information read from or written to the disk. domain A domain is a single security boundary of a Windows computer network. Active Directory is made up of one or more domains. On a stand-alone workstation, the domain is the computer itself. A domain can span more than one physical location. Every domain has its own security policies and security relationships with other domains. When multiple domains are connected by trust relationships and share a common schema, configuration and global catalog, you have a domain tree. Multiple domain trees can be connected together into a forest. domain controller With Windows 2000 or later, a server in a domain can be a domain controller. This is one of two roles that a server in a domain can have. The other server role is as a member server. A domain controller contains matching copies of the user accounts and other Active Directory data in a given domain. It is possible to change the role of a server back and forth from domain controller to member server (or stand-alone server), even after setup is complete. domain tree A domain tree consists of multiple domains which are connected by trust relationships and which share a common schema, configuration and global catalog. Multiple domain trees can be connected together into a forest. See domain. ECC RAM Error Correction Code RAM. RAM that implements a method of detecting and correcting errors that may occur. external cache See level 2 cache. forest A forest is a collection of Active Directory domain trees. Forests serve two main purposes: to simplify user interaction with the directory, and to simplify the management of multiple domains. See domain. hard disk controller Controls access to one or more disk drives, CD-ROMs and diskette drives. hosts file This file contains the mappings of IP addresses to host names.

161

host name The name of the computer in the network running TCP/IP. Connected to this name is an address that is the IP address of the computer. IP address Internet Protocol address. Every computer running in a TCP/IP network has a host name and a corresponding IP address. Other computers in the network use this IP address to communicate with your computer. There is a host name for each IP address; the host name and the IP address are listed in the hosts file. key Fast and efficient searches in a database require a sorting system. The information you are looking for is located in fields; by assigning an order to some of these fields, you can determine the order in which the fields will be searched. This field combination is called a key (or sorting key). A key can consist of a single field. Dynamics NAV comes with a number of keys, but you can set up more. Updating the keys consumes a lot of the computing power, so you can improve the performance by disabling some keys. The chapter about working with databases (starting on page 57) contains a more detailed description. lazy-write cache This is a type of cache that holds information in the cache between the disk and the disk controller. When the computer writes something to the hard disk, the disk controller actually writes the information to the lazy-write cache and not to the disk. The data is then written to the disk when demand on the system is low. level 2 cache Also called external cache. Level 2 cache is a cache that exists between the CPU and the memory. This is a very fast type of cache that improves the systems performance. log on/off To log on or off means to open or close a Dynamics NAV database. memory Computer memory refers to Random Access Memory (RAM). When a new program is started, the operating system places the program in the memory so that the CPU can work with it. multiuser installation A multiuser Dynamics NAV installation is one in which Dynamics NAV is used on several computers connected in a network and using common data on a server. NetBIOS NetBIOS is an abbreviation for Network Basic Input Output System. This is one of the protocols (sets of rules) that are necessary for different programs, including Dynamics NAV, to be able to communicate in a network. Other network protocols are TCPS, TCP/IP. network server The computer in a network that provides shared services to the other computers is called a network server. If it contains the Dynamics NAV database, it is also called a database server. We do not recommend that you use one computer as the server for both the network and Dynamics NAV because each role requires a large amount of computing power. non-dedicated database server A non-dedicated database server is a computer that not only manages the database program but also runs other programs. object The Dynamics NAV application consists of a number of objects, for example: tables, forms, reports, codeunits and dataports. object cache Object cache, like cache, allows the program to work faster. Object cache is used only on clients because its task is to store the code, descriptions and windows that will be used on the client, so they only need to be retrieved once. Using

162

A.1 Glossary

object cache requires the computer that is used as client to have enough memory to store the objects while they are being used. program property A program property is something you can use to set various system values or other information that affects how the program works. For example, in Dynamics NAV you can use the Database program property to specify the database that will be used. Many program properties can be set by clicking Tools, Options on the menu bar. In addition, most of them can be entered in the Target field or the command line used to start the program, as described on page 54. protocol A protocol is a set of rules, such as the set of rules that determines how data can be exchanged. NetBIOS is an example of such a protocol; TCPS is another protocol. RAID (Redundant Array of Inexpensive (or Independent) Disks) A storage system based on a disk array that holds a certain amount of redundant information. The redundant information can be used to detect and (in some configurations) correct errors that may occur. RAM See memory.

role A role is a collection of permissions that are given to a user. An example is a role that gives rights to read, post and print orders, invoices and credit memos. There is also an item called Roles on the Security submenu of the Tools menu. Note that the old concept of groups has been replaced by roles. rollback This is a feature of the Windows Installer service. The system restores itself to its initial state if an installation failure occurs. This feature is not available once an application has been installed successfully. At that point, an uninstallation would be required to remove the program. Even if the program is uninstalled, there is no guarantee that the system will be returned to its preinstallation state. schema The Active Directory schema is the set of definitions that defines the kinds of objects and the types of information about those objects, which can be stored in Active Directory. The definitions are themselves stored as objects so that Active Directory can manage the schema objects with the same object management operations that are used for managing the rest of the objects in the directory. server A server is the computer that serves the other computers in a network. A server carries out several functions. It can be a database server, network server and/or printer server. Thus, it enables the computers in the network to use the shared equipment or data. See also these terms: dedicated, nondedicated, database server, network server. service A process in Windows that performs a specific system function or executes a specific program. This execution is started as soon as the operating system is loaded, before any user is logged onto the system. services file This file contains port numbers for services. service connection point (SCP) The service connection point is an object that contains information about the server, such as binding information, the Domain Name System (DNS) name and type, product, version, globally unique identifier of the object (GUID), and so on. The C/SIDE Database Server must have an SCP object that contains the necessary server information. session A session is an active (running) copy of Dynamics NAV.

163

setup The setup of a computer is the way in which the system is adjusted to work with other hardware or software elements, such as a printer or a particular program. The setup is also called a configuration. The setup of a program is the way in which its functions are modified to fit the needs of a particular user. single sign-on A key feature of Windows authentication is its support of single signon. This is a process that allows a user with a domain account to log on to a network once with his or her password, and to gain access to any computer in the domain. single-user installation A single-user Dynamics NAV installation is one in which Dynamics NAV is used on an independent computer. The difference between a client and a single-user installation is that a single user uses its own database, whereas a client is connected to a network of computers that use a common database. SMS (System Management Server) If you have installed SMS software on every computer in the network, you can manage the whole network from the computer at the top of the network hierarchy. sorting key See key.

swapping This is a process used by a computer to enable it to use more memory than is physically present. If the active programs together use more memory than the computer has, the least-used data is "swapped" (moved) to the hard disk in a "swap file." When this data is needed again, it is retrieved back into the memory, and other data is placed in the swap file on the hard disk. You can read more about swapping in the description of the DBMS Cache program property on page 45. target field The field in which you specify the location of the program that you want to run, along with any parameters you want to set. You can read about this on page 54. TCP/IP Like NetBIOS, this is a network protocol. TCPS A secure version of TCP/IP. Windows authentication The process by which the user is verified by the single sign-on system or the unified login supported by Windows. In Dynamics NAV, we refer to both of these systems as Windows authentication. Windows login An entry in the Windows Login table that Dynamics NAV uses to verify that the user has a valid Windows account and has access to this Dynamics NAV database. A Windows login can give the user access to a Dynamics NAV database that is stored in either SQL Server or C/SIDE Database Server.

164

Appendix B Network Communications

This appendix contains information about setting up and testing network communications for running Microsoft Dynamics NAV. It assumes that you have a good understanding of personal computer hardware, LAN, NetBIOS or TCP/IP as well as the Windows operating system and servers. The instructions for installing the server and client programs can be found in chapter 1. The appendix contains information about the following topics: Setting Up Network Communications Testing Network Communications

B.1 Setting Up Network Communications

When the server program runs on Windows Server 2003, you can choose to use the TCP/IP or NetBIOS protocol.

TCP/IP on the Server TCP/IP is the default protocol in the Windows XP operating systems. The server program will use TCP/IP port 2407 as a default. If this port is occupied by another process, you can specify another port by making a new entry in the services file. The services file is normally located in the directory: C:\Windows\systems32\drivers\etc Open the services file in Notepad or any other ASCII editor and make a new entry in the services file using the following format:
<servername> 3001/tcp

Replace <servername> with the name of the server from which you start the server program, and 3001 is a free port number.
Note

If you make changes in the services file, you must make corresponding changes in the services file on all client units. Otherwise, the client will not be able to find the server program on the network.

TCP/IP on the Client The client program uses the WinSocket API. This means that the client program can run on any TCP/IP protocol that uses the WinSocket API. When the client program runs on Windows XP, the TCP/IP protocol included with Windows can be used. If you have changed the TCP/IP port for the server program, you must make the same changes in the services file for each client. This can be done in the same way as described in the section called "TCP/IP on the Server." If you are not running Domain Name Service then you will also have to edit the hosts file on all the clients. The hosts file, is normally placed in the same directory as the services file:
C:\Windows\systems32\drivers\etc

Open the hosts file in Notepad and make a new entry as follows:
x.x.x.x <servername>

Replace x.x.x.x with the server's TCP/IP address, and replace <servername> with the name of the server from which you start the client program.

166

B.1 Setting Up Network Communications

NetBIOS The server program looks at the license file to determine how many NetBIOS sessions it should allocate. The server program allocates one NetBIOS session for each client session purchased, plus one extra. The client program will request one NetBIOS session for each client session started.

167

B.2 Testing Network Communications

To test whether the communication works, you can use various test utilities, or you can try to establish communication between the server program and the client. One utility you can use with TCP/IP is ping. You use ping to check whether the server computer is reachable over the network. From the client computer, use the ping <host> command to check whether the TCP/IP connection is OK.

Establishing Communication between the Server and Client To test the communication between the server program and the client program, you must start the server program. Starting the Server Switch to the disk on which the server program is installed and then to the directory in which the server program is installed. Start the server program with the following three property settings:
servername=<servername> nettype=<nettype> database=<database path>

Server Name If you don't specify a server name, the server program will default to Server1. You can enter any name, but make sure that all clients are started with the same server name. Also make sure that when TCP/IP is chosen as network protocol, the hosts and services files use the same server name. When using TCP/IP, the server name in the hosts file on the client is used instead of the server name provided on the command line. Net Type Net Type should either be netb, when NetBIOS is used, or tcp, when TCP/IP is used. Database <database path> should contain the full path to the database.
Example

An example of starting the server program under Windows is:

server servername = FinServer, nettype = tcps, database=d:\fdb\database.fdb (written as one command)

If the server program has problems communicating with the network protocol, it will not start properly. In this case, it is recommended that you check the setup and make sure that everything has been specified correctly.

168

B.2 Testing Network Communications

Starting the Client After the server program has been started without problems, start the client program. The important program properties for the client program are Server Name and Net Type. It is a good idea to specify these properties in the Target field of the Dynamics NAV Properties window. (Read more about this on page 54.) When you start the client program with the proper server name and net type, you should be able to communicate with the server program. If you have any problems, check the communication setup.

169

170

INDEX

A Active Directory adding schema extension . . . . . . . . . . . 18 and Dynamics NAV . . . . . . . . . . . . . . . . 112 definition . . . . . . . . . . . . . . . . . . . . . . . . 160 security . . . . . . . . . . . . . . . . . . . . . . . . . . 110 security, features . . . . . . . . . . . . . . . . . . 111 adding a Dynamics NAV Database Server to MMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Advanced window . . . . . . . . . . . . . . . . . . . . 66 application object, see object Application Objects .132, 134, 136, 137, 139 contents . . . . . . . . . . . . . . . . . . . . . . . . . 138 part of database . . . . . . . . . . . . . . . . . . 117 restoring entire backup . . . . . . . . . . . . 136 restoring into empty database . . . . . . . 63 authentication . . . . . . . . . . . . . . . . . . . . . . 110 Database Server . . . . . . . . . . . . . . . . . . . 111 definition . . . . . . . . . . . . . . . . . . . . . . . . 110 program property . . . . . . . . . . . . . . . . . . 38 selecting . . . . . . . . . . . . . . . . . . . . . . . . . . 38 specifying on client when opening a database . . . . . . . . . . . . . . . . . . . . . . . . . . 66 B B+ trees (balanced trees) . . . . . . . . . . . . . . 89 Backup window . . . . . . . . . . . . . . . . . . . . . . . . . . 132 backup advanced information . . . . . . . . . . . . . 138 all companies . . . . . . . . . . . . . . . . . . . . . 133 automatic under Windows NT . . . . . . 134 before date compression . . . . . . . . . . . . 81 contents, data type . . . . . . . . . . . . . . . . 138 custom . . . . . . . . . . . . . . . . . . . . . . . . . . 133 definition . . . . . . . . . . . . . . . . . . . . . . . . 160 effect of database size . . . . . . . . . . . . . 135 entire database . . . . . . . . . . . . . . . . . . . 133 errors in . . . . . . . . . . . . . . . . . . . . . . . . . . 130 extent of . . . . . . . . . . . . . . . . . . . . . . . . . 133 file description . . . . . . . . . . . . . . . . . . . . 133 file extension .fbk . . . . . . . . . . . . . . . . . 133 file location . . . . . . . . . . . . . . . . . . . . . . . 133 file name . . . . . . . . . . . . . . . . . . . . . . . . . 133 in a network . . . . . . . . . . . . . . . . . . . . . . 131 preparing for . . . . . . . . . . . . . . . . . . . . . 132 procedures for . . . . . . . . . . . . . . . . . . . . 130 restoring, see restoring a backup status window . . . . . . . . . . . . . . . . . . . . 134 system for making . . . . . . . . . . . . . . . . . 130 testing before . . . . . . . . . . . . . . . . . . . . . 135 verifying . . . . . . . . . . . . . . . . . . . . . . . . . 134 when to make a . . . . . . . . . . . . . . . . . . . 130

backup file description . . . . . . . . . . . . . . . . . . . . . . . 138 header in . . . . . . . . . . . . . . . . . . . . . . . . 138 BLOB definition . . . . . . . . . . . . . . . . . . . . . . . . 160 bottleneck detecting . . . . . . . . . . . . . . . . . . . . 155157 hardware level . . . . . . . . . . . . . . . . . . . 156 software level . . . . . . . . . . . . . . . . . . . . 155 C C/SIDE definition . . . . . . . . . . . . . . . . . . . . . . . . 160 cache commit see commit cache definition . . . . . . . . . . . . . . . . . . . . . . . . 160 locations of different types . . . . . . . . . 155 object, see object cache program property . . . . . . . . . . . . . . . . . 45 specifying size during installation . . . . 16 Change Password window . . . . . . . . . . . 124 changing the installation . . . . . . . . . . 1011 checksum header . . . . . . . . . . . . . . . . . . . . . . . . . . 138 master . . . . . . . . . . . . . . . . . . . . . . . . . . 138 client computer requirements . . . . . . . . . . . . . .3 definition . . . . . . . . . . . . . . . . . . . 2, 32, 160 installing . . . . . . . . . . . . . . . . . . . . . . . . 49 client/server . . . . . . . . . . . . . . . . . . . . . . . 2, 32 definition . . . . . . . . . . . . . . . . . . . . . . . . 160 close forms on Esc program property . . . . . . . . . . . . . . . . . 43 command line . . . . . . . . . . . . . . . . . . . . . . 160 defining program properties . . . . . . . . 54 commit cache bottleneck, software level . . . . . . . . . . 155 database in several files . . . . . . . . . . . . . 60 definition . . . . . . . . . . . . . . . . . . . . . . . . 160 for server . . . . . . . . . . . . . . . . . . . . . . . . . 45 program property - client and single-user 39 relationship to (DBMS) cache . . . . . . . . 45 specifying size during installation . . . . 16 status, checking . . . . . . . . . . . . . . . . . . . 74 companies, maximum number . . . . . . . . 58 company automatic selection . . . . . . . . . . . . . . . . 54 moving to a different database . . . . . . 63 opening automatically . . . . . . . . . . . . . 37 program property . . . . . . . . . . . . . . . . . 37 selecting on client . . . . . . . . . . . . . . . . . 67 specifying in Target field . . . . . . . . . . . . 54 specifying on client . . . . . . . . . . . . . . . . 37

Index

Company Data, contents . . . . . . . . . . . . . 139 compressing a database . . . . . . . . . . . . . . . 81 computer choice of . . . . . . . . . . . . . . . . . . . . . . . . . 149 requirements, single-users and clients . . 3 concurrency . . . . . . . . . . . . . . . . . . . . . . . . . 91 connecting to server . . . . . . . . . . . . . . . . . . 36 controller correction scheme . . . . . . . . . . . . . . . . . 150 RAID system . . . . . . . . . . . . . . . . . . . . . . 150 requirements . . . . . . . . . . . . . . . . 148, 149 CPU definition . . . . . . . . . . . . . . . . . . . . . . . . 160 requirements . . . . . . . . . . . . . . . . 148, 152 CRONUS International Ltd. . . . . . . . . . . . . 58 cronus.flf, demonstration license file . . . . 58 Current Sessions . . . . . . . . . . . . . . . . . . . . . 75 current sessions details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 number of . . . . . . . . . . . . . . . . . . . . . . . . . 75 custom setup Backup of Demo Database . . . . . . . . . . . 7 Business Notification Manager . . . . . . . . 7 Commerce Integration . . . . . . . . . . . . . . . 7 Demo Database . . . . . . . . . . . . . . . . . . . . . 7 Dynamics NAV Gantt Server . . . . . . . . . . 7 Employee Portal . . . . . . . . . . . . . . . . . . . . 7 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Outlook integration . . . . . . . . . . . . . . . . . 7 Custom Setup window . . . . . . . . . . . . . . . . . 8 D Data Common to All Companies . 132, 136, 137, 139 contents . . . . . . . . . . . . . 59, 132, 134, 139 part of database . . . . . . . . . . . . . . . . . . 117 restoring entire backup . . . . . . . . . . . . 136 restoring into empty database . . . . . . . 63 data version definition . . . . . . . . . . . . . . . . . . . . . . . . . 92 database altering . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 amount used . . . . . . . . . . . . . . . . . . . . . . 73 automatic selection . . . . . . . . . . . . . . . . . 54 automatic start . . . . . . . . . . . . . . . . . . . . . 36 closing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 compression . . . . . . . . . . . . . . . . . . . . . . . 81 connection to . . . . . . . . . . . . . . . . . . . . . . 74 creating . . . . . . . . . . . . . . . . . . . . . . . .5963 creating space in . . . . . . . . . . . . . . . . . . . 81 data compression, backup function . . 132 default on starting . . . . . . . . . . . . . . . . . . 67 deleting completely . . . . . . . . . . . . . . . . 72 deleting part of . . . . . . . . . . . . . . . . . . . . 72 deleting, warning about . . . . . . . . . . . . . 71 demonstration . . . . . . . . . . . . . . . . . . . . . . 2 errors, handling . . . . . . . . . . . . . . . . . . . . 70 expanding . . . . . . . . . . . . . . . . . . . . . .6163

expanding a working . . . . . . . . . . . . . . . 88 guarding against loss . . . . . . . . . . . . . . . 59 in one file . . . . . . . . . . . . . . . . . . . . . . . . . 60 in several files . . . . . . . . . . . . . . . . . . . . . 60 information about . . . . . . . . . . . . . . . . . 73 list of tables . . . . . . . . . . . . . . . . . . . . . . . 77 location . . . . . . . . . . . . . . . . . . . . . . . . . . 74 maximum size . . . . . . . . . . . . . . . . . . . . . 60 minimum size for restoring backup . 139 modifying . . . . . . . . . . . . . . . . . . . . . . . . . .2 name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 name (when several files) . . . . . . . . . . . 63 number of companies in . . . . . . . . . . . . 58 opening from within application . . . . . 65 opening with program property . . . . . 67 program property . . . . . . . . . . . . . . . . . 36 program property, on server . . . . . . . . 45 selecting . . . . . . . . . . . . . . . . . . . . . . . . . . 36 selecting during installation . . . . . . . . . 17 setting up for server . . . . . . . . . . . . . . . . 21 size . . . . . . . . . . . . . . . . . . . . . . . . . 2, 60, 74 size and application performance . . . . 61 size purchased . . . . . . . . . . . . . . . . . . . . 74 specifying on client when opening a database . . . . . . . . . . . . . . . . . . . . . . . . . 66 standard . . . . . . . . . . . . . . . . . . . . . . . 21, 63 status, checking . . . . . . . . . . . . . . . . . . . 73 testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 testing, backup function . . . . . . . . . . . 132 transferring single-user database to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 two or more servers . . . . . . . . . . . . . . . . 22 utilization . . . . . . . . . . . . . . . . . . . . . . . . . 77 Database File table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 database file creating an extra . . . . . . . . . . . . . . . . . . 62 expanding . . . . . . . . . . . . . . . . . . . . . . . . 62 Database Files window . . . . . . . . . . . . . . . 73 Database Information (Keys) window . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Database Information (Tables) window . 78 Database Information window . . . . . . . . . 73 Database Key Groups window . . . . . . . . . 79 database login assigning a role . . . . . . . . . . . . . . . . . . . 119 creating . . . . . . . . . . . . . . . . . . . . . 114, 115 definition . . . . . . . . . . . . . . . . . . . . . . . . 160 description . . . . . . . . . . . . . . . . . . . . . . . 110 expiration date . . . . . . . . . . . . . . . . . . . 115 giving a role to . . . . . . . . . . . . . . . . . . . 115 password . . . . . . . . . . . . . . . . . . . . . . . . 115 time-limited . . . . . . . . . . . . . . . . . . . . . 115 Database Logins window . . . . . . . . . . . . . . . . . . . . . . . . . 114 database name entering for new database . . . . . . . . . . 59

Index

specifying on client when opening a database . . . . . . . . . . . . . . . . . . . . . . . . . . 66 database server dedicated . . . . . . . . . . . . . . . . . . . . . . . . 161 definition . . . . . . . . . . . . . . . . . . . . . . . . 161 non-dedicated . . . . . . . . . . . . . . . . . . . . 162 database server authentication definition . . . . . . . . . . . . . . . . . . . . . . . . 161 Database Server Manager . . . . . . . . . . . . . 49 Database Sessions window . . . . . . . . . . . . 75 database test before application opens . . . . . . . . . . . . 41 custom . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 errors, handling . . . . . . . . . . . . . . . . . . . . 70 from within the program . . . . . . . . . . . . 68 levels . . . . . . . . . . . . . . . . . . . . . . . . . .41, 68 maximum . . . . . . . . . . . . . . . . . . . . . . . . . 69 minimum . . . . . . . . . . . . . . . . . . . . . . . . . 68 normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 unopened database . . . . . . . . . . . . . . . . 68 database.fdb (standard database) . . . . . . 58 date compression backing up database before . . . . . . . . . 81 batch jobs . . . . . . . . . . . . . . . . . . . . . . . . . 82 description . . . . . . . . . . . . . . . . . . . . . . . . 82 example . . . . . . . . . . . . . . . . . . . . . . .8485 options . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 result of . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 setting filters . . . . . . . . . . . . . . . . . . . . . . 83 starting . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 db read-only program property . . . . . . . . . . . . . . . . . . 44 DB test program property . . . . . . . . . . . . . . . . . . 41 DBMS definition . . . . . . . . . . . . . . . . . . . . . . . . 161 DBMS (Database Management System) cache allocation . . . . . . . . . . . . . . . . . . . . . . . . . 74 bottleneck, software level . . . . . . . . . . 155 maximum size . . . . . . . . . . . . . . . . . . . . 155 size required . . . . . . . . . . . . . . . . . . . . . . 155 swapping . . . . . . . . . . . . . . . . . . . . .46, 155 dedicated database server . . . . . . . . . . . . 161 dedicated server definition . . . . . . . . . . . . . . . . . . . . . . . . 161 delete (permission) . . . . . . . . . . . . . . . . . . 118 in Permissions window . . . . . . . . . . . . . 121 delfin.log see log file demonstration company . . . . . . . . . . . . . . 20 access to . . . . . . . . . . . . . . . . . . . . . . . . . . 86 CRONUS International Ltd. . . . . . . . . . . 58 naming . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 demonstration database . . . . . . . . . . . . . . . 2 demonstration license file cronus.flf . . . . . . . . . . . . . . . . . . . . . . . . . . 58 restrictions . . . . . . . . . . . . . . . . . 20, 58, 86 single user . . . . . . . . . . . . . . . . . . . . . .20, 86

DHCP (Dynamic Host Configuration Protocol), server . . . . . . . . . . . . . . . . . . . . 153 disk cache definition . . . . . . . . . . . . . . . . . . . . . . . . 161 DNS (Domain Name System), server . . . 153 domain definition . . . . . . . . . . . . . . . . . . . . . . . . 161 publishing Dynamics NAV Database Server in a . . . . . . . . . . . . . . . . . . . . . . . . 18 domain controller definition . . . . . . . . . . . . . . . . . . . . . . . . 161 domain tree definition . . . . . . . . . . . . . . . . . . . . . . . . 161 publishing Dynamics NAV Database Server in a . . . . . . . . . . . . . . . . . . . . . . . . 18 Dynamics NAV service connection point, adding definition to Active Directory . . . . . . . . 18 Dynamics NAV backup starting to restore . . . . . . . . . . . . . . . . 136 Dynamics NAV Database Server importing a database into . . . . . . . . . . 21 installing . . . . . . . . . . . . . . . . . . . . . . . . . 13 maintaining . . . . . . . . . . . . . . . . . . . . . . . 18 naming . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 publishing . . . . . . . . . . . . . . . . . . . . . . . . 18 renaming . . . . . . . . . . . . . . . . . . . . . . . . . 18 running as a service . . . . . . . . . . . . . 18, 48 selecting the network protocol . . . . . . 16 status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 updating . . . . . . . . . . . . . . . . . . . . . . . . . 18 Dynamics NAV Database Server Manager 49 Dynamics NAV security initiating . . . . . . . . . . . . . . . . . . . . . . . . . 114 E equipment, choosing . . . . . . . . . . . . . . . . . . .3 equipment, PC, choosing . . . . . . . . . . . . . . .3 errors in database . . . . . . . . . . . . . . . . . . . . . . . 70 transmission . . . . . . . . . . . . . . . . . . . . . . 60 execute (permission) . . . . . . . . . . . . . . . . 118 in Permissions window . . . . . . . . . . . . 121 Expand Database (Advanced) window . . 62 Expand Database window . . . . . . . . . . . . . 62 expanding a working database . . . . . . . . . . . . . . . . 88 Export License File window . . . . . . . . . . . . 87 F fbk, extension of backup file name . . . . 133 filter, on status bar . . . . . . . . . . . . . . . . . . . 42 fin.flf (license file) . . . . . . . . . . . . . . . . . . . . 58 forest definition . . . . . . . . . . . . . . . . . . . . . . . . 161 publishing Dynamics NAV Database Server in a . . . . . . . . . . . . . . . . . . . . . . . . 18

Index

H hard disk capacity . . . . . . . . . . . . . . . . . . . . . . . . . . 150 requirements . . . . . . . . . . . . . . . . 148, 149 speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 hardware optimization . . . . . . . . . . . . . . . . . . . . . . 148 selection . . . . . . . . . . . . . . . . . . . . . . . . . 149 hardware performance table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 header checksum . . . . . . . . . . . . . . . . . . . 138 hibernation . . . . . . . . . . . . . . . . . . . . . . . . . 106 conditions preventing . . . . . . . . . . . . . 106 restarting after . . . . . . . . . . . . . . . . . . . . 106 host name . . . . . . . . . . . . . . . . . . . . . . . . . . 162 HOSTS file . . . . . . . . . . . . . . . . . . . . . 153, 161 HotCopy backup description file . . . . . . . . 142, 144 command prompt parameters . 141, 142 output . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 restoring . . . . . . . . . . . . . . . . . . . . . . . . . 145 server based backup . . . . . . . . . . . . . . . 141 I ID, user changing . . . . . . . . . . . . . . . . . . . . . . . . . 124 ID, user setup program property . . . . . . . . . . . . . . . . . . 35 saving setup . . . . . . . . . . . . . . . . . . . . . . . 35 index, sorting key . . . . . . . . . . . . . . . . . . . . 69 Insert (INS), on status bar . . . . . . . . . . . . . . 42 insert (permission) . . . . . . . . . . . . . . . . . . . 118 in Permissions window . . . . . . . . . . . . . 121 Install as service description . . . . . . . . . . . . . . . . . . . . . . . . 48 entering on the command line . . . . . . . 53 install as service program property . . . . . . . . . . . . . . . . . . 48 installation cancelling . . . . . . . . . . . . . . . . . . . . . . . . . . 4 changing . . . . . . . . . . . . . . . . . . . . .2, 1011 changing, repairing and removing . . . . 10 client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 complete . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 custom . . . . . . . . . . . . . . . . . . . . . . . . 6, 69 custom, options . . . . . . . . . . . . . . . . . . . . . 9 expanding . . . . . . . . . . . . . . . . . . . . . . . . . . 2 license file . . . . . . . . . . . . . . . . . . . . . . . . . 17 minimum . . . . . . . . . . . . . . . . . . . . . . . . . . 5 multiuser . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 procedure, description . . . . . . . . . . . . . 49 rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 selecting database . . . . . . . . . . . . . . . . . . 17 server . . . . . . . . . . . . . . . . . . . . . . . . . .1318 server, maintaining . . . . . . . . . . . . . . . . . 18 single-user . . . . . . . . . . . . . . . . . . . . . . . 49 upgrading . . . . . . . . . . . . . . . . . . . . . . . . . 11

installation upgrade custom . . . . . . . . . . . . . . . . . . . . . . . . . . . new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . typical . . . . . . . . . . . . . . . . . . . . . . . . . . . . internal node, in tree structure . . . . . . . .

11 12 11 89

K key group . . . . . . . . . . . . . . . . . . . . . . . . . . 78 disabling . . . . . . . . . . . . . . . . . . . . . . . . . 80 setting up . . . . . . . . . . . . . . . . . . . . . . . . 79 keys changing sorting order . . . . . . . . . . . . . 69 deactivating or removing . . . . . . . . . . . 78 definition . . . . . . . . . . . . . . . . . . . . . . . . 162 information about . . . . . . . . . . . . . . . . . 78 predefined . . . . . . . . . . . . . . . . . . . . . . . . 78 primary . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 secondary . . . . . . . . . . . . . . . . . . . . . . . . 69 L lazy write caching system . . . . . . . . . . . . 150 lazy-write cache definition . . . . . . . . . . . . . . . . . . . . . . . . 162 leaf, in tree structure . . . . . . . . . . . . . . . . . 89 level 2 cache definition . . . . . . . . . . . . . . . . . . . . . . . . 162 License Agreement . . . . . . . . . . . . . . . . . 107 license agreement setup card . . . . . . 107 license file changing . . . . . . . . . . . . . . . . . . . . . . . . . 87 checking validity of . . . . . . . . . . . . . . . . 87 client . . . . . . . . . . . . . . . . . . . . . . . . . . 20, 86 cronus.flf . . . . . . . . . . . . . . . . . . . . . . 20, 86 demonstration, limitations on . . . . . . . 58 exporting . . . . . . . . . . . . . . . . . . . . . . . . . 87 fin.flf . . . . . . . . . . . . . . . . . . . . . . . 20, 58, 86 if it expires . . . . . . . . . . . . . . . . . . . . . . . . 87 importing . . . . . . . . . . . . . . . . . . . . . . . . . 86 installation . . . . . . . . . . . . . . . . . . . . . . . . 17 multiuser installation . . . . . . . . . . . . . . . 20 single user . . . . . . . . . . . . . . . . . . . . . . . . 20 your own . . . . . . . . . . . . . . . . . . . . . . . . . 58 License Information window . . . . . . . . . . 86 license number . . . . . . . . . . . . . . . . . . . . . . 86 Licensed Sessions . . . . . . . . . . . . . . . . . . . . 75 log file (delfin.log) . . . . . . . . . . . . . . . . . . . 11 log on, log off definition . . . . . . . . . . . . . . . . . . . . . . . . 162 login definition . . . . . . . . . . . . . . . . . . . . . . . . 110 M machine name HOSTS file . . . . . . . . . . . . . . . . . . . . . . . 153 network configuration program . . . . 153 marquee full selection program property . . . . . . . . . . . . . . . . . 43

Index

master checksum . . . . . . . . . . . . . . . . . . . . 138 memory computer . . . . . . . . . . . . . . . . . . . . . . . . 162 ECC (Error Correction Code) type . . . . 151 requirements . . . . . . . . . . . . . . . . . . . . . 151 Microsoft Dynamics NAV Outlook Integration . . . . . . . . . . . . .25, 94 Microsoft Management Console . . . . . . . 49 MMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 modify (permission) . . . . . . . . . . . . . . . . . 118 in Permissions window . . . . . . . . . . . . . 121 multiuser installation definition . . . . . . . . . . . . . . . . . . . . . . . . 162 described . . . . . . . . . . . . . . . . . . . . . . . . . 32 description . . . . . . . . . . . . . . . . . . . . . . 2, 32 installation of single user . . . . . . . . . . . . . 2 N name backup file . . . . . . . . . . . . . . . . . . . . . . . 133 database . . . . . . . . . . . . . . . . . . . . . . . . . . 73 database (when several files) . . . . . . . . . 63 database, specifying on client when opening a database . . . . . . . . . . . . . . . . 66 printer . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 server, specifying on client when creating database . . . . . . . . . . . . . . . . . . . . . . . . . . 59 server, specifying on client when opening database . . . . . . . . . . . . . . . . . . . . . . . . . . 65 user, changing . . . . . . . . . . . . . . . . . . . . 124 net tests, network optimization . . . . . . . 157 net type program property, on client . . . . . . . . . 40 program property, on server . . . . . . . . . 45 program property, specifying on client 66 NetBIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 network protocol . . . . . . . . . . . . . . . . . . 152 network adapter, requirements . . 148, 151 network configuration program, machine name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 network optimization, net tests . . . . . . . 157 network protocol advantages and disadvantages . . . . . . 153 checking . . . . . . . . . . . . . . . . . . . . . . . . . . 74 definition (under NetBIOS) . . . . . . . . . 162 NetBIOS . . . . . . . . . . . . . . . . . . . . . . . . . 152 requirements . . . . . . . . . . . . . . . . . . . . . 148 selecting during installation . . . . . . . . . 16 TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 TCPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 network server definition . . . . . . . . . . . . . . . . . . . . . . . . 162 network type selecting during installation . . . . . . . . . 16 New Database window . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 new database naming . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

specifying size of . . . . . . . . . . . . . . . . . . 60 new users creating, database login . . . . . . . . . . . 114 creating, Windows login . . . . . . . . . . . 117 NEW, on status bar . . . . . . . . . . . . . . . . . . 42 node, in tree structure . . . . . . . . . . . . . . . . 89 non-dedicated database server definition . . . . . . . . . . . . . . . . . . . . . . . . 162 O object definition . . . . . . . . . . . . . . . . . . . . . . . . 121 permissions . . . . . . . . . . . . . . . . . . . . . . 121 types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 object cache allocation . . . . . . . . . . . . . . . . . . . . . . . . . 74 bottleneck, software level . . . . . . . . . . 155 definition . . . . . . . . . . . . . . . . . . . . . . . . 162 memory requirements . . . . . . . . . . . . . 163 program property . . . . . . . . . . . . . . . . . 39 size required . . . . . . . . . . . . . . . . . . . . . 156 object cache (program property) performance . . . . . . . . . . . . . . . . . . . . . . 39 setting size of . . . . . . . . . . . . . . . . . . . . . 39 objects, list of those with permissions . . 122 Open Database window . . . . . . . . . . . . . . 65 operating system for client/single user . . . . . . . . . . . . . . . . .3 for server . . . . . . . . . . . . . . . . . . . . . . . . . . .3 requirements . . . . . . . . . . . . . . . . . . . . . 152 selection . . . . . . . . . . . . . . . . . . . . . . . . . 149 optimistic concurrency . . . . . . . . . . . . . . . 91 Outlook Integration C/FRONT . . . . . . . . . . . . . . . . . . . . . . . . . 98 in Microsoft Dynamics NAV . . . . . . 25, 94 installation . . . . . . . . . . . . . . . . . . . . . . . . 26 settings window . . . . . . . . . . . . . . . . . . . 96 setup in Microsoft Dynamics NAV . . . . 94 synchronization progress window . . . 103 synchronization toolbar setup . . . . . . . 96 troubleshooting window . . . . . . . . . . . 101 Overtype (OVR), on status bar . . . . . . . . . 42 P password changing . . . . . . . . . . . . . . . . . . . . . . . . 124 entering . . . . . . . . . . . . . . . . . . . . . . . . . . 66 entering when creating database login . . 115 if lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 security . . . . . . . . . . . . . . . . . . . . . . . . . . 110 PC, choice of . . . . . . . . . . . . . . . . . . . . . . . . . .3 Performance Monitor . . . . . . . . . . . 156, 157 Performance table . . . . . . . . . . . . . . . . . . 156 permissions adding users . . . . . . . . . . . . . . . . . . . . . 119 creating new roles . . . . . . . . . . . . . . . . 118 delete . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Index

deleting . . . . . . . . . . . . . . . . . . . . . . . . . . 118 execute . . . . . . . . . . . . . . . . . . . . . 118, 121 FlowFields . . . . . . . . . . . . . . . . . . . . . . . . 118 for objects . . . . . . . . . . . . . . . . . . . . . . . . 121 giving a role to a database login . . . . 116 giving a role to a user . . . . . . . . . . . . . . 116 giving to existing users . . . . . . . . . . . . . 119 granting to users . . . . . . . . . . . . . . . . . . 117 groups, description . . . . . . . . . . . . . . . . 113 indirect, definition . . . . . . . . . . . . . . . . . 121 insert . . . . . . . . . . . . . . . . . . . . . . . 118, 121 limiting posting periods . . . . . . . . . . . . 125 modify . . . . . . . . . . . . . . . . . . . . . . 118, 121 modifying for a role . . . . . . . . . . . . . . . 120 modifying for individual objects . . . . . 120 modifying for multiple objects . . . . . . 122 read . . . . . . . . . . . . . . . . . . . . . . . . 118, 121 restricting to specific companies . . . . 116 standard . . . . . . . . . . . . . . . . . . . . . . . . . 117 standard, list of . . . . . . . . . . . . . . . . . . . 120 superuser . . . . . . . . . . . . . . . . . . . . . . . . 115 time-limited . . . . . . . . . . . . . . . . . . . . . . 113 to multiple objects, granting . . . . . . . . 122 types of . . . . . . . . . . . . . . . . . . . . . 118, 121 who can administer . . . . . . . . . . . . . . . . 114 Permissions (All Objects) window . . . . . . 122 Permissions window . . . . . . . . . . . . . . . . . 120 PING command, TCP/IP . . . . . . . . . . . . . . 153 posting limiting periods . . . . . . . . . . . . . . . . . . . 125 time limits for users . . . . . . . . . . . 113, 125 printer name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 selecting see printer selection printer selection default . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 description . . . . . . . . . . . . . . . . . . . . . . . 128 fixed . . . . . . . . . . . . . . . . . . . . . . . . 113, 128 printer name . . . . . . . . . . . . . . . . . . . . . 128 report ID . . . . . . . . . . . . . . . . . . . . . . . . . 128 report name . . . . . . . . . . . . . . . . . . . . . . 128 user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 program properties for clients, description . . . . . . . . . . . . . . 35 for server, list of . . . . . . . . . . . . . . . . . . . . 45 specifying in target field . . . . . . . . .5355 table of . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 program property authentication . . . . . . . . . . . . . . . . . . . . . 38 cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 close forms on Esc . . . . . . . . . . . . . . . . . . 43 commit cache, client and single-user . 39 commit cache, for server . . . . . . . . . . . . 45 company . . . . . . . . . . . . . . . . . . . . . . . . . . 37 database . . . . . . . . . . . . . . . . . . . . . . . . . . 36 database, on server . . . . . . . . . . . . . . . . . 45 db read-only . . . . . . . . . . . . . . . . . . . . . . 44 DB test . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

defining in command line . . . . . . . . . . . 54 definition . . . . . . . . . . . . . . . . . . . . . . . . 163 ID, user setup . . . . . . . . . . . . . . . . . . . . . 35 install as service . . . . . . . . . . . . . . . . . . . 48 marquee full selection . . . . . . . . . . . . . . 43 net type, on client . . . . . . . . . . . . . . . . . 40 net type, on server . . . . . . . . . . . . . . . . . 45 object cache . . . . . . . . . . . . . . . . . . . . . . 39 quick find . . . . . . . . . . . . . . . . . . . . . . . . . 44 server name, on client . . . . . . . . . . . . . . 36 server name, on server . . . . . . . . . . . . . 45 sessions . . . . . . . . . . . . . . . . . . . . . . . . . . 47 status bar . . . . . . . . . . . . . . . . . . . . . . . . . 42 stoptime . . . . . . . . . . . . . . . . . . . . . . . . . . 46 temppath . . . . . . . . . . . . . . . . . . . . . . . . . 40 testtarget . . . . . . . . . . . . . . . . . . . . . . . . . 41 uninstall as service . . . . . . . . . . . . . . . . . 49 protocol definition . . . . . . . . . . . . . . . . . . . . . . . . 163 selection . . . . . . . . . . . . . . . . . . . . . . . . . 149 protocol, see network protocol . . . . . . . 163 publishing Dynamics NAV Database Server . . . . . 18 Purchase Responsibility Center filter user setup . . . . . . . . . . . . . . . . . . . . . . . 126 Q quick find program property . . . . . . . . . . . . . . . . . 44 R RAID definition . . . . . . . . . . . . . . . . . . . . . . . . 163 requirements . . . . . . . . . . . . . . . . . . . . . 148 system, configurations . . . . . . . . . . . . . 151 system, controller . . . . . . . . . . . . . . . . . 150 read consistency . . . . . . . . . . . . . . . . . . . . . . . 91 permission . . . . . . . . . . . . . . . . . . . . . . . 118 read (permission) in Permissions window . . . . . . . . . . . . 121 registering time use . . . . . . . . . . . . . . . . . 113 reinstalling server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Restore window . . . . . . . . . . . . . . . . . . . . . . . . . 136 Restore window . . . . . . . . . . . . . . . . . . . . . 64 restore, advanced information . . . . . . . . 138 restoring a backup all companies . . . . . . . . . . . . . . . . . . . . 137 constraints . . . . . . . . . . . . . . . . . . . . . . . 138 custom . . . . . . . . . . . . . . . . . . . . . . . . . . 137 entire . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 example . . . . . . . . . . . . . . . . . . . . . . . . . 139 extent . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 limiting extent . . . . . . . . . . . . . . . . . . . . 137 minimum size of database . . . . . . . . . 139 monitoring . . . . . . . . . . . . . . . . . . . . . . . 65 problems . . . . . . . . . . . . . . . . . . . . . . . . 139

Index

procedure . . . . . . . . . . . . . . . . . . . 136137 using built-in function . . . . . . . . . . . . . 136 using other restore functions . . . . . . . 136 role creating a new . . . . . . . . . . . . . . . . . . . . 118 definition . . . . . . . . . . . . . . . . . . . . . . . . 163 entering ID . . . . . . . . . . . . . . . . . . . . . . . 118 giving to database logins . . . . . . 115, 119 giving to users . . . . . . . . . . . . . . . . . . . . 115 giving to Windows group . . . . . . . . . . 123 giving to Windows logins . . . . . . . . . . 119 giving to Windows Users and Groups 122 modifying permissions for . . . . . . . . . . 120 users linked to . . . . . . . . . . . . . . . . . . . . 119 Roles window . . . . . . . . . . . . . . . . . . . . . 116, 119 roles list of . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 rollback definition . . . . . . . . . . . . . . . . . . . . . . . . 163 of the installation . . . . . . . . . . . . . . . . . . . 4 of the uninstallation . . . . . . . . . . . . . . . . 10 root, in tree structure . . . . . . . . . . . . . . . . . 89 S Sales Responsibility Center filter user setup . . . . . . . . . . . . . . . . . . . . . . . . 126 schema definition . . . . . . . . . . . . . . . . . . . . . . . . 163 schema extension adding to Active Directory . . . . . . . . . . . 18 security additional features provided by Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . 122 creating new roles . . . . . . . . . . . . . . . . . 118 FlowFields . . . . . . . . . . . . . . . . . . . . . . . . 118 level of . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 security updates . . . . . . . . . . . . . . . . . . . 29 seek time, optimizing . . . . . . . . . . . . . . . . . 80 server automatic connection to . . . . . . . . . . . . 54 automatic timed stop . . . . . . . . . . . . . . . 46 computer requirements . . . . . . . . . . . . . . 3 connecting to . . . . . . . . . . . . . . . . . . . . . . 36 dedicated . . . . . . . . . . . . . . . . . . . . . . . . 161 definition . . . . . . . . . . . . . . . . . . 2, 32, 163 DHCP (Dynamic Host Configuration Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . 153 different databases . . . . . . . . . . . . . . . . . 22 DNS (Domain Name System) . . . . . . . 153 installation . . . . . . . . . . . . . . . . . . . . .1318 installation, maintaining . . . . . . . . . . . . . 18 naming . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 network . . . . . . . . . . . . . . . . . . . . . . . . . . 162 non-dedicated . . . . . . . . . . . . . . . . . . . . 162 operating system . . . . . . . . . . . . . . . . . . . . 3 reinstalling . . . . . . . . . . . . . . . . . . . . . . . . 18 renaming . . . . . . . . . . . . . . . . . . . . . . . . . 18

selecting . . . . . . . . . . . . . . . . . . . . . . . . . . 36 specifying in Target field . . . . . . . . . . . . 54 specifying on client when creating a database . . . . . . . . . . . . . . . . . . . . . . . . . 59 specifying on client when opening a database . . . . . . . . . . . . . . . . . . . . . . . . . 65 starting . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 updating . . . . . . . . . . . . . . . . . . . . . . . . . 18 server based backup see HotCopy Server Manager . . . . . . . . . . . . . . . . . . . . . 49 server name designating . . . . . . . . . . . . . . . . . . . . . . . 15 program property, on client . . . . . . . . . 36 program property, on server . . . . . . . . 45 specifying on client when creating database . . . . . . . . . . . . . . . . . . . . . . . . . 59 specifying on client when opening database . . . . . . . . . . . . . . . . . . . . . . . . . 65 server package . . . . . . . . . . . . . . . . . . . . . . . .2 server program, installing . . . . . . . . . . . . . 21 service connection point definition . . . . . . . . . . . . . . . . . . . . . . . . 163 Dynamics NAV . . . . . . . . . . . . . . . . . . . . 18 Service Packs . . . . . . . . . . . . . . . . . . . . . . . . 29 session, definition . . . . . . . . . . . . . . . . . . . 163 sessions current number of . . . . . . . . . . . . . . . . . 75 description . . . . . . . . . . . . . . . . . . . . . . . . 47 number allowed . . . . . . . . . . . . . . . . 47, 75 program property . . . . . . . . . . . . . . . . . 47 terminating . . . . . . . . . . . . . . . . . . . . . . . 75 setup definition . . . . . . . . . . . . . . . . . . . . . . . . 164 fixed printer selection . . . . . . . . . . . . . 128 single-user . . . . . . . . . . . . . . . . . . . . . . . . 35 setup file, see zup file . . . . . . . . . . . . . . . . 32 single sign-on definition . . . . . . . . . . . . . . . . . . . . . . . . 164 support of . . . . . . . . . . . . . . . . . . . . . . . 110 single-user computer requirements . . . . . . . . . . . . . .3 converting to client . . . . . . . . . . . . . . . . . .6 definition . . . . . . . . . . . . . . . . . . . . . . 2, 164 in multiuser installation . . . . . . . . . . . . . . .2 installing . . . . . . . . . . . . . . . . . . . . . . . . 49 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 single-user installation description . . . . . . . . . . . . . . . . . . . . . . . . 32 SMS (System Management Server) . . . . . 27 package definition files . . . . . . . . . . . . . 27 snap-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 sorting keys, predefined . . . . . . . . . . . . . . 78 sorting order . . . . . . . . . . . . . . . . . . . . . . . . 69 space allocation in database testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 standard database . . . . . . . . . . . . . . . . . . . 21 database.fdb . . . . . . . . . . . . . . . . . . . . . . 58 restoring . . . . . . . . . . . . . . . . . . . . . . . . . 63

Index

restoring a backup . . . . . . . . . . . . . . . . . 59 standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 conditions preventing . . . . . . . . . . . . . 106 restarting after . . . . . . . . . . . . . . . . . . . . 106 start command . . . . . . . . . . . . . . . . . . . . . . . 54 Start in field start command . . . . . . . . . . . . . . . . . . . . 54 status Dynamics NAV Database Server . . . . . . 51 status bar program property . . . . . . . . . . . . . . . . . . 42 stoptime closing a database . . . . . . . . . . . . . . . . . . 67 description . . . . . . . . . . . . . . . . . . . . . . . . 46 program property . . . . . . . . . . . . . . . . . . 46 superuser definition . . . . . . . . . . . . . . . . . . . . . . . . 115 granting permissions . . . . . . . . . . . . . . 115 setting up . . . . . . . . . . . . . . . . . . . . . . . . 115 swapping definition . . . . . . . . . . . . . . . . . . . . . . . . 164 swapping, DBMS (Database Management System) cache . . . . . . . . . . . . . . . . . . .46, 155 Synchronization . . . . . . . . . . . . . . . . . . . . . . 96 T table finding errors in . . . . . . . . . . . . . . . . . . . . 81 optimizing . . . . . . . . . . . . . . . . . . . . .80, 89 Table Information - Sort window . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 table seek time improving . . . . . . . . . . . . . . . . . . . . . . . . . 80 tables in database . . . . . . . . . . . . . . . . . . . . 77 Target field definition . . . . . . . . . . . . . . . . . . . . . . . . 164 program properties . . . . . . . . . . . . . . . . . 54 specifying company . . . . . . . . . . . . . . . . 54 specifying server . . . . . . . . . . . . . . . . . . . 54 TCP/IP network protocol . . . . . . . . . . . . . . . . . . 152 PING command . . . . . . . . . . . . . . . . . . . 153 TCPS network protocol . . . . . . . . . . . . . . . . . . 152 two servers . . . . . . . . . . . . . . . . . . . . . . . . 22 temporary files, location . . . . . . . . . . . . . . . 40 temppath (program property) . . . . . . . . . 40 Test Database window . . . . . . . . . . . . . . . . 68 Test Space Allocation . . . . . . . . . . . . . . . . . 69 Test Tables window . . . . . . . . . . . . . . . . . . . 81 testtarget program property . . . . . . . . . . . . . . . . . . 41 time limits for company . . . . . . . . . . . . . . . . . . . . . . 126 on posting . . . . . . . . . . . . . . . . . . 113, 125 on user IDs . . . . . . . . . . . . . . . . . . 113, 125

time use, registering . . . . . . . . 113, 125, 126 time used, on user IDs . . . . . . . . . . . . . . . 125 time-limited permissions . . . . . . . . . . . . . 113 transmission errors . . . . . . . . . . . . . . . . . . . 60 tree structure . . . . . . . . . . . . . . . . . . . . . . . 80 U uninstall as service description . . . . . . . . . . . . . . . . . . . . . . . . 49 entering on the command line . . . . . . 53 program property . . . . . . . . . . . . . . . . . 49 uninstalling Dynamics NAV . . . . . . . . . . . . . . . . . . . . 10 rollback . . . . . . . . . . . . . . . . . . . . . . . . . . 10 updating server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 upgrading the installation . . . . . . . . . . . . 11 user ID and user setup file . . . . . . . . . . . . . . . . . 33 changing . . . . . . . . . . . . . . . . . . . . . . . . 124 creating . . . . . . . . . . . . . . . . . . . . . . . . . 115 current displayed on status bar . . . . . 113 displayed on status bar . . . . . . . . . . . . 127 entering . . . . . . . . . . . . . . . . . . . . . . . . . . 66 if lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 logging time used . . . . . . . . . . . . . . . . 125 of super user . . . . . . . . . . . . . . . . . . . . . 115 on G/L entries . . . . . . . . . . . . . . . . 113, 127 time-limited . . . . . . . . . . . . . . . . . 113, 125 user name changing . . . . . . . . . . . . . . . . . . . . . . . . 124 when creating database login . . . . . . 115 User Setup window . . . . . . . . . . . . . . . . . . . . . . . . . 125 user setup Purchase Responsibility Center filter . 126 Sales Responsibility Center filter . . . . 126 user setup file creating . . . . . . . . . . . . . . . . . . . . . . . . . . 35 individual . . . . . . . . . . . . . .42, 43, 113, 127 location . . . . . . . . . . . . . . . . . . . . . . . . . . 33 returning to original . . . . . . . . . . . . . . . 35 saving . . . . . . . . . . . . . . . . . . . . . . . . . 33, 35 User Time Registers window . . . . . . . . . . 126 user time, registering . . . . . . . . 113, 125, 126 W window Advanced . . . . . . . . . . . . . . . . . . . . . . . . . 66 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . 132 backup function, status . . . . . . . . . . . . 134 Change Password . . . . . . . . . . . . . . . . . 124 Custom Setup . . . . . . . . . . . . . . . . . . . . . . .8 Database Files . . . . . . . . . . . . . . . . . . . . . 73 Database Information . . . . . . . . . . . . . . 73 Database Information (Keys) . . . . . . . . 78 Database Information (Tables) . . . . . . . 78 Database Key Groups . . . . . . . . . . . . . . 79 Database Logins . . . . . . . . . . . . . . . . . . 114

Index

Database Sessions . . . . . . . . . . . . . . . . . . 75 Expand Database . . . . . . . . . . . . . . . . . . . 62 Expand Database (Advanced) . . . . . . . . 62 Export License File . . . . . . . . . . . . . . . . . . 87 License Information . . . . . . . . . . . . . . . . 86 New Database . . . . . . . . . . . . . . . . . . . . . 59 Open Database . . . . . . . . . . . . . . . . . . . . 65 Permissions . . . . . . . . . . . . . . . . . . . . . . . 120 Permissions (All Objects) . . . . . . . . . . . 122 Restore . . . . . . . . . . . . . . . . . . . . . . .64, 136 Roles . . . . . . . . . . . . . . . . . . . . . . . 116, 119 Table Information - Sort . . . . . . . . . . . . . 78 Test Database . . . . . . . . . . . . . . . . . . . . . . 68 Test Tables . . . . . . . . . . . . . . . . . . . . . . . . 81 User Setup . . . . . . . . . . . . . . . . . . . . . . . 125 User Time Registers . . . . . . . . . . . . . . . . 126 Windows Logins . . . . . . . . . . . . . 119, 123 Windows Users and Groups . . . . . . . . . 117 Windows authentication definition . . . . . . . . . . . . . . . . . . . . . . . . 164 Windows group giving a role to . . . . . . . . . . . . . . . . . . . 123 Windows login assigning a role . . . . . . . . . . . . . . . . . . . 119 creating . . . . . . . . . . . . . . . . . . . . . . . . . . 117 definition . . . . . . . . . . . . . . . . . . . . . . . . 164 description . . . . . . . . . . . . . . . . . . . . . . . 110 Windows Logins window . . . . . . . . . . . . . . . . . . . . . 119, 123 Windows Users and Groups giving a role . . . . . . . . . . . . . . . . . . . . . . 122 window . . . . . . . . . . . . . . . . . . . . . . . . . . 117 write back system . . . . . . . . . . . . . . . . . . . 150 Z zup file each user has their own file . . . . . . . . . . 32 returning to original . . . . . . . . . . . . . . . . 35 sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Index