na2009 enus ic

INSTALLATION AND CONFIGURATION IN MICROSOFT DYNAMICS® NAV 2009

Microsoft Official Training Materials for Microsoft Dynamics ® Your use of this content is subject to your current services agreement

December 2008 The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. 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. © 2008 Microsoft Corporation. All rights reserved. Microsoft and Solomon are either trademarks or registered trademarks of Microsoft Corporation or Dynamics NAV Software, Inc. or their affiliates in the United States and/or other countries. Dynamics NAV Software, Inc. is a subsidiary of Microsoft Corporation. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.


Table of Contents

i

Introduction 0-1

Welcome ............................................................................................................ 0-1 Microsoft Dynamics Courseware Contents ........................................................ 0-2 Documentation Conventions .............................................................................. 0-3 Student Objectives ............................................................................................. 0-4

Chapter 1: Architecture 1-1

Objectives ........................................................................................................... 1-1 Introduction ......................................................................................................... 1-1 Microsoft Dynamics NAV 5.0 Architecture.......................................................... 1-2 Microsoft Dynamics NAV 2009 Architecture....................................................... 1-3 Three-Tiers on Three-Computers ....................................................................... 1-7 Summary .......................................................................................................... 1-12 Test Your Knowledge ....................................................................................... 1-13 Quick Interaction: Lessons Learned ................................................................. 1-14 Solutions ........................................................................................................... 1-15

Chapter 2: Installation Requirements 2-1

Objectives ........................................................................................................... 2-1 Introduction ......................................................................................................... 2-1 Software Prerequisites of Microsoft Dynamics NAV ........................................... 2-2 Microsoft Windows Server .................................................................................. 2-3 Microsoft SQL Server ......................................................................................... 2-7 SQL Server 2005 Editions .................................................................................. 2-8 Summary .......................................................................................................... 2-10 Quick Interaction: Lessons Learned ................................................................. 2-11

Chapter 3: RoleTailored Client Install 3-1

Objectives ........................................................................................................... 3-1 Introduction ......................................................................................................... 3-1 Install Dynamics NAV Demo Version on a Single Computer ............................. 3-2 Install Dynamics NAV 2009 Clients on a Network .............................................. 3-4 Start the RoleTailored Client .............................................................................. 3-6 Lab 3.1 - Installing Microsoft Dynamics NAV 2009 Clients .............................. 3-15 Summary .......................................................................................................... 3-17 Quick Interaction: Lessons Learned ................................................................. 3-18

Chapter 4: RoleTailored Client Personalization 4-1

Objectives ........................................................................................................... 4-1 Introduction ......................................................................................................... 4-1 Customize the Navigation Pane ......................................................................... 4-2 Customize Pages ............................................................................................... 4-7 Lab 4.1 - Adding a Vendor List to the Role Center ........................................... 4-14 Summary .......................................................................................................... 4-15 Quick Interaction: Lessons Learned ................................................................. 4-16

Chapter 5: Database Server 5-1

Objectives ........................................................................................................... 5-1


Installation and Configuration in-Microsoft Dynamics® NAV 2009

ii

Introduction ......................................................................................................... 5-1 NAV Server Setup .............................................................................................. 5-2 Server Configuration During Setup .................................................................... 5-4 NAV Server Configuration After Setup ............................................................... 5-6 Lab 5.1 - Editing the Configuration file for the NAV Server ................................ 5-9 Summary .......................................................................................................... 5-10 Quick Interaction: Lessons Learned ................................................................. 5-11

Chapter 6: Classic Client Option 6-1

Objectives ........................................................................................................... 6-1 Introduction ......................................................................................................... 6-1 Requirements ..................................................................................................... 6-2 Classic Client Installation ................................................................................... 6-2 The Developer Environment Option ................................................................... 6-3 Summary ............................................................................................................ 6-4 Quick Interaction: Lessons Learned ................................................................... 6-5

Chapter 7: Deployment 7-1

Objectives ........................................................................................................... 7-1 Introduction ......................................................................................................... 7-1 Deployment Process .......................................................................................... 7-2 Deploy Microsoft Dynamics NAV 2009............................................................... 7-3 Summary .......................................................................................................... 7-17 Quick Interaction: Lessons Learned ................................................................. 7-18

Chapter 8: Optimization and Troubleshooting 8-1

Objectives ........................................................................................................... 8-1 Introduction ......................................................................................................... 8-1 Microsoft Dynamics NAV 2009 Troubleshooting ................................................ 8-2 Database Performance Troubleshooting ............................................................ 8-2 Troubleshooting Software Deployed with Group Policy ................................... 8-15 Lab 8.1 - Use SQL Server Profiler to configure a baseline trace ...................... 8-21 Lab 8.2 - Configure a System Monitor Counter Log ......................................... 8-23 Lab 8.3 - Analyzing a Workload in DTA............................................................ 8-24 Quick Interaction: Lessons Learned ................................................................. 8-26


Introduction

0 - 1

INTRODUCTION Welcome

We know training is a vital component of retaining the value of your Microsoft Dynamics® NAV 2009 investment. Our quality training from industry experts keeps you up-to-date on your solution and helps you develop the skills necessary for fully maximizing the value of your solution. Whether you choose Online Training, Classroom Training, or Training Materials; there is a type of training to meet everyone's needs. Choose the training type that best suits you so you can stay ahead of the competition.

Online Training Online Training delivers convenient, in-depth training to you in the comfort of your own home or office. Online training provides immediate access to training 24 hours-a-day. It is perfect for the customer who does not have the time or budget to travel. Our newest online training option, eCourses, combine the efficiency of online training with the in-depth product coverage of classroom training, with at least two weeks to complete each course.

Classroom Training Classroom Training provides serious, in-depth learning through hands-on interaction. From demonstrations to presentations to classroom activities, you receive hands-on experience with instruction from our certified staff of experts. Regularly scheduled throughout North America, you can be sure you will find a class convenient for you.

Training Materials Training Materials enable you to learn at your own pace, on your own time with information-packed training manuals. Our wide variety of training manuals feature an abundance of tips, tricks, and insights you can refer to again and again:

Microsoft Dynamics Courseware The Microsoft Dynamics Courseware consists of detailed training manuals, designed from a training perspective. These manuals include advanced topics as well as training objectives, exercises, interactions and quizzes. Look for a complete list of manuals available for purchase on the Microsoft Dynamics website: www.microsoft.com/Dynamics.


Installation and Configuration in Microsoft Dynamics® NAV 2009

0 - 2

Microsoft Dynamics Courseware Contents Test Your Skills Within the Microsoft Dynamics Training Materials you find a variety of different exercises. These exercises are offered in three levels to accommodate the variety of knowledge and expertise of each student. We suggest you try the level three exercises first, if you need help completing the task look to the information in the level two exercises. If you need further assistance each step of the task is outlined in the level one exercise.

Challenge Yourself! Level 3 exercises are the most challenging. These exercises are designed for the experienced student who requires little instruction to complete the required task.

Need a Little Help? Level 2 exercises are designed to challenge students, while providing some assistance. These exercises do not provide step by step instructions, however, do provide you with helpful hints and more information to complete the exercise.

Step by Step Level 1 exercises are geared towards new users who require detailed instructions and explanations to complete the exercise. Level 1 exercises guide you through the task, step by step, including navigation.

Quick Interaction: Lessons Learned At the end of each chapter within the Microsoft Dynamics Training Material, you find a Quick Interaction: Lessons Learned page. This interaction is designed to provide the student with a moment to reflect on the material they have learned. By outlining three key points from the chapter, the student is maximizing knowledge retention, and providing themselves with an excellent resource for reviewing key points after class.


Introduction

0 - 3

Documentation Conventions The following conventions and icons are used throughout this documentation to help you quickly and effectively navigate through the information. CAUTION: Cautions are found throughout the training manual and are preceded by the word CAUTION in bold. Cautions are used to remind you of a specific result of a specific action which may be undesirable.

HINT: Hints are found throughout the training manual and are preceded by the word HINT in bold. Hints are used to suggest time-saving features or alternative methods for accomplishing a specific task.

NOTE: Notes are found throughout the training manual and are preceded by the word NOTE in bold. Notes are used to provide information which, while not critical, may be valuable to an end user.

BEYOND THE BASICS: Advanced information found throughout the training manual is preceded by the words BEYOND THE BASICS in bold. Beyond the Basics provides additional detail, outside of standard functionality, that may help you to more optimally use the application.

EXAMPLE: Examples are found throughout the training manual and are preceded by the word EXAMPLE in bold. Examples bring to light business scenarios that may better explain how an application can be used to address a business problem.



0 - 4

Student Objectives What do you hope to learn by participating in this course? List three main objectives below. 1.

2.

3.


Chapter 1: Architecture

1-1

CHAPTER 1: ARCHITECTURE Objectives

The objectives are:

• Review the Microsoft Dynamics® NAV 5.0 Architecture • Understand the Microsoft Dynamics NAV 2009 Architecture • Install Microsoft Dynamics NAV 2009 three-tier architecture on

three computers

Introduction Microsoft Dynamics NAV 2009 is built on a three-tier architecture model. This differs significantly from the two-tier architecture of Microsoft Dynamics NAV 5.0.

Microsoft Dynamics NAV 2009 introduces a new layer in the architecture. This additional layer, or tier, is designed to host and execute all the business logic. In the two-tier architecture of Microsoft Dynamics NAV 5.0, the business logic resides at the client layer.

It improves security to execute the business logic on another layer that does not provide an interface, or access point, to the user. Scalability is also improved in the three-tier architecture.



1-2

Microsoft Dynamics NAV 5.0 Architecture Two-tier architecture models are used in the true Client/Server Distributed Data solution. In two-tier architectures, the data and data manipulation layers reside on the server, whereas the application logic, presentation logic, and presentation layers reside on the client.

Microsoft Dynamics NAV 5.0 is designed according to the two-tier architecture model. It puts the application logic (Business Logic) and presentation logic/layers (User Interface) on the client computer.

The two-tier architecture also puts the data and data manipulation layers (DML) on the server in the native database and SQL Server configurations.

FIGURE 1.1 THE MICROSOFT DYNAMICS NAV 5.0 ARCHITECTURE



1-3

The Client Tier

The C/Side Client is located on the client tier. It consists of an administration component for administrators and Microsoft Dynamics NAV 4.0/5.0 super users and client access for the C/Side client user.

Additionally, the client tier has specific connections for data transfer to the server tier and the database management component. These connections consist of the client, security approved access to the database components on the server tier, and administration access to the database management

The Server Tier

The server tier consists of the database management system and the native database for Microsoft Dynamics NAV 4.0/5.0 or the Microsoft® SQL Server®

database.

The existing application server or Navision Application Server (NAS) is an integration point to the Microsoft Dynamics NAV 4.0/5.0 application. Therefore it enables connection to Microsoft® BizTalk Server®, for example. The Navision Application Server represents an effort to achieve three-tier architecture benefits. However, it is limited to only one process at a time. Therefore, multiple Navision Application Servers are needed for many production environments.

Microsoft Dynamics NAV 2009 Architecture The three-tier architecture is used in the Client/Server Distributed Data and Application system. With this architecture, in which the data and data manipulation layers are put on their own servers, the application logic is put on its own server, and the presentation and presentation logic are put on the client computer.

Microsoft Dynamics NAV 2009 is designed according to the three-tier architecture model.

• This version puts the presentation logic/ layers (User Interface) on the client computer.

• It puts the Business logic on another layer available in the three-tier architecture called the service tier.

• It puts the data and data manipulation layers (DML) on the database server tier.

The Microsoft Dynmics NAV 2009, three -tier architecture and the classic two-tier architecture are not mutually exclusive. The Classic client remains an essential component for developing and administering Dynamics NAV applications. (For example, you must use the Classic client to upload your Microsoft Dynamics NAV 2009 license file.)



1-4

But once administrators or Microsoft Certified Partners roll out an implementation to a customer, end-users only see and use the RoleTailored client, which interacts with the other RoleTailored components.

The three-tier architecture is multithreaded so that it can handle more than one process at a time. This architecture overcomes the intrinsic limitations of the two-tier architecture.

• The first tier of the architecture is the client. • The second tier is the multithreaded middle tier. This is the service

tier that is based on Web services. • The third tier is where the SQL Server database resides.

FIGURE 1.2 THE MICROSOFT DYNAMICS NAV 2009 ARCHITECTURE



1-5

The Client Tier consists of the following components:

• The Microsoft Business Framework (MBF) is located on the client tier. The Client is built on Microsoft Windows Forms (Winforms) technology for smart client applications.

• Microsoft Windows Forms is the set of classes in the .NET Framework that enables the rapid development of powerful smart client applications. This logical form is a device independent representation of forms/UI parts and Web parts.

• The User Interface (UI) in the client determines the User Experience (UX) for the user. Content is delivered to the client from the data binder layer in MBF. It will be possible for end-users to customize their user experience.

• The Data Binder consists of the data binding layer which transports data, data state, and notifications about data from the underlying business logic to forms and controls in the display target client. It also has reverse functionality and transports input data, data state and notifications from the client to the underlying business logic.

• The Form Builder requests reading metadata for a form and building a logical form with data-binding, controls and behavior. The logical form provides the functionality that is shared by all display targets: data-binding, input-validation, navigation and possible business logic.

• UX Controls are necessary because the MBF client will not deliver all the Microsoft Dynamics NAV 2009 controls. Therefore, native controls, or managed win forms controls, are wrapped in a thin abstraction. This is the physical control.

The Service Tier

The Service Tier consists of five main components:

• The Microsoft Dynamics NAV Service • The Application Code • The metadata provider • Business Web services • Navision Class Library (NCL)

Briefly, the Microsoft Dynamics NAV Service functions as a hub that handles requests coming from the new clients through Web services. The Web service is hosted by Internet Information Services (IIS). This is responsible for authentication (security) and thread management (performance).



1-6

As soon as a request is received and validated, it is passed on to the relevant component, metadata provider, application, or reporting service for execution. When execution is complete, the executing component sends a response to the calling client.

• The Microsoft Dynamics NAV Service represents the started state of the system and provides an interface between the application and the clients. The service exposes its functionality as methods on a Web service hosted by IIS. Within the Web service framework, IIS handles authentication and thread management. Tracing and logging of starts is also performed by the NAV Service.

• The Business Web Services Components provide a platform by which developers can use the existing NAV development environment to build and customize Web services based on standard definitions such as SOAP and Windows Services Enhancements (WSE). Business Web Services functionality includes use of all related business logic that accompanies such operations on such objects. This includes but is not limited to field validation, and assignment of Identification (ID's) from number series and other code associated with the entry and manipulation of data in Navision, such as data modify triggers like OnCreate, OnModify and OnDelete.



1-7

Three-Tiers on Three-Computers Microsoft Dynamics NAV 2009 introduces a three-tier RoleTailored architecture that improves the security, scalability, and flexibility of Microsoft Dynamics NAV. In this lesson the installation of the new architecture in a production environment on three computers is discussed.

This table is an example of what each computer will host in the three tier architecture:

Computer Description

DYNNAV-SQL-SERVER

• Server computer hosting SQL Server. • This is the database tier. • This computer runs Microsoft Windows

Server 2003 or 2008.

DYNNAV-SERVER • Server computer hosting Microsoft Dynamics NAV Server.

• This is the server tier. • This computer runs Microsoft Windows

Server 2003 or 2008.

DYNNAV-CLIENT • Client computer running the RoleTailored client.

• This is the client tier. • This computer runs Microsoft Windows

Vista.

The key characteristic of this lesson is that the components are all on separate computers. In a real production environment, you might have several SQL Server computers, several Microsoft Dynamics NAV Server computers, and several RoleTailored client computers. As long as you do not install multiple Microsoft Dynamics NAV components together on a single computer, the procedures and issues presented in this lesson apply.

After completing this lesson, you will have a functioning three-tier installation on three computers. The install uses the CRONUS International Ltd. demo database.

This walkthrough illustrates the following tasks:

• Installing the Microsoft Dynamics NAV database components. • Configuring Microsoft SQL Server for Microsoft Dynamics NAV. • Installing Microsoft Dynamics NAV Server. • Installing Microsoft Dynamics NAV RoleTailored client. • Configuring delegation



1-8

Database Components

After you have installed SQL Server 2005 and SQL Server 2005 SP2, the next step is to install the Microsoft Dynamics NAV database components and the CRONUS International Ltd. demo database.

Follow these steps to install the Microsoft Dynamics NAV 2009 Database Components and demo database:

1. Insert the Microsoft Dynamics NAV 2009 DVD into the DVD drive of DYNNAV-SQL-SERVER, your database computer. The Startup screen opens and presents a set of options in the Prepare, Install, and Join the community sections.

2. Under Install, click Microsoft Dynamics NAV. 3. On the Welcome screen, click Next. 4. To accept the license terms, click I accept. 5. On the Microsoft Dynamics NAV 2009 Installer page, click

Choose an installation option. 6. On the Choose an installation option page, click Database

Components. The demo database is included as part of this option. 7. On the Specify parameters page, click Install. 8. After the installation is complete, click Close to exit Setup.

Configuring SQL

NOTE: The extended stored procedure is automatically installed for 32-bit SQL Server installations. You do not need to manually configure it.

Follow these steps to configure the Microsoft Dynamics NAV 2009 stored procedure for 64 bit installations:

1. Copy xp_ndo_x64.dll from the Sql_esp\x64 folder on the DVD to the Microsoft Dynamics NAV Database folder on your server computer. In a default installation, this location is C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database.

2. Open SQL Server Management Studio by clicking Start, clicking All Programs, pointing to SQL Server, and then clicking SQL Server Management Studio.



1-9

3. In the Connect to Server pane, in the Server type box, fill in the following fields:

Field Action

Server Type Select Database Engine.

Server name Select DYNNAV-SERVER (the database server computer)

Authentication Select Windows Authentication.

4. Click Connect. 5. In the left pane, click Databases, click System Databases, click

master, click Programmability, and then click Extended Stored Procedures.

6. Update the xp_ndo_enumusergroups extended stored procedure with the 64-bit DLL.

7. In the Extended Stored Procedures tab, right-click xp_ndo_enumusergroups, and on the shortcut menu, choose Properties.

8. In the Select a Page pane, click General. In the DLL property, provide the location of the 64-bit DLL that you previously copied, such as C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database.

9. In the Select a Page pane, click Permissions. 10. In the Users or roles section, click Add to open the Select Users or

Roles window. 11. Click Browse, select [public], and click OK. Click OK to close the

Select Users or Roles window. 12. In the Users or roles section, click public. In the Explicit

permissions for public section, select the Grant check box for the Execute permission.

13. Repeat the preceding steps for the xp_ndo_enumuserids extended stored procedure.

When using the 64-bit version of SQL Server 2005, you must configure it to be accessed by the Microsoft Dynamics NAV Server tier. The trace flag must be set before Microsoft Dynamics NAV Server can connect to the SQL database. You must restart the SQL Server service after you complete this procedure.

Follow these steps to set the Trace Flag on 64 bit version of SQL Server:

1. Open SQL Server Configuration Manger by clicking Start, clicking All Programs, pointing to SQL Server, pointing to Configuration Tools, and then clicking SQL Server Configuration Manager.

2. In the left pane, click SQL Server 2005 Services.



1-10

3. In the right pane, right-click SQL Server (MSSQLSERVER), and on the shortcut menu, click Properties.

4. In the Properties window, click the Advanced tab. 5. Click the Startup Parameters property, and open the drop-down

list. 6. Type ;-T4616 at the end of the line in the drop-down list and click

OK. 7. In the right pane, right-click SQL Server (MSSQLSERVER), and

on the shortcut menu, click Restart.

The next step in completing the installation of the three-tier architecture is to install the Microsoft Dynamics NAV Server service to the second server computer, DYNNAV-SERVER. This is a different server computer from the one where you installed SQL Server and the Microsoft Dynamics NAV database components.

To install Microsoft Dynamics NAV Server

1. Insert the Microsoft Dynamics NAV DVD into the DVD drive of DYNNAV-SERVER.

2. Under Install, click Microsoft Dynamics NAV. 3. On the Welcome screen, click Next. 4. To accept the license terms, click I accept. 5. On the Microsoft Dynamics NAV 2009 Installer page, click

Choose an installation option. 6. On the Choose an installation option page, click Server. 7. On the Specify parameters page, click Server to open the

Installation Parameters pane. 8. In the SQL Server field, type the name of the SQL Server

computer—DYNNAV-SQL-SERVER. 9. In the SQL Database field, type Demo Database NAV (6-0). 10. This identifies the CRONUS International Ltd. demo database. 11. Click Apply to save the Microsoft Dynamics NAV Server settings. 12. Click Install to begin installing software. 13. After the installation is complete, click Close to exit.

The third and final tier is the client tier. The first task is to install the RoleTailored client to a workstation computer.

Follow these steps to install the Role Tailored Client:

1. Insert the Microsoft Dynamics NAV DVD into the DVD drive of DYNNAV-CLIENT, your Microsoft Dynamics NAV client computer.

2. Under Install, click Microsoft Dynamics NAV.



1-11

3. On the Welcome page, click Next. 4. On the Microsoft Software License Terms page, review the

software license, and then click I accept. 5. On the Microsoft Dynamics NAV 2009 Installer page, click

Choose an installation option. 6. On the Choose an installation option page, click Client to install

the RoleTailored client. 7. On the Specify Parameters page, click RoleTailored client to

configure the component. 8. On the Installation Parameters pane, type the name of the

Microsoft Dynamics NAV Server computer, DYNNAV-SERVER, in the Server Name field.

9. Click Apply to begin installing software. 10. Click Install on the Specify parameters page. 11. After installation is complete, click Close to exit.

The procedures in this section are necessary only when the logon for Microsoft Dynamics NAV Server is a domain user account, instead of the Network Service account.

In this case, the RoleTailored client must have a way of identifying the Microsoft Dynamics NAV Server service's domain account. To accomplish this, the client must get a Kerberos ticket for the Microsoft Dynamics NAV Server service. The Microsoft Dynamics NAV Server service can then allow the client to use its credentials while interacting with a SQL Server database. This extension of credentials by proxy is known as delegation.

NOTE: If you were installing Microsoft Dynamics NAV Server and SQL Server on the same computer, but using a domain user account to log in to both, all of the following steps would still be necessary except Delegating Access to the SQL Server Service.

It is a good practice to create a dedicated domain user account for the NAV Service. This action requires a domain administrator.

After you create the user, right-click it in the tree view and choose Raise Domain Functional Level. From the drop-down, click Windows Server 2003 (if it is not already at this level).

The next step is to create a Service Principal Name (SPN) for the new domain user account. This will enable you to configure the Microsoft Dynamics NAV Server service to delegate access to the SQL Server service, on behalf of the RoleTailored client.



1-12

Follow these steps to create a Service Principal Name

On any server computer in the domain, download the Windows Server 2003 Service Pack 2 32-bit Support Tools.

Create the SPN by running the setspn utility. The required syntax is:

Copy Code

setspn –A ServerName_InstanceName/FullyQualifiedDomainNameOfServer:Port Domain \User

1. Using DYNNAV-SERVER (the server that runs Microsoft

Dynamics NAV Server in this walkthrough) and DynamicsNAV (the default instance name for Microsoft Dynamics NAV Server), the full command should look like this

Copy Code Setspn -A DYNNAV-SERVER_DynamicsNAV/DYNNAV-SERVER.yourDomain.yourCompany.com:7046 yourdomain\yourUser

Summary The new three-tier multithreaded architecture model of Microsoft Dynamics NAV 2009 provides process benefits beyond the two-tier architecture model's capability.

Understanding the Microsoft Dynamics NAV 2009 architecture enables IT professionals, system implementers and developers to install and customize Microsoft Dynamics NAV 2009



1-13

Test Your Knowledge 1. The following are benefits of a three-tier architecture

( ) It can accommodate up to 20 users. ( ) The business rules are located on the client tier. ( ) Business logic rules and execution are isolated from the client. ( ) Process logic is positioned at the client tier for optimal access by the end

user.

2. What is the purpose of the External Component in the NAV 4.0 and 5.0 two-tier architecture?

( ) It represents another application that integrates by means of the Navision Application Server.

( ) It represents remote access to the NAV 4.0 and 5.0 systems. ( ) It provides three-tier functionality to the two-teir architecture. ( ) Is of no real use.

3. The purpose of the Data Binder component in the NAV 2009 three-tier architecture does the following: (Select all that apply.)

( ) Determines the user experience for the end-user. ( ) Saves input data, data state and data notifications only on the client ( ) Sends data, and data state, and notifications from the business logic tot the

client and vice - versa ( ) Builds a logical form with data-binding, controls and behavior.



1-14

Quick Interaction: Lessons Learned Take a moment and write down three key points you have learned from this chapter:

1.

2.

3.



1-15

Solutions Test Your Knowledge

1. The following are benefits of a three-tier architecture

( ) It can accommodate up to 20 users. ( ) The business rules are located on the client tier. (•) Business logic rules and execution are isolated from the client. ( ) Process logic is positioned at the client tier for optimal access by the end

user.

2. What is the purpose of the External Component in the NAV 4.0 and 5.0 two-tier architecture?

(•) It represents another application that integrates by means of the Navision Application Server.

( ) It represents remote access to the NAV 4.0 and 5.0 systems. ( ) It provides three-tier functionality to the two-teir architecture. ( ) Is of no real use.

3. The purpose of the Data Binder component in the NAV 2009 three-tier architecture does the following: (Select all that apply.)

( ) Determines the user experience for the end-user. ( ) Saves input data, data state and data notifications only on the client (√) Sends data, and data state, and notifications from the business logic tot

the client and vice - versa ( ) Builds a logical form with data-binding, controls and behavior.



1-16


Chapter 2: Installation Requirements

2-1

CHAPTER 2: INSTALLATION REQUIREMENTS Objectives

The objectives are:

• Understand the Operating System and Software Prerequisites for Microsoft Dynamics® NAV 2009

• Select the correct Microsoft Windows® Server Version • Understand the Microsoft® SQL Server® components • Microsoft SQL Server Editions

Introduction Microsoft Dynamics NAV 2009 is designed to take advantage of the Microsoft software platform. Therefore, all the software prerequisites of Microsoft Dynamics NAV are part of the Microsoft software stack.

This software platform consists of the following prerequisites for Microsoft Dynamics NAV 2009:

• Windows Server 2003 or 2008 • Microsoft SQL Server 2005 or 2008 • The Microsoft® .NET Framework 3.5 • Microsoft Windows Services Enhancements • ASP.NET • Microsoft Report Viewer 2008

These software requirements determine the hardware configuration.

The hardware configuration must be sufficient to run the software prerequisites. If this is not the case then the software prerequisites will not run correctly. This will lead to a failed implementation of Microsoft Dynamics NAV.

Next the focus is about how to select the hardware and software prerequisites for Microsoft Dynamics NAV 2009.



2-2

Software Prerequisites of Microsoft Dynamics NAV Users must install and configure the following prerequisites to prepare the server on which you will load Microsoft Dynamics NAV:

Windows Server is the infrastructure platform for powering connected applications, networks, and Web services from the workgroup to the data center.

Microsoft SQL Server is a comprehensive database platform providing enterprise-class data management with integrated business intelligence (BI) tools. The Microsoft SQL Server 2005 and 2008 database engine provides improved security and reliable storage for both relational and structured data. This enables you to build and manage highly available, performance data applications for use in your business.

The .NET Framework is a development and execution environment that enables different programming languages and libraries to work together seamlessly to create Microsoft Windows-based applications that are easier to build, manage, deploy, and integrate with other networked systems.

The Web Services Enhancements for Microsoft .NET is an add-in to Microsoft Visual Studio® 2007 and the Microsoft .NET Framework 3.5 that enables developers to build secure Web services based on the latest Web services protocol specifications.

The Microsoft Report Viewer 2008 Redistributable Package includes Windows Forms and ASP.NET Web server controls for viewing reports designed by using Microsoft reporting technology. Microsoft Report Viewer control enables applications that run on the .NET Framework to display reports designed by using Microsoft reporting technology. This redistributable package contains Windows Forms and ASP.NET Web server control versions of the Report Viewer.

FIGURE 2.1 ROLE TAILORED CLIENT PRE-REQUISITES



2-3

Microsoft Windows Server Windows Server 2003 or Windows Server 2008 is the platform operating system for Microsoft Dynamics NAV 2009. Whether you use the 2003 or 2008 depends on your hardware and infrastructure, and your performance needs.

Windows Server 2003

Windows Server 2003 is an effective, and productive platform for running mission-critical applications. Leading Independent Software Vendors (ISVs) are actively testing, updating, and developing server applications that support changes that you make to the Windows Server 2003 family.

Windows Server 2003 includes all the functionality customers need to do more with less, while providing security, reliability, availability, and scalability. Microsoft has improved and extended the Microsoft Windows server operating systems to incorporate the benefits of Microsoft .NET which enables information, people, systems, and devices to connect to each other

Windows Server 2003 is a multipurpose operating system able to handle a diverse set of server roles, depending on a user's needs, in either a centralized or distributed manner. Some of these server roles include

• Application server • File and print server • Web server and Web application services • Mail server • Terminal server • Remote access and Virtual Private Network (VPN) server • Directory services including Domain Name System (DNS), Dynamic

Host Configuration Protocol (DHCP) server, and Microsoft Windows Internet Naming Service (WINS)

• Streaming media server

Windows Server 2003 Standard Edition is designed for departmental and standard workloads.

Windows Server 2003 R2 Enterprise Edition differs from Windows Server 2003 R2 Standard Edition primarily in its support for high-performance servers and its ability to cluster servers for more load handling. These capabilities include the following:

• Eight-way Symmetric Multiprocessing (SMP) • Eight-Node Clustering • Up to 64 Gigabytes of RAM



2-4

This platform provides reliability that helps systems remain available even if problems occur.

• Windows Server 2003 Datacenter Edition is designed for: • The highest levels of scalability and reliability • Supporting mission-critical solutions for databases • Enterprise resource planning software • High-volume, real-time transaction processing • Server consolidation

Windows Server 2003 R2, Datacenter Edition, is available in both 32-bit and 64-bit versions and includes the following:

• Thirty two-way SMP • Eight-Node Clustering • Up to 64 Gigabytes of RAM

Microsoft Dynamics NAV uses Windows Server 2003 as an application server, and will be installed on a Windows Server 2003 Standard Edition in most production environments. Other environments may require the Enterprise or Datacenter Editions

Windows Server 2008

Windows Server 2008, with built-in Web and virtualization technologies, enables businesses to increase the reliability and flexibility of their server infrastructure. New virtualization tools, Web resources, and security enhancements help save time, reduce costs, and provide a platform for a dynamic and optimized datacenter.

FIGURE 2.2 WINDOWS SERVER 2008



2-5

Powerful new tools, such as Internet Information Services (IIS) 7.0 and Server Manager, provide more control over servers, and streamline Web, configuration, and management tasks. Advanced security and reliability enhancements, such as Network Access Protection and the Read-Only Domain Controller, harden the operating system and help protect the server environment to make sure a solid foundation on which to build businesses.

Windows Server 2008 provides a solid foundation for all server workload and application requirements while it is easy to deploy and manage. Hallmark Windows Server reliability and increased high availability features help make sure that your important applications and data is available when you need them.

• Initial Configuration Tasks moves interactive elements of setup to after installation. This eliminates the need for the administrator to interact with the installation of the operating system.

• Server Manager, the expanded Microsoft Management Console (MMC), provides a single interface for server configuration and monitoring with wizards to streamline common server management tasks.

• Windows PowerShell, a new optional command-line shell and scripting language, enables administrators to automate routine system administration tasks across multiple servers.

• Windows Reliability and Performance Monitor provides powerful diagnostic tools to give you ongoing visibility into the server environment, both physical and virtual, to pinpoint and resolve issues quickly.

• Optimized server administration and data replication for increased control over servers that are located in remote locations, such as a branch office.

• Componentized Server Core installation option enables minimal installations where only the server roles and features that you need are installed, reducing maintenance needs and decreasing the available attack surface of the server.

• Windows Deployment Services (WDS) provides a simplified, highly secure means of quickly deploying Windows operating systems to computers by using network-based installation.

• Failover clustering wizards make it easy for even IT generalists to implement high-availability solutions. IP version 6 (IPv6) is now fully integrated, and geographically dispersed cluster nodes no longer have to be on the same IP subnet or configured with complex Virtual Local Area Networks (VLANs).

• Network Load Balancing (NLB) supports IPv6 and includes multiple dedicated IP address support which enables multiple applications to be hosted on the same NLB cluster.

• Windows Server Backup incorporates faster backup technology and simplifies data or operating system restoration.



2-6

Windows Server 2008 is available in multiple editions to support the varying server needs of organizations of all sizes. Windows Server 2008 is available in five primary editions, and three of these editions are also available without Windows Server Hyper-V, bringing the total number of editions to eight.

Windows Server 2008 Roles are specified in this table:

FIGURE 2.3 WINDOWS SERVER 2008 ROLES



2-7

Microsoft SQL Server Microsoft SQL Server 2005 is a comprehensive database platform providing enterprise-class data management with integrated business intelligence (BI) tools. It is fully integrated into the Microsoft Data Platform.

FIGURE 2.4 THE SQL SERVER PLATFORM CONTEXT

he Microsoft SQL Server 2005 data engine is the core of this enterprise data management solution. Additionally, Microsoft SQL Server 2005 combines analysis, reporting, integration, and notification.

Business intelligence (BI) features provide a competitive advantage. These advantages include enriching data and building complex business analytics with Analysis Services, and writing, managing, and delivering rich reports that use Reporting Services.

Microsoft Dynamics NAV 2009 uses the following components of Microsoft SQL Server 2005:

• Relational Database • Notification Services • Analysis Services • Reporting Services

The Relational Database

The Relational Database is where the Microsoft Dynamics NAV data is stored. Microsoft SQL Server 2005 is a robust data management solution used to manage data needs for organizations of all sizes.



2-8

Notification Services

The Notification Services are used to provide alerts within the Microsoft Dynamics NAV application. It is also used by associated Microsoft Dynamics NAV functionality such as Business Notification.

Analysis Services

Analysis Services are used by Microsoft Dynamics NAV Business Analytics to provide decision makers with accurate and timely views of the data.

Reporting Services

Reporting Services are used by Microsoft Dynamics NAV to write, manage, and deliver rich reports.

SQL Server 2005 Editions Microsoft SQL Server 2005 offers five editions. Two of these editions are available in 32-bit and 64-bit versions. Determining the correct version for your company's requirements for Microsoft Dynamics NAV is important for a successful implementation.

SQL Server 2005 Enterprise Edition (32-bit and 64-bit)

Enterprise Edition is meant to support the largest enterprise online analytical processing environments, highly complex data analysis, data warehousing and active Web servers.

SQL Server 2005 Standard Edition (32-bit and 64-bit)

Standard Edition includes the necessary functionality for e-commerce, data warehousing and line of business solutions that most small and medium sized business use. If your organization has to track large amounts of data but do not have to have all the functionality of Enterprise Edition then Standard Edition will work well with Microsoft Dynamics NAV.

SQL Server 2005 Workgroup Edition (32-bit only)

Workgroup Edition is the data management solution for small organizations that need a database that has no limit on the size or number of users and has the capability to work as a back end to small Web servers and departmental or branch office operations.

SQL Server 2005 Developer Edition (32-bit and 64-bit)

Developer Edition includes all the functionality of SQL Server 2005 Enterprise Edition. However, it is licensed as a development and test server, not as a production server.



2-9

SQL Server 2005 Express Edition is a free, easy to use and easy to manage database that can be redistributed to act as a client database and basic server database. It is usually suited for small data sets and will not work in some Microsoft Dynamics NAV implementations.

To determine which SQL Server edition will work best your Microsoft Dynamics NAV implementation, review the features in each edition.

SQL Server 2008

SQL Server 2008 delivers on Microsoft’s Data Platform vision by helping your organization manage any data, any place, any time. It enables you to store data from structured, semi-structured, and unstructured documents, such as images and music, directly within the database. SQL Server 2008 delivers a rich set of integrated services that enable you to do more with your data such as query, search, synchronize, report, and analyze. Your data can be stored and accessed in your largest servers within the data center down to desktops and mobile devices. This gives you control over your data regardless of where it is stored.

FIGURE 2.5 SQL SERVER 2008 PLATFORM CONTEXT



2-10

SQL Server 2008 enables you to consume your data within custom applications developed by using Microsoft .NET and Visual Studio and within your service-oriented architecture (SOA) and business process through Microsoft BizTalk Server while information workers can access data directly in the tools that they use every day, such as the 2007 Microsoft Office system. SQL Server 2008 delivers a trusted, productive, and intelligent data platform for all data needs.

Summary The prerequisites of Microsoft Dynamics NAV 2009 consist of the Microsoft Stack components including:

• Microsoft Windows Server 2003 or Microsoft Windows Server 2008 • Microsoft SQL Server 2005 or Microsoft SQL Server 2008



2-11


1.

2.

3.



2-12


Chapter 3: RoleTailored Client Install

3-1

CHAPTER 3: ROLETAILORED CLIENT INSTALL Objectives

The objectives are:

• Install Microsoft Dynamics® NAV 2009 Demo version on a Single Computer

• Install Microsoft Dynamics™ NAV 2009 Clients on a Network • Launch the Microsoft Dynamics NAV 2009 RoleTailored Client.

Introduction Microsoft Dynamics NAV 2009 is designed to use the Microsoft software platform. Therefore, all the software prerequisites of Microsoft Dynamics NAV are part Microsoft software stack.

The following Microsoft components must be configured correctly before Microsoft Dynamics NAV 2009 can be installed.

The complete product with sample data is supported on the following operating systems:

• Microsoft® Windows® XP SP2 • Microsoft® Windows® Vista • Microsoft® Windows® Server 2003 • Microsoft® Windows® Server 2008

NOTE: To install the Microsoft® Outlook® Add-In for Microsoft Dynamics NAV 2009, you must install Outlook before running the installer.



3-2

Install Dynamics NAV Demo Version on a Single Computer Microsoft Dynamics NAV 2009 can be installed on a single computer that has sample data for demonstration.

The following components are installed on the single computer :

• RoleTailored client • Classic client with SQL • Classic Client • Microsoft Dynamics NAV Server • Demo database and demo license

NOTE: The Microsoft® SQL Server® 2005 - Express edition will be installed if the system does not already have SQL Server 2005 or 2008 Installed

NOTE: When doing a Typical Install, only the RoleTailored Client will install

Procedure: Installation Steps

Use the following steps to install Microsoft Dynamics NAV 2009 with sample data on a single computer:

1. Run setup.exe.



3-3

The Welcome to the Microsoft Dynamics NAV 2009 Installer window appears.

FIGURE 3.1 MICROSOFT DYNAMICS NAV 2009 INSTALLER

1. Click Next. 2. To agree with the license agreement terms, click I accept. 3. Click the Install Demo option. 4. When the installation is complete, click Close.

The following components are installed:

• RoleTailored client • Classic client • Microsoft Dynamics NAV Server • Demo database and demo license • Microsoft SQL Server 2005 Express Edition (if SQL Server is not

already installed)

After installing the product, start the RoleTailored client or the Classic client on the Start menu. In Windows Vista, to run the Classic client or RoleTailored client that has User Account Control turned on, click Start, and then click All Programs. Right-click the client, and on the shortcut menu, click Run as administrator.



3-4

NOTE: The Classic client must be connected with the Microsoft Dynamics NAV database when you start it. The installer does not connect the Classic client to a database.

NOTE: The demo database is not uninstalled when you uninstall Microsoft Dynamics NAV 2009 through the control panel. You need to remove it manually.

Install Dynamics NAV 2009 Clients on a Network The RoleTailored client and Classic client can be installed on a different computer from where the Microsoft Dynamics NAV Server is installed. The clients are supported on the following operating systems:

• Microsoft® Windows® XP SP2 • Microsoft® Windows® Vista • Microsoft® Windows® Server 2003 • Microsoft® Windows® Server 2008


To install the Role Tasteps to install Microsoft Dynamics NAV2009 with sample data on asingle computer

1. Run setup.exe.



3-5

The Welcome to the Microsoft Dynamics NAV 2009 Installer page appears.

FIGURE 3.2 THE MICROSOFT DYNAMICS NAV 2009 INSTALLER

2. Click Next. 3. To agree with the license agreement terms, click I accept. 4. Click Choose an installation option. 5. The Choose an installation option page appears. 6. Click Clients. 7. The Specify parameters page appears with RoleTailored client and

Classic client options. Click RoleTailored client. 8. The Installation Parameters dialog box appears. Enter the following

parameters to connect a RoleTailored client to Microsoft Dynamics NAV Server: o Server Name: The name of the server. o Server Port: The port that the server uses for communication.

NOTE: No parameters are specified for the Classic client.

9. Click Apply. 10. Click Install.



3-6

The following components are installed:

• RoleTailored client, which can connect to a different computer that is running Microsoft Dynamics NAV Server.

• Classic client, which can connect to a SQL database on a different computer that is running SQL Server

After installing the product, start the RoleTailored client and the Classic client from the Start menu. In Windows Vista, to run the Classic client or RoleTailored client with User Access Control turned on, click Start, and then click All Programs. Right-click the client, and on the shortcut menu, click Run as administrator

NOTE: You must connect the Classic client to the SQL database when you start it. The installer does not connect the Classic client to a database.

Start the RoleTailored Client The biggest change in Microsoft Dynamics NAV from version 5.0 to version 2009 is the introduction of the new RoleTailored user interface (UI). The RoleTailored design provides you with a quick overview of the information relevant to your job and gives you the ability to focus, prioritize and apply your expertise.

The new task-oriented navigation structure reduces the complexity of information the user has to sift through and allows them to focus on the key work areas for their role in their company. The Role Center links them to the processes in which they participate. On list places, the tasks and information relevant to their goals in a work process are displayed together in one window. The tasks for each process step are available in task pages. The Action Pane promotes those commands the user accesses most frequently within a given context. FactBoxes reduce searching by offering the user all the information they need for a given context in one window. Furthermore, they have the bility to customize all of these parts of the program to make them better fit the user's needs.

Begin on the Start Menu

Launch the RoleTailored Client by going to the start menu on you Server's user interface.



3-7

Select Microsoft Dynamics NAV 2009.

FIGURE 3.3 ROLETAILORED CLIENT PINNED TO THE START MENU

As the client launches you will be presented with an opportunity to load the demonstration company.

After the client launches the first time, it is necessary to setup Outlook 2003 or 2007 for use with the client, if it is not already setup on your system.



3-8

Navigate in the RoleTailored Client

The Microsoft Dynamics NAV, Role Centered Client opens on the Role Center by default.

FIGURE 3.4 ROLE CENTERED CLIENT USER INTERFACE

The Role Center is your main point of entry into Microsoft Dynamics NAV. You can use it to get an overview of the status of your day’s work.

It can contain the following parts:

• Activities - contains stacks of documents, called “Cues” – Click a Cue to open the corresponding list or journal.

• Outlook - gives you an overview of your e-mails, calendar and Outlook tasks. You can click an item to open the corresponding folder, e-mail or appointment in Outlook.

• Charts - may contain one or more graphs that display information that is relevant to your work. Hover the cursor over a part of the chart to see the related data in text.

• Notifications - shows notes that your colleagues have sent to you. You can click on a note to open the document that the message is related to.

• Lists - may contain one or more lists with customers, vendors or items. You can decide which customers, vendors or items to include on the list. By selecting a line and clicking the Open command, you can open the card for the customer, vendor or item.



3-9

Keyboard Shortcuts

This table indicates the shortcuts in the RoleTailored Client and the Classic Client:

Shortcuts in the Classic client

Shortcuts in the RoleTailored client

Description

Alt+F5 Not supported Get warehouse documents

Alt+F9 Not supported No Actions

Alt+Arrow Left Alt+Arrow Left Accelerator to move to the previous page in the navigation travel history

Alt+Arrow Right Alt+Arrow Right Accelerator to move to the next page in the navigation travel history

Alt+Tab Alt+Tab Switch between open items

Ctrl+A Not supported Select all (copy)

Ctrl+C Ctrl+C Copy

Ctrl+E Ctrl+E Export to Microsoft®

Excel®.

Ctrl+F Ctrl+F Find/Navigate Form

Ctrl+L Ctrl+L Show links

Ctrl+N • F8 • Ctrl+N

Create new or Insert

Ctrl+O Ctrl+O Open a company

Ctrl+P Ctrl+P Print

Ctrl+R Not supported Replace

Ctrl+V Ctrl+V Paste

Ctrl+W Ctrl+W Export to Word

Ctrl+X Ctrl+X Cut

Ctrl+Z Ctrl+Z Undo

Ctrl+F1 Not supported Toggle mark

Ctrl+F2 Not supported Open Designer

Ctrl+F3 Ctrl+Shift+M Split line; used in Warehouse, for example, Form 5770



3-10



Description

Ctrl+F4 Esc Cancel or close the current task or window, unless it is the main window

Ctrl+F5 Ctrl+Shift+N Show ledger entries

Ctrl+F6 Alt+Tab Switch between open windows

Ctrl+F7 Ctrl+Shift+T Add a table filter (show results/Advanced filter) in the filter pane

Ctrl+F9 Ctrl+Shift+Z Reconcile

Ctrl+F11 Ctrl+Shift+R Release a document

Ctrl+Shift+A Ctrl+Shift+U Expand or collapse tree

Ctrl+Shift+D Ctrl+Shift+D Show dimensions

Ctrl+Shift+I Ctrl+Shift+I • (Service Lines) when user wants to close a Service Order

• (Service Shipment Lines) used by service - example Form5975

Ctrl+Shift+F7 Ctrl+Shift+A Clear all filters in filter pane

Delete Delete Clear selected text

End End In view mode, move to the last field in the row or, if already in the last field, do not move. The text in the destination field is selected. In edit mode, move to the last character position in the field or if already in the last position, do not move.

Esc Esc Cancel or close the current task or window, unless it is the main window

F1 F1 Display Help



3-11



Description

F2 • F2 • Ctrl+Shift+E

Toggle between Edit mode and View mode or open a card, document, or editable list in Edit mode

F3 • F8 • Ctrl+N • Ctrl+ +

Create new or Insert

F4 Ctrl+D Delete

F5 Ctrl+Shift+L List

F6 • F4 • Ctrl+U

Lookup; Launches AssistEdit

F8 Ctrl+R Copy previous

F9 Ctrl+Shift+J Open statistics on a card

F10 F10 Focus on the menu bar and display key tips

F11 F9 Post a document

F12 F12 Focus on the navigation pane

Shift+F1 Not supported What's This…

Shift+F2 • F4 • Ctrl+U

Lookup; Launches AssistEdit

Shift+F5 Ctrl+Shift+C Open a card or a document

Shift+F6 Not supported Drill down

Shift+F7 Ctrl+Shift+F Add a FlowFilter (limit totals) in the filter pane

Shift+F8 Ctrl+Shift+S Sort, or focus on sort in filter pane

Shift+F9 Ctrl+Shift+Y Apply entries

Shift+F11 Shift+F9 Post and print a document

Shift+F12 Not supported Open Object Designer



3-12



Description

Shift+Tab Shift+Tab Move keyboard focus to the previous element in the tab sequence within a part. If the element is the last in the part, focus moves to the first element in the next part.

Tab Tab Move forward through elements within a part. The tab order skips the Action menu and the Collapse/Expand button on the FastTabs. If the element is the last in the part, focus moves to the first element in the next part.

Not applicable Alt Key tips on action pane; focus on command bar; same as F10

Not applicable Alt+A Launch action menu

Not applicable Alt+I Launch related information

Not applicable Alt+M Open Microsoft Dynamics NAV menu

Not applicable Alt+P Launch action pane

Not applicable Alt+R Launch report

Not applicable Alt+Arrow Down Open the lookup menu when focus is on a cell with a drop-down menu

Not applicable Ctrl+D Delete

Not applicable Ctrl+F1 shows extended tooltip on a validation error

Not applicable Ctrl+F10 Turn on or off key tips in the action pane

Not applicable Ctrl+Arrow Down Move the focus down while the selected line stays selected



3-13



Description

Not applicable Ctrl+Arrow Left Move focus to first cell in a row

Not applicable Ctrl+Arrow Right Move focus to last cell in a row

Not applicable Ctrl+Arrow Up Move the focus up while the selected line stays selected

Not applicable Ctrl+Delete On the filter pane, deletes a filter

Not applicable Ctrl+End Move to the last cell of the entire grid

Not applicable Ctrl+Home Move to the first cell of the entire grid

Not applicable Ctrl+Insert On the filter pane, adds a filter

Not applicable Ctrl+Shift+B Open (Journals, worksheets, accounts schedules)

Not applicable Ctrl+Shift+K Edit list

Not applicable Ctrl+Shift+L View list

Not applicable Ctrl+Shift+V Open a card or a document in View mode

Not applicable Ctrl+Shift+W In View mode, open a list in a new List Task page in a new separate window

Not applicable Ctrl+Shift+X Exit

Not applicable Ctrl+ + Insert a new line in a grid

Not applicable F3 Focus on the filter pane

Not applicable F5 Refresh the current page

Not applicable F6 Move forward through screen elements such as panes or FastTabs, with focus on the first part of a pane. In a lookup moves focus to the Advanced action, if any.



3-14



Description

Not applicable F10 Key tips on action pane; focus on command bar; same as Alt

Not applicable F11 Focus on address bar

Not applicable Home In view mode, move to the first field in a row in focus or, if already in the first field, does not move. The text in the destination field gets selected. In edit mode, move to the first character position in the field or, if already in the first position, does not move.

Not applicable Shift+F6 Move backward through screen elements such as panes or FastTabs, with focus on the first part of a pane



3-15

Lab 3.1 - Installing Microsoft Dynamics NAV 2009 Clients Scenario

You are the consultant implementing Microsoft Dynamics NAV 2009 Clients for Woodgrove Construction. You need install the client on 2 computers with sample data so that A/P clerks can familiarize themselves with the software. You will also launch the client to confirm that it is installed correctly.

Challenge Yourself!

In this exercise you will install the RoleTailored client with demo data on single computer. The main tasks for this exercise are as follows:

1. Install the RoleTailored client from the Setup CD. 2. Specify the Installation Parameters. 3. Launch the RoleTailored client.

Step by Step

Step 1

To install the Microsoft Dynamics NAV2009 RoleTailored client with sample data on a single computer:

1. Run setup.exe. 2. Click Next. 3. To agree with the license agreement terms, click I accept. 4. Click Choose an installation option. 5. The Choose an installation option page appears

Click Clients. 6. Specify parameters page appears with RoleTailored client and

Classic client options. 7. Click RoleTailored client. 8. The Installation Parameters dialog box appears. Enter the following

parameters to connect a RoleTailored client to Microsoft Dynamics NAV Server: a. Server Name: The name of the server b. Server Port: The port that the server uses for communication

9. Click Apply. 10. Click Install.



3-16

Step 2

To launch the RoleTailored client follow these steps:

1. From the Start Menu select Microsoft Dynamics NAV 2009. 2. Click OK to accept the loading of the demo company, Cronus

International Ltd.



3-17

Summary This chapter covers the installation of Microsoft Dynamics NAV 2009 Role Based Client.: In particular it covers:

1. The installation of the full RoleTailored Client installation for demonstration purposes was covered.

2. The installation of the RoleTailored Client on a Network was discussed.

3. Launch of the RoleTailored Client 4. How to navigate in the Role Center



3-18


1.

2.

3.


Chapter 04: RoleTailored Client Personalization

4-1

CHAPTER 4: ROLETAILORED CLIENT PERSONALIZATION Objectives

The objectives are:

• Customize the Navigation Pane • Customize Pages

Introduction Users can personalize their Role Center to meet their individual work requirements. They can save their personalization settings directly in the Role Center or create their own Views or share other's views.

The following are some examples of user personalization options:

• Re-sizing columns. • Changing what appears in drop-down menus. • Personalizing the Navigation pane. • Adding or removing FactBoxes. • Organizing items in the Quick Access pane. • Saving queries or filters. • Selecting columns in a list location.

Accessing the Customization Dialog Box

The navigation pane can be customized in many ways using the Customize Navigation Pane dialog box.

The dialog box can be accessed from the menu bar as follows:

On the menu bar, click Customize , and then click Customize Navigation Pane.

FIGURE 4.1 ACCESSING THE DIALOG BOX



4-2

Another way to access the Customize Navigation Pane is to position the mouse pointer over the control and right-click.

FIGURE 4.2 ACCESS THE CUSTOMIZE NAVIGATION PANE DIALOG BOX

Customize the Navigation Pane The navigation pane contains one or more menus that have been defined for your role, and also Departments. The menus in the navigation pane contain links to lists. You access task pages, reports, and documents from the lists.

The Navigation Pane customizations enable the user to personalize their interface:

• Renaming or Rearranging Buttons in the Navigation Pane • Creating a New Menu Button • Adding a Link to a Menu in the Navigation Pane • Moving or Copying a Link from One Menu to Another • Rearranging the Order of the Menu • Restoring the default Settings

Renaming or Rearranging Buttons in the Navigation Pane

You cannot move, rename, or remove the Home or Departments buttons. They are always the first and last buttons, respectively. However, you can move, rename, or remove other menu buttons in your navigation pane.

To move, rename, or remove buttons in your navigation pane:



4-3

In the Customize Navigation Pane dialog box, in the navigation pane, select the button that you want to move, rename, or remove and then click the relevant button in the middle of the window.

FIGURE 4.3 THE CUSTOMIZE NAVIGATION PANE WINDOW

Procedure: Creating a New Menu Button

Use the these steps to create a new menu button:

1. In the Customize Navigation Pane dialog box, click New and type a name in the Name field. Also select the icon you want to use.

2. Click OK.

FIGURE 4.4 CREATING A NEW MENU

3. Now you can add links to the menu you created.



4-4

Adding a Link to a New Menu Button

If you have permission to view a list, such as the sales order list, you can add a link to the list to one of the menus in your navigation pane.

1. In the Customize Navigation Pane dialog box, in the Navigation pane buttons field, select the menu that you want to add the link to.

2. Click Add. 3. Browse to the link that you want to add, and then click OK.

FIGURE 4.5 ADD LIST TO THE NAVIGATION PANE

If you find a link in the Departments pages, you can also add it to the navigation pane.

Procedure: Moving or Copying a Link from One Menu to Another

Perform these steps to move a link from one menu to another:

1. In the Customize Navigation Pane dialog box, in the Navigation pane buttons field, select the menu where the link currently appears.



4-5

2. In the Lists pane, select the link that you want to move, and then click Move To or Copy To.

3. Select the menu that you want to add the link to, and then click OK.

FIGURE 4.6 MOVING A LINK TO ANOTHER MENU

4. Select the menu that you want to add the link to, and then click OK.

FIGURE 4.7 MOVE LIST



4-6

To rearrange the order of a menu, follow these steps:

1. In the Lists pane, select the link that you want to move. 2. Use the Move Up and Move Down buttons to position the link.

FIGURE 4.8 MOVE UP AND MOVE DOWN BUTTONS

If you want to cancel all the changes that you have made (and saved) to the navigation pane, you can do this in the Customize Navigation Pane dialog box. This will restore the navigation pane that your administrator defined for you.



4-7

To restore the default settings, click Restore Defaults and then click OK.

FIGURE 4.9 RESTORE DEFAULTS

Your changes will appear in the navigation pane when you restart Microsoft Dynamics® NAV.

Customize Pages Customizing Pages enables a user to personalize various aspects of Microsoft Dynamics NAV 2009.

The following are changes that you can make to the Microsoft Dynamics NAV 2009:

• Customizing the Action Pane • Customizing the Fact Box Pane • Customize the FactBoxes • Adding or Removing Panes • Customizing FastTabs

These changes only affect your program, and not those of your colleagues..



4-8

Customizing the Action Pane

You can add or remove commands in the Action Pane from the Customize window. By displaying the commands that you use most frequently in the Action Pane, you can gain fast and easy access to these commands. The Actions Pane is divided into groups, for example New, Process and Reports. You can add or remove a group and you can add or remove commands in a group.

To open the Customize window, click Customize on the right side hand side of the menu bar (next to Help) and select Customize Action Pane.

The Customize dialog box opens.

FIGURE 4.10 ACTION PANE



4-9

Removing and Adding Commands

Select the group that you want to modify in the Select a group field. All the commands from the menus in the menu bar are listed in the Available commands box. All the commands already in the selected group are listed in the Show these commands box.

FIGURE 4.11 ADD OR REMOVE ACTIONS

Do one of the following:

• To remove a command, select the command in the Show these commands box and then click Remove.

• To add a new command to a group in the Action Pane, in the Available commands box, select the command that you want to add to the group. Click Add and then click OK.



4-10

Changing the Size of an Icon

To change the size of an icon:

1. Select the group that you want to modify in the Select a group field. 2. Select the command in the Show these commands box and click

Change Size. A check mark shows in the Large column in the Show these commands box. Click OK.

FIGURE 4.12 CHANGE SIZE BUTTON

Adding a New Group

To add a new group, select the contents of the Select a Group field and type the name of your new group. Press Tab. You can now start adding commands to your new group.

Restoring Default Settings

You can cancel all the changes you have made (and saved) to the Action Pane. This will restore the default setting that was defined by your administrator for this particular page or list place.



4-11

To restore the default settings, click Restore Defaults and then click OK.

Customizing the FactBox Pane

You can add or remove FactBoxes in the FactBox pane from the Customize dialog box. The FactBoxes can provide you with information that relates to the record that you have selected in the list or opened in a task page. You can select from a list of FactBoxes which ones to display in your FactBox pane.

To open the Customize window to select FactBoxes, click Customize on the right hand side of the menu bar and select Customize This Page.

The Customize dialog box opens. Select FactBoxes.

FIGURE 4.13 THE FACTBOX CUSTOMIZATION PANE

Removing and Adding FactBoxes To remove a FactBox, select the FactBoxes in the Show FactBoxes in this order box. Click Remove and then click OK.

To add a new FactBox to the FactBox pane, select the FactBox that you want to add to the FactBox pane in the Available FactBoxes box. Click Add and then click OK.

Changing the Order of the FactBoxes To change the order of the FactBoxes, select the FactBox that you want to move in the Show FactBoxes in this order box and then click Move Up or Move Down. Repeat this procedure until the FactBox is where you want it.



4-12

Adding or Removing Panes

You can select among different panes in Microsoft Dynamics NAV. These panes provide easy access to related information. Some panes can be added or removed directly from the Customize menu (which opens when you click Customize ). Some panes (the Filter Pane, Action Pane and FactBox pane) can also be added or removed using the Customize dialog box. Panes on the Role Center can only be removed using the Customize dialog box.

To add or remove panes using the Customize menu:

• Click Customize on the right side of the menu bar and add or clear a check mark next to the specific pane.

FIGURE 4.14 CUSTOMIZE SALES ORDER WINDOW

When you close the menu, the page or place updates with your changes.

Customizing FastTabs

You can arrange your FastTabs on a page so they support your normal working flow in the best possible way. You can, for example, change the order of the FastTabs, remove fields or make less important fields only show when required. You can also have the most important fields show in the FastTab headers when the FastTabs are collapsed. This will provide you with a summary of the information on the FastTabs.



4-13

There are three priority levels for fields:

FIGURE 4.15 PRIORITY LEVELS



4-14

Lab 4.1 - Adding a Vendor List to the Role Center Scenario

You are the consultant implementing Microsoft Dynamics NAV 2009 Clients for Woodgrove Construction. You need to personalize the client on 2 computers with sample data so that A/P clerks can view the Vendor Information in their Role Center when they log on.

Challenge Yourself!

In this exercise you will personalize the RoleTailored client to provide the user access to Vendor Lists in their Role Center. The main tasks for this exercise are as follows:

1. Create a button 2. Add Vendor List link to the button

Step by Step

Step 1

Use these steps to create a new menu button:

1. In the Customize Navigation Pane dialog box, click New and type a name in the Name field. Choose Vendor List. Also select the icon you want to use.

2. Click OK. 3. Restart the client. 4. Now you can add links to the menu you created.

Step 2

Add a link to a new Menu Button with the following steps:

If you have permission to view a list, such as the Vendor list, you can add a link to the list to one of the menus in your navigation pane.

1. In the Customize Navigation Pane dialog box, in the Navigation pane buttons field, select the menu (Vendor List) that you want to add the link to.

2. Click Add. 3. Browse to the link for Purchase, Planning, Vendors, and then click

OK to add it to the Vendor List Menu Button. 4. Click Vendor List to the Navigation Pane.



4-15

Summary The navigation pane can be customized in many ways using the Customize Navigation Pane dialog box.

These Navigation Pane customizations allow the user to personalize their interface by:

• Renaming or Rearranging Buttons in the Navigation Pane • Creating a New Menu Button • Adding a Link to a Menu in the Navigation Pane • Moving or Copying a Link from One Menu to a Another • Rearranging the Order of the Menu • Restoring the default Settings

Customizing Pages enables a user to personalize various aspects of Microsoft Dynamics NAV 2009.

The following are changes that you can make to your Microsoft Dynamics NAV 2009:

• Customize the Action Pane • Customize the FactBox Pane • Customize the FactBoxes • Add or Remove Panes • Customize FastTabs

It is also possible to customize Reports and Actions.



4-16


1.

2.

3.


Chapter 5: Database Server

5-1

CHAPTER 5: DATABASE SERVER Objectives

The objectives are:

• Set up the Microsoft Dynamics® NAV 2009 Server • Configure the Microsoft Dynamics NAV 2009 Service with Setup • Configure the Microsoft Dynamics NAV 2009 Server after Setup

Introduction The new Microsoft Dynamics NAV 2009 Server is a .NET-based Windows Service application that works exclusively with SQL Server databases.

It uses the Windows Communication Framework as the communication protocol for Role Tailored clients, and Internet Information Services for Web services that connect with it. It can execute multiple client requests in parallel and serves other clients by providing Web service access to authenticated clients.



5-2

NAV Server Setup A key difference between the two-tier architecture with the Classic client and three-tier architecture with the Role Tailored client and the Microsoft Dynamics NAV Server is that business logic runs on the Server instead of the client in the three-tier architecture. A simple example is the FILE.CREATE function. In previous versions of Microsoft Dynamics NAV, files are created on the client when code such as this code is run. With the RoleTailored architecture, the files are created on the service itself.

Microsoft Dynamics NAV 2009 Server provides an additional layer of security between the clients and the database. It leverages the authentication features of the Windows Communications Framework to provide another layer of user authentication and uses impersonation to ensure that business logic is executed in a process that has been instantiated by the user who submitted the request. This means that authorization and logging of user requests is still performed on a per-user basis, and ensures that all Windows authentication and Microsoft Dynamics NAV 2009 roles and permissions that have been granted to the user are correct. It also ensures that business logic–level auditing is still performed.

FIGURE 5.1 INSTALLER



5-3

NOTE: Do not install the Microsoft Dynamics NAV Server to an encrypted drive. If you do, the NAV Server will not run.

Server Installation

The Microsoft Dynamics NAV Server is installed when you select either the Server Installation Option or the Developer Environment Installation Option in Microsoft Dynamics NAV Setup.


Configure Windows Services

Some Microsoft Dynamics NAV 2009 components are Windows services. Specifically, processes that remain in memory, function without user intervention, and serve other processes as needed.

Windows services must log on to an account to access resources and objects on the operating system. If all your Microsoft Dynamics NAV components run on a single computer configuring services are not a problem, but if you have installed different components on different computers, then you may need to configure one or more services to communicate with other Microsoft Dynamics NAV 2009 components.



5-4

The Microsoft Dynamics NAV Server runs as the NT Authority\Network Service account by default. If the Microsoft Dynamics NAV Server and SQL Server are on different computers, Microsoft recommends that you configure the Microsoft Dynamics NAV Server to run as a Windows domain account that is recognized by the SQL Server service. This account should not be an administrator in the domain or on any local computer.

Procedure: Configuring a Service

1. Perform the following steps to configure a service in Windows Server® 2003 or 2008:

2. Select Control Panel, then Administrative Tools, and then Services. 3. In the list of services, double-click the service you want to configure. 4. In the Server Properties dialog box, go to the Log On tab. 5. Select This account and either enter or browse to the account that

you want the service to use. 6. Enter and confirm the password for this account. 7. Click OK to exit the Server Properties dialog box.

Server Configuration During Setup As you run Microsoft Dynamics NAV 2009 Setup, you can provide configuration information for the Microsoft Dynamics NAV Server. This information is then written, by Setup, to the CustomSettings.config file. Assuming you install to the default destination, you can find CustomSettings.config after installing at C:\Program Files\Microsoft Dynamics NAV\60\service.

Configuring during Setup

The NAV Server can be configured while running Microsoft Dynamics NAV 2009 Setup. You must first select the Microsoft Dynamics NAV Server as a component to install. Do this by selecting one of the Installation Options that includes the Microsoft Dynamics NAV Server. There are two possible options:

• The Server Option installs the Microsoft Dynamics NAV Server without any other components.

• The Developer Environment Option installs the Microsoft Dynamics NAV Server along with various other components.



5-5

You can also opt to customize your installation After you specify an Installation Option or customize your component list, you come to the Specify parameters pane in Setup. Click Server (the underscore indicates that this component is configurable) to open an Installation Parameters pane.


Installing the Server Option

Select the Server installation option from the Installer Window

The list of parameters displayed in the Specify parameters pane varies, depending on which components you have selected for configuration. The following parameters pertain to the Microsoft Dynamics NAV Server.

Server Port This is the listening TCP port for the NAV Server, which becomes part of the server's URL. Default value: 7046 Valid range: 1-65535.

SQL Server Identifies the computer running SQL Server.



5-6

SQL Database Identifies the SQL Server database.

Web Service Port Identifies the listening HTTP port for Microsoft Dynamics NAV 2009 Business Web Services. Default value: 7047. Valid range: 1-65535.

Click Apply when you have finished entering values to exit back to the Specify parameters pane in Setup.

FIGURE 5.4 CUSTOMSETTINGS.CONFIG FILE

After running Setup you can modify Microsoft Dynamics NAV Server settings by editing CustomSettings.config.

NAV Server Configuration After Setup After you install the NAV Server, configuration settings are stored in the CustomSettings.config file, created C:\Program Files\Microsoft Dynamics NAV\60\service. If you have configured the NAV Server in Setup, your setting values are included in this file.



5-7

In addition to the settings you can configure in Setup, CustomSettings.config contains additional settings for the NAV Server. After you modify CustomSettings.config, you must restart the NAV Server service.

CustomSetting.config File

CustomSettings.config is an XML file that you can edit with any text editor. Quotes are required for all values.

It can be found at: Program Files > Microsoft Dynamics NAV> 60 >Service

The settings are as follows.

Setting Meaning

NetType The network protocol used to access the database. Default value: Default. Valid values: Default, NamedPipes, Sockets.

DatabaseServer Identifies the computer running SQL Server.

DatabaseName Identifies the SQL Server database.

ServerInstance The name of the NAV Server. Default: DynamicsNAV. The only circumstance where you would need to modify this value is if you have more than one NAV Server installed on a single server computer.

ServerPort This is the listening TCP port for the NAV Server, which becomes part of the server's URL. Default value: 70476 Valid range: 1-65535.

WebServicePort Identifies the listening HTTP port for Microsoft Dynamics NAV 2009 Business Web Services. Default value: 85. Valid range: 1-65535.

WebServiceSSLEnabled Specifies whether SSL (https) is enabled for the Web Service Port. Default value: true. Values: true, false.



5-8

Setting Meaning

OperationTimeout Specifies the maximum time the NAV Server can take to return a call from the client. Time span format: [dd.]hh:mm:ss[.ff] Where: • dd: days • hh: hours • mm: minutes • ss: seconds • ff: fractions of a second You can also use MaxValue to indicate no timeout. This is the default.

ProtectionLevel Specifies the security services for protecting the client/server data stream. Default: EncryptAndSign. Values: EncryptAndSign, Sign, None.

MaxConcurrentCalls Specifies the maximum number of concurrent client calls that can be active on the NAV Server. Default: 60 Range: 1 - 2,147,483,647. To disable this setting, use a value of MaxValue.

ClientReconnectPeriod Specifies the grace period during which a client can reconnect to a running NAV Server. Time span format: [dd.]hh:mm:ss[.ff] Where: • dd: days • hh: hours • mm: minutes • ss: seconds • ff: fractions of a second Default value: 00:10:00.

CompressionThreshold Specifies a threshold, in terms of memory consumption, at which the NAV Server begins compressing data sets. Default: 65535.



5-9

Lab 5.1 - Editing the Configuration file for the NAV Server Scenario

You are the consultant implementing Microsoft Dynamics NAV 2009 Clients for Woodgrove Construction. Users of Sales information report that they cannot access their data. You determine that clients are not connecting to the service tier.

Challenge Yourself!

In this exercise you will change the Database Server Name in the configuration file to the correct name for the server that hosts SQL Server 2005, so that clients can connect to their Sales data. The main tasks for this exercise are as follows:

1. Open the configuration file in Visual Studio. 2. Change the server name to the correct name.

Step by Step

Step 1: Access the Configuration File

1. The configuration file is called CustomSettings.config. It is an XML file.

2. Find the file at Program Files > Microsoft Dynamics NAV >6.0>Service.

3. Double-click the file to open it in Visual Studio.

Step 2: Edit the Configuration File

1. Identify the XML tag that contains the SQL Database Server name 1. Change the name to the correct name. 2. Save the CustomSeettings.config file. 3. Launch the RoleTailored client and access the Sales data.



5-10

Summary The NAV Server is a component of the Three-Tier architecture in Microsoft Dynamics NAV 2009.

You can configure the NAV Server while running Microsoft Dynamics NAV 2009 Setup. There are two such options:

• The Server Option installs the NAV Server without any other components.

• The Developer Environment Option installs the NAV Server along with various other components.



5-11


1.

2.

3.



5-12


Chapter 6: Classic Client Option

6-1

CHAPTER 6: CLASSIC CLIENT OPTION Objectives

The objectives are:

• Discuss the Classic Client software requirements and hardware recommendation.

• Install the Classic Client • Install the Developer Environment Option

Introduction The Classic client runs business logic locally, and displays data in forms, such as card forms or list forms. You design forms in a visual design environment with precise layout information.

You can migrate users and applications from the Classic client to the RoleTailored client over time. Microsoft Dynamics® NAV 2009 is designed to accommodate both types of clients in parallel.

The Classic client is installed when you select either the Clients Installation Option or the Developer Environment Installation Option in Microsoft Dynamics NAV Setup.



6-2

Requirements Meeting the Classic Client software and hardware requirements is an important step in the provision of the client to end-users or for the needs of a developer.

Software

Microsoft Dynamics NAV Clients must be installed on one of the following operating systems:

• Windows® XP Professional SP3 or later (X86 or running 32 bit on X64)

• Windows® Server 2003 SP2 or later (X86 or running 32 bit on X64) • Windows Server 2003 R2 SP2 or later (X86 or running 32 bit on

X64) • Windows Vista® (Business, Enterprise, or Ultimate) SP1 or later

(X86 or running 32 bit on X64) • Windows Server 2008 (X86 or running 32 bit on X64)

Hardware and Network

Minimum computer requirements are as follows:

• Hard disk space -2.5 GB (3.0 GB for the Developer Edition) • Memory - 1 GB

If you run Microsoft Dynamics NAV Developer Environment option on a network, you need the following network requirements

• WinSockets-compatible TCP/IP if you are using the tcp protocol with the Microsoft Dynamics NAV Server.

• NetBIOS-compatible LAN if you are using the netb protocol with the Microsoft Dynamics NAV Server.

• LAN network connection should be 100 Mbit/sec or better.

Classic Client Installation The Classic client is the one Classic component that remains essential for all Dynamics NAV 2009 installations, as a tool for development and administration tasks. (For example, you must use the Classic client to upload your Microsoft Dynamics NAV 2009 license file.)



6-3


Perform the following steps to run the Microsoft Dynamics NAV 2009 Classic Client Setup:

1. Verify that the target computer meets the hardware and software requirements for the Classic Client Installation Option.

2. Select Client in the Choose an installation window and select Customize

3. In the Customize the Installation window select Not Available on the drop-down menu next the Role Tailored client

4. Select Run All From My Computer on the drop-down menu next to the Classic Client

5. Click Choose an installation option. Proceed to the Choose an installation option pane.

6. To install Microsoft Dynamics NAV 2009 software to a location other than the default location (C:\Program Files\Microsoft Dynamics NAV\60), click Customize and then click Destination folder on the Customize the installation pane.

7. Once components are configured (or if you do not need to configure components at this time), click Install to begin copying software.

8. Click Close to exit Setup.

Cancel an Installation Setup

Setup has no Cancel button, but you can cancel an installation from any pane by clicking the X in the upper-right corner of the Setup window. All Microsoft Dynamics NAV 2009 components are removed from the computer. The only kinds of software that Setup installs but cannot remove during an install cancel are:

• Database files such as the Demo database • Pre-requisites for Microsoft Dynamics NAV 2009 components that

Setup can install, such as the .NET Framework

The Developer Environment Option When you choose the Developer Environment option, Setup installs the following components on the computer:

• RoleTailored Client • Classic Client • Database Components and a demo database. • The Microsoft Dynamics NAV 2009 Software Development Kit

This option installs all three tiers in the three-tiered architecture along with the Software Development Kit.



6-4

Procedure: Developer Environment Setup

To run Microsoft Dynamics NAV 2009 Developer Environment Setup verify that the target computer meets the hardware and software requirements for the Developer Environment Installation Option.

Insert the Microsoft Dynamics NAV 2009 DVD.

The Startup screen presents a set of options in sections entitled Prepare, Install, and Join the Community.

1. Click Microsoft Dynamics NAV under Install. 2. Click Next to move past the Welcome screen. 3. Click I accept to indicate acceptance of the license terms. 4. Click Choose an installation option. 5. If you click Choose an installation option, you proceed to the

Choose an installation option pane. 6. On the Choose an installation option pane, click the Developer

Environment option. 7. You can click the word Customize, in smaller text, to modify the list

of installed components before installing. See Choosing Components to Install for details.

8. To install Microsoft Dynamics NAV 2009 software to a location other than the default location (C:\Program Files\Microsoft Dynamics NAV\60), click Customize and then click Destination folder on the Customize the installation pane.

9. On the Specify Parameters page you can configure any component displayed with a black underscore.

10. Each configurable component has an icon indicating one of three possible statuses. See the bottom of the screen in Setup for the meaning of these icons.

11. For information on how to configure components, see Configuring Components.

12. Once components are configured (or if you do not need to configure components just now), click Install to begin copying software.

13. Click Close to exit Setup.

Summary The Classic Client is used in the three-tier architecture as the means to customize Microsoft Dynamics NAV. It is also used to upload a license to the server.

The Classic Client can be installed by using customized installation option or by selecting the Developer Environment option.



6-5


1.

2.

3.



6-6



Chapter 7: Deployment

7-1

CHAPTER 7: DEPLOYMENT Objectives

The objectives are:

• Understand Software Deployment with Group Policy • Deploy Microsoft Dynamics® NAV 2009 RoleTailored and Classic

clients with Group Policy

Introduction Deploying Software is essential to meet the changing application needs of organizations and provide these benefits:.

1. When deploying Microsoft Dynamics NAV 2009 clients with Windows Server Group Policy, users no longer need to look for the application on a network share, use a CD-ROM or install, fix and upgrade software themselves.

2. Deploying Microsoft Dynamics NAV 2009 with Group Policy reduces time spent administering users’ systems.

3. Applications can be redeployed, upgraded or removed in the same meaner in which they were deployed.




7-2

Deployment Process The Software Installation and Maintenance feature of IntelliMirror is the administrator's primary tool for managing software within an organisation.

The Software Installation extension in the Group Policy Object Editor console is the key administrative tool for deploying software.

The Administrator controls which software is available to users within Add Or Remove Programs.

Software can be either assigned or published, and targeted to users or computers. A workable combination of these methods can be established to meet your software management goals.

Software Installation Extension

Using the Software Installation extension allows administrators to assign or publish an application to a user.

Assigning the RoleTailored Client

• When you assign a Microsoft Dynamics NAV 2009 RoleTailored Client to a user, the application is advertised to the user on the Start menu the next time they log on to a workstation and local registry settings, including filename extensions, are updated. It does not matter on which physical computer the user logs on to because the application advertisement is mapped to their user credentials.

• When you assign the RoleTailored client to a computer, the application is advertised and the client will be installed the next time the computer is restarted.

Publishing the RoleTailored Client

• When you publish the RoleTailored client to a user, the application does not appear installed on the user’s computer, no shortcuts are visible, and no updates are made to local registry on the users computers. Instead, the published applications store their information in Active Directory.

• The application is available for the user to use Add Or Remove Programs in Control Panel or by clicking on a file associated with the application.

Software Deployment Processes

The steps in software deployment vary depending on whether the application is published or assigned and whether the application is automatically installed by activating a document associated with the application.




7-3

Published Applications

This is the installation process for published applications:

1. The user logs on to a client computer running Windows 2000 or later.

2. The user opens Add Or Remove Programs in Control Panel. 3. Add Or Remove Programs obtains the list of published software

form Active Directory. 4. The user selects the Microsoft Dynamics NAV 2009. 5. Add Or Remove Programs obtains the location of published software

from Active Directory. 6. A request for software is sent to the Software Distribution Point 7. The Windows Installer service is started, and it installs, the requested

Windows Installer package. 8. The user opens the newly installed application.

Assigned Applications

This is the sequence of the installation process for assigned applications:

1. The user logs on to a client computer running Windows 2000 or later.

2. The WinLogon process advertises applications on the users desktop or on the Start menu.

3. The user selects Microsoft Dynamics NAV 2009 from the desktop or the Start menu.

4. The Windows Installer service gets the Windows Installer package. 5. A request for the software is sent to the Software Distribution Point. 6. The Windows Installer service is started, it installs the requested

Windows Installer package, and it opens the application.

Deploy Microsoft Dynamics NAV 2009 After you’ve familiarized yourself with the software deployment tools, the Windows Installer service, and the software deployment processes, you’re ready to learn how to deploy software with Group Policy. This lesson walks you through the steps of deploying software with Group Policy.

The tasks for deploying software with Group Policy are:

1. Plan and prepare the software deployment 2. Set up an SDP 3. Create a GPO and a GPO console for software deployment 4. Specify the software deployment properties for the GPO




7-4

5. Add Windows Installer packages to the GPO and select package deployment method.

6. Set Windows Installer package properties

Planning and Preparing to Deploy Software

Before you can begin deploying software with Group Policy, you must plan the deployment. When planning for software deployment, you should:

• Review your organization’s software requirements on the basis of your overall organizational structure within Active Directory and your available GPOs

• Determine how you want to deploy your applications • Create a pilot to test how you want to assign or publish software to

users or computer • Prepare your software using a format that allows you to manage it

based on what your organization requires, and test all of the Windows Installer packages or repackaged software

This table describes strategies and considerations for deploying software. Some of these strategies might seem contradictory, but select the strategies that meet your business goals.

Strategy Considerations Create OUs based on software management needs.

Allows you to target applications to the appropriate set of users. Group Policy security settings are not required to target the appropriate set of users.

Deploy software close to the root in the Active Directory tree.

Makes it easy to provide all users in an organization with access to an application. This reduces administration because you can deploy a single GPO rather than having to re-create that object in multiple containers deep in the Active Directory tree.

Deploy multiple applications with a single GPO.

Reduces administration overhead by allowing you to create and manage a single GPO rather than multiple GPOs. The logon process is faster because a single GPO deploying 10 applications processes faster than 10 GPOs, each deploying one application. This is appropriate in organizations where users share the same core set of applications.

Publish or assign an application only once in the same GPO or in a series of GPOs that might apply to a single user or computer.

Makes it easier to determine which instance of the application applies to the user or computer.




7-5

Software licenses are required for software written by independent software vendors and distributed using SDPs. It is your responsibility to match the number of users who can access software to the number of licenses you have on hand. It is also your responsibility to verify that you are working within the guidelines provided by each independent software vendor with the software.

Gather the Windows Installer packages (.msi files) for the software. Perform any necessary modifications to the packages and gather the transform (.mst) or patch (.msp) files.

Setting Up an SPD

After you have planned and prepared for software management, the next step is to copy the software to one or more SDPs, network locations from which users are able to get the software that they need.

To set up an SDP, complete the following steps:

1. Create the folders for the software on the file server that will be the SDP and make the folders network shares; for example: \\servername\sharename(file://\\servername\sharename).

2. Replicate the software to the SDP by placing or copying the software, packages, modifications, all necessary files, and components to a separate folder on the SDP.

3. Set the appropriate permissions on the folders. Administrators must be able to change the files (Full Control), and users must only view (Read) the files from the SDP folders and shares. Use Group Policy to manage the software within the appropriate GPO.

Using DFS to Manage SDPs

The Microsoft Distributed File System (DFS) provides users with convenient access to shared folders that are distributed throughout a network. With DFS, you can make files distributed across multiple servers appear to users as if they reside in one place on the network. For a software deployment with Group Policy, you can set up DFS to automatically direct users to the nearest SDP.

Creating a GPO and a GPO Console

In this step, you create a GPO and a GPO console for the software deployment.

In this step, you define the default settings for all Windows Installer packages in the GPO in the Software Installation Properties dialog box. The Software Installation Properties dialog box consists of the following tabs—General, Advanced, File Extensions, and Categories.




7-6

In the General and Advanced tabs, you specify how you want all Windows Installer packages in the GPO to be deployed and managed.

In the File Extensions tab, you specify which application users install when they select a file with an unknown extension. You can also configure a priority for installing applications when multiple applications are associated with an unknown file extension. For example, if you use a GPO to deploy both Microsoft Office XP Professional and Microsoft Office FrontPage version 2002, both of these applications can edit Spreadsheet Load Library files with the .sll extension. To configure the file extension priority so that users who are managed by this GPO always install FrontPage, set FrontPage as the application with the highest priority for the .sll extension. When a user managed by this GPO who has installed neither Microsoft Office Word version 2002 nor FrontPage 2002 receives an .sll file (by e-mail or other means) and double-clicks the .sll file, Software Installation installs FrontPage 2000 and opens the .sll file for editing. Without Software Installation, the user would see the Open With dialog box and be asked to select the best alternative from the software already present on his or her computer. File extension associations are managed on a per-GPO basis. Changing the priority order in a GPO affects only those users who have that GPO applied to them.

In the Categories tab, you can designate categories for organizing assigned and published applications to make it easier for users to locate the appropriate application from within Add Or Remove Programs in Control Panel.

Specify Software Deployment Properties

To specify software deployment properties for the GPO, complete the following steps:

Open the GPO console for the software deployment.

1. In the User Configuration or the Computer Configuration node, right-click the Software Installation node, and then click Properties.




7-7

2. In the General tab of the Software Installation Properties dialog box type the Uniform Naming Convention (UNC) path (\\servername\sharename(file://\\servername\sharename)) to the SDP for the Windows Installer packages (.msi files) in the GPO in the Default Package Location box.

FIGURE 7.1 SOFTWARE PROPERTIES DIALOG BOX

3. In the New Packages section, select one of the following: Display

The o Deploy Software Dialog Box, to specify that when you add new

packages to the GPO, the Deploy Software dialog box will display, allowing you to choose whether to assign, publish, or configure package properties. This is the default setting.

o Publish, to specify that when you add new packages to the GPO, they will be published by default with standard package properties. Packages can be published only to users, not computers. If this is an installation under the Computer Configuration node of the Group Policy Object Editor console, the Publish choice is unavailable.

o Assign, to specify that when you add new packages to the GPO, they will be assigned by default with standard package properties. Packages can be assigned to users and computers.

o Advanced, to specify that when you add new packages to the GPO, the Properties dialog box for the package will display, allowing you to configure all properties for the package.




7-8

4. In the Installation User Interface Options section, select one of the following: o Basic, to provide only a basic display for users during the

installation of all packages in the GPO. o Maximum, to provide all installation messages and screens for

users during the installation of all packages in the GPO.

5. Click the Advanced tab. In the Advanced tab of the Software Installation Properties window, select any of these, to be applied to all packages in the GPO: o Uninstall The Applications When They Fall Out Of The Scope

Of Management, to remove the application if it no longer applies to users or computers.

o Include OLE Information When Deploying Applications, to specify whether to deploy information about Component Object Model (COM) components with the package.

o Make 32-Bit X86 Windows Installer Applications Available To Win64Machines, to specify whether 32-bit Windows Installer Applications (.msifiles) can be assigned or published to 64-bit computers.

o Make 32-Bit X86 Down-Level (ZAP) Applications Available To Win64Machines, to specify whether 32-bit application files (.zap files) can bea ssigned or published to 64-bit computers.

FIGURE 7.2 ADVANCED TAB




7-9

Click the File Extensions tab. In the File Extensions tab, shown in File Extensions tab, select the file extension for which you want to specify an automatic software installation from the Select File Extension list.

FIGURE 7.3 FILE EXTENSIONS TAB

1. In the Application Precedence list box, move the application with the

highest precedence to the top of the list using the Up or Down buttons. The application at the top of the list is automatically installed if a document with the selected filename extension is invoked before the application has been installed.

2. Click the Categories tab. In the Categories tab, shown in Categories Tab of the Software Installation Properties dialog box, click Add.

FIGURE 7.4 CATEGORIES TAB

3. In the Enter New Category dialog box, type the name of the application category to be used for the domain in the Category box and click OK.

4. Click OK.




7-10

Adding Windows Installer Packages to the GPO

In this step, you specify the software applications you want to deploy by adding Windows Installer packages to the GPO. Then you specify how the package is deployed (either assigned or published).

To modify or update the software application, any modifications must be associated with the Windows Installer package at deployment time rather than when the Windows Installer is actually using the package. Transform (.mst) and patch (.msp) files are applied to Windows Installer packages (which have the .msi extension) in an order specified by the administrator. This order must be determined before the application is assigned or published.

1. To add Windows Installer packages to the GPO and select package deployment method, complete the following steps:

2. Open the GPO console for the software deployment. In the Computer Configuration or User Configuration node, open Software Settings.

3. Right-click the Software Installation node, click New, and then click Package. In the Open dialog box, in the File Name list, type the UNC path (\\servername\sharename(file://\\servername\sharename)) to the SDP for the Windows Installer packages (.msi files), and then click Open.

4. In the Deploy Software dialog box, click one of the following: o Published, to publish the Windows Installer package to users

without applying modifications to the package. o Assigned, to assign the Windows Installer package to users or

computers without applying modifications to the package. o Advanced, to set properties for the Windows Installer package,

including published or assigned options and modifications.

FIGURE 7.5 DEPLOY SOFTWARE

Click OK. If you selected Published or Assigned, the Windows Installer package has been successfully added to the GPO and appears in the details pane. If you selected Advanced, the Properties dialog box for the Windows Installer package opens, where you can set properties for the Windows Installer package, such as deployment options and modifications.




7-11

Setting Windows Installer Package Properties

In this step, you can fine-tune the deployment of each application by setting Windows Installer package properties in the Properties dialog box for the package. The Properties dialog box for the Windows Installer package contains the following tabs: General, Deployment, Upgrades, Categories, Modifications, and Security.

In the General tab, you can change the default name of the package and designate a support URL. Users can select a support URL from the Add Or Remove Programs window to be directed to a support Web page. A support URL can contain helpful information such as frequently asked questions (FAQs) and can assist in reducing calls to a help desk or support team. In the Deployment tab, you can designate the deployment type, deployment options, and installation user interface options. In the Upgrades tab, you can deploy a package that upgrades an existing package. The Upgrades tab does not appear for packages created from application files (.zap files). Using the Upgrades tab is discussed in Lesson 3. In the Categories tab, you can select the categories under which the application is listed for users in Add Or Remove Programs in Control Panel, making it easier for users to find the application. Categories you set generally pertain to published applications only, as assigned applications do not appear in Add Or Remove Programs. In the Modifications tab, you can indicate the modifications (transforms or patches) you want to apply to the package and specify the order in which the modifications apply to the package. In the Security tab, you can indicate permissions for the software installation. Permissions set for software installation pertain only to the package installation.

To set Windows Installer package properties, complete the following steps:

1. Open the GPO console for the software deployment. In the Computer Configuration or User Configuration node, open Software Settings.

2. Click the Software Installation node. 3. In the details pane, right-click the package for which you want to set

properties, and then click Properties.




7-12

4. In the General tab of the Properties dialog box for the package, you can type a new name for the package in the Name box, if desired. You can also type a URL that provides user support in the URL box.

FIGURE 7.6 GENERAL TAB

5. Click the Deployment tab. In the Deployment tab of the Properties

dialog box for the package, select one of the following in the Deployment Type area: o Published, to allow users in the selected site, domain, or OU to

install the application using either Add Or Remove Programs in Control Panel or application installation by file activation. If this is an application under the Computer Configuration node of the Group Policy Object Editor console, the Published option is unavailable, because packages can only be assigned to computers, not published.

o Assigned, to allow users in the selected site, domain, or OU to receive this application the next time they log on (for assignment to users) or when the computer restarts (for assignment to computers).

FIGURE 7.7 DEPLOYMENT TAB




7-13

6. In the Deployment Options area, select one of the following: o Auto-Install This Application By File Extension Activation, to

use the application precedence for the filename extension as determined in the File Extensions tab of the Software Installation Properties dialog box. If this is an application under the Computer Configuration node of the Group Policy Object Editor console, the check box appears dimmed and selected, because by default the application is installed automatically.

o Uninstall This Application When It Falls Out Of The Scope Of Management, to remove the application when users log on or computers start up in the event of relocation to a site, domain, or OU for which the application is not deployed.

o Do Not Display This Package In The Add/Remove Programs Control Panel, to specify that this package should not be displayed in Add Or Remove Programs in Control Panel.

o Install This Application At Logon, to specify that this package should be fully installed rather than just advertised by a shortcut. This option is available only for assigned applications. Avoid this option if the computer or user to which the application is assigned has a slow connection because the startup and logon procedures require a large amount of time when the application is first assigned.

7. In the Installation User Interface Options area, select one of the following: o Basic, to provide only a basic display to users during the install

process. o Maximum, to provide all installation messages and screens to

users during the package installation.

8. Click Advanced to display the Advanced Deployment Options dialog box. In the Advanced Deployment Options area, select any of the following check boxes: o Ignore Language When Deploying This Package, to specify

whether to deploy the package even if it is in a different language.

o Make This 32-Bit X86 Application Available To Win64 Machines, to specify whether the 32-bit program is assigned or published to 64-bit computers.




7-14

o Include OLE Class And Product Information, to specify whether to deploy information about COM components with the package.

FIGURE 7.8 ADVANCED DEPLOYMENT OPTIONS DIALOG BOX

9. Click OK. 10. Click the Categories tab. In the Categories tab of the Properties

dialog box for the package, shown in Figure 7-9, click the category under which you want to display this application to users from the Available Categories list, and then click Select.

FIGURE 7.9 CATEGORIES TAB




7-15

11. Click the Modifications tab. In the Modifications tab, Do any of the following: o To add modifications, click Add. In the Open dialog box, browse

to find the transform file (.mst) or patch file (.msp), and then click Open. You can add multiple modifications.

o To remove modifications, click the modification you want to remove, and then click Remove. Repeat until each unwanted modification has been removed.

o To set the order of modifications, select a modification and then click Move Up or Move Down. Modifications are applied according to the order specified in the list.

FIGURE 7.10 MODIFICATIONS TAB

Do not click OK in the Modifications tab until you have finished configuring the modifications. When you click OK, the package is assigned or published immediately. If the modifications are not properly configured, you will have to uninstall the package or upgrade the package with a correctly configured version.




7-16

12. Click the Security tab. In the Security tab of the Properties dialog box for the package, click the security group on which to set permissions. Administrators who manage the application installation should have the Full Control permission set to Allow. Users who use the software assigned or published by the application should have the Read permission set to Allow.

FIGURE 7.11 SECURITY TAB

13. Click OK.

Microsoft Dynamics NAV 2009 Settings

To configure the RoleTailored client and the NAV Server in Microsoft Dynamics NAV 2009 Setup:

1. Double-click RoleTailored client in the Specify parameters pane. 2. Provide values for the settings. For example:

Setting Values Server Name Since the RoleTailored client and the NAV

Server are both to be installed on the local computer, use localhost as the value for this setting.

Server Port Value is not relevant. The default (7046) is fine.

SQL Server Identifies the network server computer where SQL Server is installed. In our example, this computer is named jetsam.




7-17

Setting Values SQL Database Identifies the SQL database to use. In our

example, the database name is operations4.

Web Service Port The default value (85) is fine.

3. Click Apply to save the settings and return to the Specify

parameters pane.

To create a Setup configuration file:

1. In the Specify parameters pane, click Save the configuration. 2. In the Save As window, provide appropriate path and filename

information.

Click Save to exit the Save As window and return to the Specify parameters pane.

That's it. At this point you can go ahead and click Install to begin installing Microsoft Dynamics NAV 2009. Or you can click in the upper-right corner of the Setup screen to exit setup without installing any software for now.

Summary • The tasks for deploying software with Group Policy are the

following: plan and prepare the software deployment, set up an SDP, create a GPO and a GPO console for software deployment, specify the software deployment properties for the GPO, add Windows Installer packages to the GPO and select package deployment method, and set Windows Installer package properties.

• For a software deployment with Group Policy, you can set up DFS to automatically direct users to the nearest SDP.

• You can define software deployment properties that affect all Windows installer packages in a GPO.

• You can also define software deployment properties that affect individual Windows Installer packages in a GPO.

• Microsoft Dynamics NAV 2009 deployment settings were discussed




7-18


1.

2.

3.


Chapter 8: Optimization and Troubleshooting

8-1

CHAPTER 8: OPTIMIZATION AND TROUBLESHOOTING Objectives

The objectives are:

• Understand how to troubleshoot Microsoft Dynamics NAV 2009 Installation Issues

• Troubleshooting SQL Server Database and Server Performance • Troubleshoot the deployment of Microsoft Dynamics NAV 2009

clients

Introduction Microsoft Dynamics is built on the Microsoft technology stack. Consequently all the components need to be installed, configured, monitored, and optimized.

Troubleshooting needs and Optimization opportunities can occur in several areas including such as Network, Hardware, Operating System, Database Server, and Application.

In this module we fous on the Microsoft SQL Server 2005 and Windows Server 2003 Group Policy including:

• Resolving Space Issues • Updating Statistics • Evaluating Index Usage • Using SQL Server Profiler • Using the Database Engine Tuning Advisor • Monitoring Transaction Log Size • Investigating Locks and Deadlocks • Software Deployment Troubleshooting Scenarios



8-2

Microsoft Dynamics NAV 2009 Troubleshooting Performance of Microsoft Dynamics NAV 2009 is dependent on the Microsoft Technology stack on which it is built. That includes Windows Server and SQL Server. Before troubleshooting Windows Server or SQL Server performance issues it is recommended that you check that the Microsoft Dynamics NAV 2009 components are correctly installed.

Database Performance Troubleshooting When a Microsoft SQL Server 2005 server is not meeting its performance requirements, this situation could be a result of issues within a database, issues relating to instances of SQL Server, or the physical performance of the server.

As with any type of server, bottlenecks can occur because of pressure on one or more server resources such as memory, hard disk, input/output (I/O) devices, and central processing unit (CPU) usage. You need to be able to determine whether a system is improperly configured for the workload, or whether poor database design is the root cause of the problem. You need to proactively prevent or minimize problems and, when they occur, diagnose the cause and take corrective action.

Resolving Space Issues

SQL Server Management Studio, which provides a consistent and (arguably) user-friendly interface for managing and troubleshooting database issues. SSMS is an interactive, graphical tool that enables a DBA to write queries, execute multiple queries simultaneously, view results, analyze the query plan, and receive assistance to improve the query performance. The Execution Plan options graphically display the data retrieval methods chosen by the SQL Server query optimizer.

Resolving Space Issues

You can configure a database to auto-grow, or you can grow it manually by using the ALTER DATABASE Transact-SQL statement. The advantages of using auto-grow are that you avoid the tedium of growing databases on a regular basis, and users are less likely to encounter out-of-space problems. The disadvantages are that you can run out of disk space and that auto-grow uses a considerable amount of system resource.



8-3

Monitoring Auto-Grow and Auto-Shrink

You can use Profiler to record events as they occur in an instance of the database engine. The recorded events are instances of the event classes in the trace definition. In SQL Server Profiler, event classes and their event categories are available on the Events Selection tab of the Trace File Properties dialog box. You use the Database event category to monitor auto-grow and auto-shrink events in a database. These is a list of event classes of interest in this context:

• Data File Auto Grow Event Class

This event indicates that the data file grew automatically. It is not triggered if you grow the data file explicitly through ALTER DATABASE.

• Data File Auto Shrink Event Class

This event indicates that the data file has been shrunk.

• Log File Auto Grow Event Class

This event indicates that the log file grew automatically. It is not triggered if the log file is grown explicitly through ALTER DATABASE.

• Log File Auto Shrink Event Class

This event indicates that the log file shrunk automatically. It is not triggered if the log file shrinks explicitly through ALTER DATABASE.

Updating Statistics

After a series of INSERT, DELETE, or UPDATE Transact-SQL statements are performed on a table, the statistics might not reflect the true data distribution in a given column or index. If a column in a table has undergone substantial update activity since the last time the statistics were created or updated, SQL Server automatically updates the statistics by sampling the column values (using auto-update statistics).

The statistics auto-update is triggered by query optimization or by execution of a compiled plan, and it involves only a subset of the columns referred to in the query. If the query optimizer needs a particular statistics object when a query is first compiled and that statistics object exists, the statistics object is updated (if it is out of date).

When you execute a query and its plan is in the cache, the query optimizer checks the statistics on which the plan depends to see whether they are out of date. If so, SQL Server removes the plan from the cache and updates the statistics during recompilation of the query. SQL Server also removes the plan from the cache if any of the statistics that it depends on have changed.



8-4

The auto-update statistics feature can be turned off at different levels. At the database level, you can disable auto-update statistics using ALTER DATABASE dbname SET AUTO_UPDATE_STATISTICS OFF. At the table level, you can disable auto-update statistics using the NORECOMPUTE option of the UPDATE STATISTICS or CREATE STATISTICS command.

The sp_autostats Stored Procedure

You can use the stored procedure sp_autostats to display and change the auto-update statistics setting for a table, an index, or a statistics object. You can re-enable the automatic updating of statistics by using ALTER DATABASE, UPDATE STATISTICS, or the sp_autostats stored procedure. You cannot override the database setting of OFF for auto-update statistics by setting it ON at the statistics object level.

The sp_updatestats Stored Procedure

The sp_updatestats stored procedure runs UPDATE STATISTICS against all user defined and internal tables in the current database. It specifies the ALL keyword against all user-defined and internal tables in the database. The stored procedure displays messages that indicate its progress. When the update is completed, it reports that statistics have been updated for all tables.

Evaluating Index Usage

A database index lets SQL Server quickly find specific information in a table or indexed view. It contains keys built from one or more columns in the table or view, and pointers that map to the storage location of the specified data. You can significantly improve the performance of database queries and applications by creating well designed indexes to support your queries. Indexes can reduce the amount of data that must be read to return the query result set. Indexes can also enforce uniqueness on the rows in a table, ensuring the data integrity of the table data.

An index contains keys built from one or more columns in the table or view. These keys are stored in a structure known as a b-tree that enables SQL Server to find the row or rows associated with the key values quickly and efficiently. A table or view can contain clustered or nonclustered indexes.

Clustered Indexes

Clustered indexes sort and store the data rows in the table or view based on their key values. These are the columns included in the index definition. You can define only one clustered index per table because the data rows themselves can be sorted and stored in only one order.



8-5

Data rows in a table can be stored in order only when the table contains a clustered index. A table that has a clustered index is called a clustered table. If you do not define a clustered index for a table, SQL Server stores its data rows in an unordered structure called a heap.

Nonclustered Indexes

Nonclustered indexes have a structure separate from the data rows of the table itself. A nonclustered index contains nonclustered index key values and each key value entry has a pointer to the data row that contains the key value.

The pointer from an index row in a nonclustered index to a data row is called a row locator. The structure of the row locator depends on whether the actual data pages are stored in a heap or a clustered table. For a heap, a row locator is a pointer to the row. For a clustered table, the row locator is the clustered index key.

Constraints

A constraint is a rule that the database server enforces automatically. Indexes are automatically created when you define PRIMARY KEY and UNIQUE constraints on table columns. For example, when you create a table and identify a particular column as the primary key, the SQL Server 2005 database engine automatically creates a PRIMARY KEY constraint and index on that column.

Query Optimizer

Well-designed indexes can reduce disk I/O operations and consume fewer system resources, thereby improving query performance. Indexes can be helpful for a variety of queries that contain SELECT, UPDATE, or DELETE statements. For example, suppose that you issue the following query against the AdventureWorks database:

SELECT Title, HireDate FROM HumanResources.Employee WHERE EmployeeID = 222

Defragmenting Indexes

Data stored inside the database files can become fragmented at the index level. This prevents SQL Server 2005 from using indexes optimally. Index fragmentation can be either internal or external. Pages that have a lot of free space are internally fragmented.

This happens when you remove rows by DELETE statements or when SQL Server splits and only partly fills pages. Empty space on pages means there are less rows per page, which in turn means more page reads.



8-6

External fragmentation occurs when pages are not contiguous. Inserting new rows and updating existing rows can result in page splits. When a new page is created from a page split, SQL Server allocates it in the same 8-page extent as the original page if there is room for it. If the extent is already full, SQL Server allocates a new extent to the index or table and places the new page there. Thus, the new page is not contiguous to the original page.

You can use DBCC SHOWCONTIG to view the extent of index fragmentation. If you specify the TABLERESULTS option, you see extra output columns that describe index statistics. The following metrics assist you in auditing index defragmentation:

Avg. Page Density (full) - Shows how filled the pages are.

Scan Density - Shows the ratio between the Best Count of extents that should be necessary to read when scanning all the pages of the index and the Actual Count of extents that were read. This percentage should be as close to 100 as possible. Values less than 75 percent indicate serious external fragmentation.

Logical Scan Fragmentation - Shows the ratio of pages that are out of logical order. The percentage should be as close to 0 as possible. Values over 10 percent indicates external fragmentation.

You can use the following methods to defragment an index:

Drop and re-create the index

CREATE INDEX … WITH DROP_EXISTING

DBCC DBREINDEX

DBCC INDEXDEFRAG

You perform the first three options offline, which means that users cannot execute queries against the database while defragmentation is occurring. DBCC INDEXDEFRAG is an online operation, but SQL Server cannot defragment any indexes that are currently in use.

Rebuilding Indexes

You can use Object Explorer in SSMS to rebuild an index or all indexes on a table. Rebuilding an index drops and re-creates the index. This option removes fragmentation, reclaims disk space, and reorders the index rows in contiguous pages.



8-7

In Object Explorer, you connect to an instance of the SQL Server 2005 database engine, expand that instance, expand Databases and the relevant application database, navigate to the table that contains the index and then to the index itself. You then right-click the index, choose Rebuild, and click OK. To rebuild all the indexes in a table, you navigate to the table, right-click indexes, choose Rebuild All, and then click OK.

Creating Missing Indexes

When the query optimizer generates a query plan, it analyzes what the best indexes are for a particular filter condition. If the best indexes do not exist, the query optimizer generates a suboptimal query plan but stores information about the missing indexes. The missing indexes feature enables you to access information about these indexes so that you can decide whether you should implement them. You can then use missing index information to use CREATE INDEX statements that restore the missing indexes.

Dropping an Inappropriate Index

When you no longer need an index, you can remove it from a database by using the DROP INDEX Transact-SQL statement or by connecting to the database with SSMS, navigating to the index in Object Explorer, right-clicking it, choosing Delete, and clicking OK. This process reclaims the disk space the index currently uses. Deleting an index is the same as dropping it.

Dropping a clustered index can take time because in addition to dropping the clustered index, SQL Server must rebuild all nonclustered indexes on the table. To avoid rebuilding indexes, drop the nonclustered indexes first and the clustered index last.

Profiler

Use SQL Server Profiler to capture a trace when a script containing the queries you want to analyze is running, or when you execute the queries directly by typing them into the Query Editor. Alternatively, you can capture a trace during a period of peak activity and filter the results to display the information you require. Profiler enables you to select the events you want to capture and specify the data columns from those events. You can use filters to obtain only the data you require. The events you should capture are the following:

• Stored Procedures—RPC:Completed • TSQL—SQL:BatchCompleted



8-8

The first of these events captures stored procedures, and the second one captures all other Transact-SQL queries. Typically, the data columns you would specify are the following:

• Duration • Event Class • DatabaseID • TextData • CPU • Writes • Reads • StartTime • EndTime • ApplicationName • NTUserName • LoginName • SPID

StartTime, EndTime, ApplicationName, NTUserName, and LoginName are optional. You require DatabaseID only if you are accessing more than one database. Information in the Duration and TextData columns is especially useful in this analysis. Typically, you filter the trace to exclude system events and events with a duration of less than, for example, 5000 (5 seconds).

Database Engine Tuning Advisor

You can use the DTA to tune databases and create an optimized query environment.

The tool enables you to view the effects of a workload against single or multiple databases, and it makes recommendations to alter the physical design structure of your SQL Server databases.

These physical structures include

• clustered indexes • nonclustered indexes • indexed views • partitioning

The goal of the DTA recommendations is to enable the query server to execute the query in the least amount of time. Typically, you run DTA on a test server because it uses a large amount of server resources.



8-9

You can use the DTA tool to troubleshoot issues caused by the existing indexing strategy and to perform a what-if analysis on the databases. A what-if analysis helps you to determine how an alternative indexing strategy might affect query performance without changing your current strategy.

Monitoring Transaction Log Size

Every SQL Server 2005 database has a transaction log that records all transactions and the database modifications made by each transaction. The transaction log is a critical component of the database and, in the case of a system failure, enables you to restore mission-critical data to the point of failure. You should never delete or move transaction logs unless you fully understand the consequences of doing so.

An application database is typically very active, with many transactions. This activity can cause the transaction log to grow quickly. The instance database transaction log is also likely to grow rapidly. In both cases, you (or the database designer) should specify an initial log file size equal to 25 percent of the initial application database size. If the log is truncated regularly during log file backups or during a checkpoint, it should stay a reasonable size.

The transaction log is implemented as a separate file or set of files in the database. You can configure the files to expand automatically by setting the FILEGROWTH value for the log. This reduces the potential for running out of space in the transaction log, while at the same time reducing administrative overhead.

You can set % Free Space alerts that tell you when the physical or logical disk that holds the transaction files is running out of space, or you can use the SQLServer: Databases: Percent Log Used counter to trigger a SQL Server performance condition alert that starts a transaction log backup and sends you a message by using Database Mail. However, the best method of ensuring that transaction logs do not become too large is to implement a regular backup routine that truncates the logs.

The active portion of a transaction log cannot be truncated or removed by shrinking, and truncation can be delayed when log records remain active for a long time. This can happen for a variety of reasons—for example, no checkpoint has occurred since the last log truncation, a data backup or restore is in progress, a long-running transaction is active, database mirroring is paused, a database snapshot is being created, or a log scan is occurring.

SQL Server 2005 introduces the log_reuse_wait and log_reuse_wait_desc columns of the sys.databases catalog view. These features enable you to discover what is preventing log truncation.



8-10

Monitoring Database Growth

When you create a database, you must either specify an initial size for the data and log files or accept the default size. As data is added to the database, these files become full. However, you must consider whether and how the database will grow beyond the initial space you allocate if more data is added to the database than will fit in the files.

By default, the data files grow as much as required until no disk space remains. Therefore, if you do not want the database files to grow any larger than when they were first created, you must specify this at the time you create the database using SSMS or the CREATE DATABASE statement.

Alternatively, SQL Server lets you create data files that can grow automatically when they fill with data, but only to a predefined maximum size. This can prevent the disk drives from running out of disk space completely. When you create a database, make the data files as large as possible, based on the maximum amount of data you expect in the database. Permit the data files to grow automatically, but put a limit on the growth by specifying a maximum data file growth size that leaves some available space on the hard disk. This approach lets the database grow if more data is added than expected, but it does not fill up the disk drive.

If the initial data file size is exceeded and the file starts to grow automatically, re-evaluate the expected maximum database size and add more disk capacity if required.

If the database is not supposed to expand beyond its initial size, set the maximum growth size of the database to zero. This prevents the database files from growing. If the database files fill with data, no more data is added until more data files are added to the database or until the existing files are expanded.

Filegroups

Filegroups are named collections of files used to simplify data placement and administrative tasks such as backup and restore operations. They use a proportional fill strategy across all the files within each filegroup. As data is written to the filegroup, the database engine writes an amount proportional to the free space in the file to each file within the filegroup, instead of writing all the data to the first file until full. For example, if file myfile1 has 300 MB free and file myfile2 has 600 MB free, one extent is allocated from file myfile1, two extents from file myfile2, and so on. Both files become full at about the same time, and the procedure achieves simple striping.



8-11

When all the files in a filegroup are full, the database engine automatically expands one file at a time in a round-robin manner to allow for more data (provided that the database is set to grow automatically). Suppose, for example, a filegroup is made up of three files. When space in all the files is exhausted, the first file is expanded. When the first file is full and no more data can be written to the filegroup, the second file is expanded. When the second file is full and no more data can be written to the filegroup, the third file is expanded. If the third file becomes full and no more data can be written to the filegroup, the first file is expanded, and so on.

If you let files grow automatically and several files share the same disk, this can cause fragmentation. Therefore, you should create the files or filegroups on as many different local physical disks as possible. Also, put objects that compete heavily for space in different filegroups.

Improving Database Perfomance

Using files and filegroups improves database performance because it lets you create a database across multiple disks, multiple disk controllers, or RAID systems. For example, if your computer has four disks, you can create a database that is made up of three data files and one log file, with one file on each disk. As data is accessed, four read/write heads can access the data in parallel at the same time. This approach speeds up database operations.

Additionally, files and filegroups enable data placement because you can create a table in a specific filegroup. This improves performance because it enables you to direct all I/O for a specific table at a specific disk. For example, you can put a heavily used table on one file in one filegroup, located on one disk, and put the other less heavily accessed tables in the database on the other files in another filegroup, located on a second disk.

Monitoring Database Size

The sp_spaceused Transact-SQL stored procedure displays the number of rows, disk space reserved, and disk space used by a table, indexed view, or SQL Server 2005 Service Broker queue in the current database. It also displays the disk space reserved and used by the whole database.

The following example summarizes space used in the AdventureWorks database and uses the optional parameter @updateusage to ensure current values are returned:

USE AdventureWorks;

GO

EXEC sp_spaceused @updateusage = N‘TRUE’;



8-12

Investigating Locks and Deadloocks

The SQL Server database engine uses locks to synchronize access by multiple users to the same piece of data at the same time. Before a transaction reads or modifies data, it must protect itself from the effects of another transaction modifying the same data.

It does this by requesting a lock on the piece of data. Locks have different modes, such as shared or exclusive. No transaction can be granted a lock that would conflict with the mode of a lock already granted on that data to another transaction. If this situation occurs, the database engine pauses the requesting transaction until the first lock is released.

When a transaction modifies a piece of data, it holds the lock protecting the modification until the end of the transaction. All locks held by a transaction are released when the transaction either commits or rolls back. Typically, applications do not request locks directly. Locks are managed internally by the database engine lock manager.

When an instance of the database engine processes a Transact-SQL statement, the database engine query processor determines which resources are to be accessed. The query processor determines what types of locks are required to protect each resource based on the type of access and the transaction isolation level setting. The query processor then requests the appropriate locks from the lock manager. The lock manager grants the locks if there are no conflicting locks held by other transactions.

Displaying Locking Information

The database engine and its associated APIs provide mechanisms for displaying information about the locks currently held in a database. You can keep track of information about locks and lock notification requests by using the sys.lock_information DMV.

The sys.lock_information is a virtual table that contains a collection of lock information—for example, the session that requested the lock, the resource that is being locked, the row identifier of a locked row within a table, the lock mode that is being requested or that has been granted, the internal identity of the table, and the status of the lock.

Deadlocks

A deadlock occurs when two SPIDs are waiting for a resource and neither process can advance because the other process is preventing it from getting the resource. When the lock manager’s deadlock detection algorithm detects a deadlock, the lock manager chooses one of the SPIDs and kills the process. This frees the resources and allows the other SPID to continue. However, any application that depends on that process crashes.



8-13

By default, the lock manager chooses the transaction that is least expensive (for example, in time taken to load and initialize) to roll back as the deadlock victim. You can, however, specify the priority of sessions in a deadlock situation using the SET DEADLOCK_PRIORITY statement. You can set the DEADLOCK_PRIORITY to LOW, NORMAL (the default), or HIGH—or to any integer value in the range –10 through 10.

If two sessions have different deadlock priorities, SQL Server chooses the session with the lower priority as the deadlock victim. If both sessions have the same deadlock priority, SQL Server chooses the session with the transaction that is least expensive to roll back. If sessions involved in the deadlock cycle have the same deadlock priority and the same cost, SQL Server chooses a victim at random.

The database engine provides three tools for viewing deadlock information:

Deadlock graph An event group in SQL Server Profiler that presents a graphical description of the tasks and resources involved in a deadlock.

Trace flag 1204 This returns the type of locks participating in the deadlock and the current command affected. The results are captured in the SQL Server 2005 error log.

Trace flag 1222 This returns the type of locks participating in the deadlock and the current command affected in an XML-like format. The results are captured in the SQL Server 2005 error log.

Activity Monitor

You can use Activity Monitor within SSMS to get information about users’ connections to the database engine and the locks that they hold. To open the tool within SSMS, connect to the server with Object Explorer, expand Management, and then double-click Activity Monitor.

Activity Monitor has three pages.

• The Process Info page contains information about the connections. • The Locks By Process page sorts the locks by the connection. The • Locks By Object page sorts the locks by the object name.

You can click the Filter button to apply a filter and reduce the amount of information displayed. You can use Activity Monitor when troubleshooting database locking issues and to terminate a deadlocked or otherwise unresponsive process.



8-14

Optimizing RAID Configuration

SQL Server 2005 servers in a production environment typically use hard disk arrays configured to the appropriate RAID level. Typically, most organizations implement hardware RAID instead of software RAID. Hardware implementations are more expensive, but they are usually faster than software implementations and offer considerable advantages. Reliable disk storage that offers fast disaster recovery is relatively inexpensive when compared with the costs of data loss or long downtimes.

This table lists the advantages and disadvantages of using the various RAID implementations typically used with SQL Server 2005.

FIGURE 8.1

RAID0, striping (with no parity), provides excellent read/write performance but no disaster recovery.

Filegroups, discussed earlier, can provide advantages when configuring disk storage.

Troubleshooting Database and Transaction Log Storage

The SQLServer:Databases object provides counters to monitor bulk copy operations, backup and restore throughput, and transaction log activities. These counters enable you to monitor transactions and the transaction log to determine how much user activity is occurring in the database and how full the transaction log is becoming. Monitoring user activity and resource usage can help you to identify performance bottlenecks. You can monitor multiple instances of the object, each representing a single database, at the same time.



8-15

The following list shows counters specific to monitoring database and transaction log storage:

• Data File(s) Size (KB) - Returns the cumulative size (in kilobytes) of all the data files in the database, including any automatic growth.

• Log Cache Hit Ratio - Returns the percentage of log cache reads satisfied from the log cache.

• Log File(s) Size (KB) - Returns the cumulative size of all the transaction log files in the database.

• Log File(s) Used Size (KB) - Returns the cumulative used size of all the log files in the database.

You can use both SQL Server and Windows Server 2003 counters to troubleshoot disk space storage. For example, a SQL Server performance condition alert triggered by the SQLServer:Databases: Percent Log Used counter lets you know when a particular log file is running out of space. A Windows Server 2003 performance alert triggered by the LogicalDisk: % Free Space performance counter lets you know whether the RAID that holds the transaction logs or the database files is running short of disk space.

Troubleshooting Software Deployed with Group Policy To maintain software deployed with Group Policy, you must be able to troubleshoot the software deployment. This lesson shows you how to work with tools to troubleshoot software deployed with Group Policy.

Troubleshooting Software Deployed with Group Policy

As an administrator, it will likely be your task to find solutions to problems with software deployed with Group Policy. If problems occur, you might need to perform some tests to verify that your Group Policy configuration is working properly, and diagnose and solve problems.

Windows Server 2003 provides the following Group Policy troubleshooting tools to assist you in verifying your configuration and in diagnosing and solving problems:

• Resultant Set Of Policy Wizard • Gpresult • Gpupdate • Event Viewer • Log files



8-16

You must be proficient in the use of these tools to effectively troubleshoot software deployed with Group Policy.

Advanced Diagnostic Information

You can use the advanced diagnostic information provided in the Advanced Deployment Options dialog box to troubleshoot software deployed with Group Policy. The Advanced Deployment Options dialog box lists the following:

Product Code - A globally unique identifier (GUID) that identifies the application and its version.

Deployment Count - Displays the number of times the package has been redeployed.

Script Name - Displays the full path to the application assignment script (.aas file). An application assignment script contains instructions associated with the assignment or publication of a package and is generated for every published or assigned application in a GPO and stored in that domain’s GPO.

View Diagnostic Information

To view advanced diagnostic information, complete the following steps:

1. Open the Group Policy Object Editor console. In the Computer Configuration or User Configuration node, open Software Settings.

2. Click the Software Installation node. 3. In the details pane, right-click the package for which you want to

view advanced diagnostic information, and then click Properties. 4. Click the Deployment tab, and then click Advanced.

Software Deployment Troubleshooting Scenarios

The following tables describe some troubleshooting scenarios related to software deployed with Group Policy.



8-17

Problem:

Published applications do not appear for the user in Add Or Remove Programs in Control Panel.

Problem Causes Solutions

The client is running Terminal Services on the desktop.

Use Addiag.exe to see if Terminal Services is running on the user’s desktop. Software deployed with Group Policy is not supported for Terminal Services clients.

Group Policy is not applied to this user.

Run Gpresult for the user to ensure that the GPO is applied to the user.

The user has not logged on since the GPO was created.

Have the user log off and log back on. Ensure that the user is authenticated by the domain controller.

The GPO did not run.

Run Gpresult to verify that the GPO runs.

The user cannot access Active Directory.

Check to see if the user can access Active Directory.

The user cannot access the SDP.

Use ping to test connectivity. Check the user’s permissions on the SDP.

Problem:

When a user activates a document with the extension used in a published application, the application does not install.

Problem Causes Solutions Auto-install is not set.

Ensure that Auto-Install This Application By File Extension Activation is selected on the Deployment tab in the Properties dialog box for the package.

Problem:

When a user activates a document with the extension used in a published application, an unexpected application automatically installs.


The precedence of filename extensions has not been set properly.

Check to see that the File Extensions tab in the Software Installation Properties dialog box has the correct application precedence set.

Group Policy did not run. Check the GPO console to make sure the GPO manages the computer. Run Gpresult for the computer to ensure that the GPO is applied to the computer.



8-18


The computer cannot access Active Directory.

Use ping to test connectivity to the domain controller.

The computer cannot access the SDP.

Use ping to test connectivity to the SDP.

Problems with the Windows Installer package.

Install the package on another computer and make sure the package can be opened.

The user does not have the appropriate permissions to read the Windows Installer package from the SDP or to install the application to the installation target folder as defined in the package.

Verify the user has Read permission on the SDP and Write access to the installation target directory.

Problem:

A user who has never installed a managed application selects the application to install. The installation begins and one of many error messages appears.


Problems with the Windows Installer package.

Install the package on another computer and make sure the package can be opened.

The user does not have the appropriate permissions to read the Windows Installer package from the SDP or to install the application to the installation target folder as defined in the package.

Verify the user has Read permission on the SDP and Write access to the installation target directory.

Problem:

A previously installed, assigned application is unexpectedly removed.


The Uninstall Applications When They Fall Out Of The Scope Of Management check box in the Advanced tab of the Software Installation Properties dialog box is selected and the scope of management has changed.

Check to see if the GPO containing the managed application still applies to the user or computer.



8-19


The software is managed by a GPO linked to a site or OU and the computer moved to a new site or OU.

Check to see if the computer has moved to a new site or OU.

Problem:

The user receives an error message such as The Feature You Are Trying ToInstall Cannot Be Found In The Source Directory.


Network or permissions problems.

Make sure the network is working correctly. Ensure that the user has Read and Apply Group Policy permission for the GPO. Ensure that the folder containing the application on the SDP is shared. Ensure that the user has Read permission for the SDP. Ensure that the user has Read permission for the folder containing the application on the SDP.

Problem:

After removal of an application, the shortcuts for the application still appear on the user’s desktop.


The user has created shortcuts and the Windows Installer service has no knowledge of them.

The user must remove the shortcuts manually.

Automatic upgrade of the application has left shortcuts for the application being upgraded.

Check to see if there is a new version of the application, and if so, delete the shortcuts

Problem:

The user attempts to install a published or assigned application and receives an error message such as “Another Installation Is Already In Progress.”


The Windows Installer service is already running another installation.

The user should wait for the installation to complete and try again later.



8-20

Problem:

The user opens an already installed application, and the Windows Installer service starts.


An application is undergoing automatic repair.

The user must wait for the installation to complete.

A feature is being added.

The user must wait for the installation to complete.

Problem:

The administrator receives error messages such as “Active Directory Will Not Allow The Package To Be Deployed” or “Cannot Prepare Package for Deployment.”


The Windows Installer service cannot communicate with the computer on which the SDP is located.

Use ping to test connectivity with the SDP.

The package is corrupted. Install the package on another computer and make sure the package can be opened.



8-21

Lab 8.1 - Use SQL Server Profiler to configure a baseline trace

Scenario

You are the database administrator for Microsoft Dynamics NAV 2009 2009 at Woodgrove Construction. Users of Accounts Payable information report that they experience intermittent access to their data. Access is slow even when available. Sometimes they cannot post transactions to the database. You decide to use SQL Server Profiler, System Monitor and Database Tuning Advisor to troubleshoot the problem.

Challenge Yourself!

In this exercise you will configure a baseline trace that you can use as the initial investigative trace for performance issues in the Microsoft Dynamics NAV 2009 Demo database. This type of trace is generally the first step in the data-gathering process, letting you determine which additional filtering or events you need to add to focus on particular performance issues. The main tasks for each exercise are as follows:

1. Create a New Trace in SQL Profiler. 2. Specify options on the General Tab. 3. Specify options on the Events Tab. 4. Specify Additional data columns. 5. Execute queries against the demo database and observe what is

captured in the Profiler.

Step by Step

Step 1: Create a New Trace

1. Launch SQL Server Profiler. 2. From the File menu, choose New Trace. 3. Connect to your SQL Server instance for Microsoft Dynamics NAV

2009 Demo Database.

Step 2: Specify Trace Settings

1. On the General tab, specify the following options: a. Name of the trace b. Blank template c. Save to file and use the default file name d. Maximum file size of 50MB e. Enable file rollover



8-22

2. On the Events tab, select the check boxes for the following events: a. SQL:BatchCompleted b. RPC:Completed c. Showplan XML

3. Specify the following additional data columns.

a. CPU b. Reads c. Writes d. Start Time e. End Time

Step 3: Execute Queries

1. Run the trace. 2. Using SSMS, execute several queries against the Microsoft

Dynamics NAV 2009 Demo database and observe what is captured in Profiler.

3. In SQL Server Profiler, stop the trace. Close Profiler.



8-23

Lab 8.2 - Configure a System Monitor Counter Log Challenge Yourself!

In this exercise, you will configure a System Monitor counter log, which you can use to correlate data between Profiler and System Monitor. The main tasks for each exercise are as follows:

1. Create a New Log Settings File in System Monitor. 2. Add Counters SQLBuffer Manager and SQLBuffer Statistics. 3. Set the capture interval and specify user credentials. 4. Start the capture.

Step by Step

Step 1: Create a New Log

1. Launch SQL Server Profiler 2. From the File menu, choose New Trace. 3. Connect to your SQL Server instance for Microsoft Dynamics NAV

2009 Demo Database.

Step 2: Add Counters to the Log

1. Click Add Counters and add the following counters: a. Network Interface \ Output Queue Length b. Processor \% Processor Time c. SQL Server:Buffer Manager \ Buffer Cache Hit Ratio d. SQL Server:Buffer Manager \ Page Life Expectancy e. SQL Server:Buffer Statistics \ Batch Request/Sec f. SQL Server:Buffer Statistics \ SQL Compilations/Sec g. SQL Server:Buffer Statistics \ SQL Re-compilations/Sec

2. Set the interval to one second. 3. Specify a user to run the counter log and enter the user’s password 4. Leave the Log Files and Schedules tabs at their defaults.

Step 3: Start the Counter Log

1. Click OK. By default, System Monitor stores log files in the folder C:\PerfLogs. If this folder does not yet exist, you are prompted to create it. Click Yes.

2. Right-click your new counter log and choose Start.



8-24

Lab 8.3 - Analyzing a Workload in DTA Challenge Yourself!

In this exercise, you will create a workload file and then use that workload file as a source for DTA to source for data to analyze for performance improvements. The main tasks for each exercise are as follows:

1. Create a New Tuning Trace using SQL Server Profiler. 2. Execute several queries against the Microsoft Dynamics NAV 2009

Demo Database. 3. Start workload analysis on the workload file that you just created

with SQL Server Profiler. 4. Review the Database Tuning Advisor recommendations.

Step by Step

Step 1: Create a New Tuning Trace

1. Open SSMS and connect to your SQL Server instance. 2. Open a new query window and change the context to the Microsoft

Dynamics NAV 2009 Demo database. 3. Open SQL Server Profiler (choose Tools, SQL Server Profiler),

connect to your SQL Server instance, and create a new trace. 4. Specify the trace template called Tuning and set Profiler to save the

trace to a file. 5. Start the trace. 6. Switch back to your query window and execute several queries

against the Microsoft Dynamics NAV 2009 Demo database. 7. Stop the trace and close SQL Server Profiler. 8. Close SSMS without saving your queries.

Step 2: Run the Database Tuning Advisor

1. Start Database Tuning Advisor and connect your SQL Server instance.

2. If not already created, create a new session. 3. Specify a name for the session. 4. Select the workload file that you just created in SQL Server Profiler. 5. Select Microsoft Dynamics NAV 2009 Demo database for workload

analysis.



8-25

6. Select the check box next to the Microsoft Dynamics NAV 2009 Demo database and leave the default for all of the tables.

7. On the Tuning Options tab, leave all default options. 8. Start the analysis (Click Start Analysis on the toolbar.) 9. After the analysis is complete, review DTA’s output for

recommendations and look at each report DTA generated for the workload.



8-26


1.

2.

3.


na2009 enus ic

Technology

listening

listening

properties

developer

business logic

sql server

sql server

query optimizer