Professional Documents
Culture Documents
Installation and Configuration in Microsoft Dynamics Nav 2009
Installation and Configuration in Microsoft Dynamics Nav 2009
Installation and Configuration in Microsoft Dynamics Nav 2009
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.
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
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:
Look for a complete list of manuals available for purchase on the Microsoft
Dynamics website: www.microsoft.com/Dynamics.
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.
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.
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.
Student Objectives
What do you hope to learn by participating in this course?
1.
2.
3.
CHAPTER 1: ARCHITECTURE
Objectives
The objectives are:
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.
The two-tier architecture also puts the data and data manipulation layers (DML)
on the server in the native database and SQL Server configurations.
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 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.)
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.
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).
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 computer hosting SQL Server.
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.
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:
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. 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.
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.
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.
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:Po
rt Domain \User
Summary
The new three-tier multithreaded architecture model of Microsoft Dynamics
NAV 2009 provides process benefits beyond the two-tier architecture model's
capability.
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.
2.
3.
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.
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.
Next the focus is about how to select the hardware and software prerequisites for
Microsoft Dynamics NAV 2009.
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
• 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 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:
This platform provides reliability that helps systems remain available even if
problems occur.
Windows Server 2003 R2, Datacenter Edition, is available in both 32-bit and 64-
bit versions and includes the following:
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.
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.
• Relational Database
• Notification Services
• Analysis Services
• Reporting Services
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.
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
Reporting Services
Reporting Services are used by Microsoft Dynamics NAV to write, manage, and
deliver rich reports.
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.
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.
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 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:
1.
2.
3.
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 complete product with sample data is supported on the following operating
systems:
NOTE: To install the Microsoft® Outlook® Add-In for Microsoft Dynamics NAV
2009, you must install Outlook before running the installer.
• 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
1. Run setup.exe.
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.
• 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.
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.
1. Run setup.exe.
The Welcome to the Microsoft Dynamics NAV 2009 Installer page appears.
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.
9. Click Apply.
10. Click Install.
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.
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.
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.
Keyboard Shortcuts
This table indicates the shortcuts in the RoleTailored Client and the Classic
Client:
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:
Step by Step
Step 1
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.
Step 2
Summary
This chapter covers the installation of Microsoft Dynamics NAV 2009 Role
Based Client.: In particular it covers:
1.
2.
3.
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.
• 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.
The dialog box can be accessed from the menu bar as follows:
On the menu bar, click Customize , and then click Customize Navigation Pane.
Another way to access the Customize Navigation Pane is to position the mouse
pointer over the control and right-click.
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.
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.
If you find a link in the Departments pages, you can also add it to the navigation
pane.
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.
4. Select the menu that you want to add the link to, and then click OK.
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.
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.
To restore the default settings, click Restore Defaults and then click OK.
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:
These changes only affect your program, and not those of your colleagues..
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.
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.
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.
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.
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.
To restore the default settings, click Restore Defaults and then click OK.
To open the Customize window to select FactBoxes, click Customize on the right
hand side of the menu bar and select Customize This Page.
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.
• Click Customize on the right side of the menu bar and add or clear a
check mark next to the specific pane.
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.
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
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
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.
Summary
The navigation pane can be customized in many ways using the Customize
Navigation Pane dialog box.
The following are changes that you can make to your Microsoft Dynamics NAV
2009:
1.
2.
3.
Introduction
The new Microsoft Dynamics NAV 2009 Server is a .NET-based Windows
Service application that works exclusively with SQL Server databases.
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.
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.
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.
Click Apply when you have finished entering values to exit back to the Specify
parameters pane in Setup.
After running Setup you can modify Microsoft Dynamics NAV Server settings
by editing CustomSettings.config.
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
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.
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.
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:
Step by Step
Step 1: Access 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.
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.
1.
2.
3.
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.
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:
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.
• 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.
The Startup screen presents a set of options in sections entitled Prepare, Install,
and Join the Community.
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.
1.
2.
3.
CHAPTER 7: DEPLOYMENT
Objectives
The objectives are:
Introduction
Deploying Software is essential to meet the changing application needs of
organizations and provide these benefits:.
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.
Published Applications
Assigned Applications
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 Allows you to target applications to the appropriate
on software set of users. Group Policy security settings are not
management needs. required to target the appropriate set of users.
Deploy software Makes it easy to provide all users in an organization
close to the root in with access to an application. This reduces
the Active Directory administration because you can deploy a single GPO
tree. rather than having to re-create that object in multiple
containers deep in the Active Directory tree.
Deploy multiple Reduces administration overhead by allowing you to
applications with a create and manage a single GPO rather than multiple
single GPO. 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 Makes it easier to determine which instance of the
application only application applies to the user or computer.
once in the same
GPO or in a series
of GPOs that might
apply to a single
user or computer.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
1.
2.
3.
Introduction
Microsoft Dynamics is built on the Microsoft technology stack. Consequently all
the components need to be installed, configured, monitored, and optimized.
In this module we fous on the Microsoft SQL Server 2005 and Windows Server
2003 Group Policy including:
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.
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:
This event indicates that the data file grew automatically. It is not
triggered if you grow the data file explicitly through ALTER
DATABASE.
This event indicates that the data file has been shrunk.
This event indicates that the log file grew automatically. It is not
triggered if the log file is grown explicitly through ALTER
DATABASE.
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).
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.
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.
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.
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.
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.
Constraints
Query Optimizer
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.
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.
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.
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.
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.
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
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
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.
• 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.
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.
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.
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.
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.
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.
USE AdventureWorks;
GO
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.
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.
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.
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.
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.
This table lists the advantages and disadvantages of using the various RAID
implementations typically used with SQL Server 2005.
FIGURE 8.1
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.
Windows Server 2003 provides the following Group Policy troubleshooting tools
to assist you in verifying your configuration and in diagnosing and solving
problems:
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.
Problem:
Published applications do not appear for the user in Add Or Remove Programs in
Control Panel.
Problem:
Problem:
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.
Problem:
Problem:
The user receives an error message such as The Feature You Are Trying
ToInstall Cannot Be Found In The Source Directory.
Problem:
After removal of an application, the shortcuts for the application still appear on
the user’s desktop.
Problem:
Problem:
The user opens an already installed application, and the Windows Installer
service starts.
Problem:
The administrator receives error messages such as “Active Directory Will Not
Allow The Package To Be Deployed” or “Cannot Prepare Package for
Deployment.”
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:
Step by Step
Step 1: Create a New Trace
2. On the Events tab, select the check boxes for the following events:
a. SQL:BatchCompleted
b. RPC:Completed
c. Showplan XML
Step by Step
Step 1: Create a New 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.
Step by Step
Step 1: Create a New Tuning Trace
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.
1.
2.
3.