Have your free copy of GP10

Saturday, May 24, 2008

Microsoft SQL Server configuration

Microsoft SQL Server configuration
This chapter guides you through the Microsoft SQL Server 2005 and the Microsoft SQL Server 2005 Express installation and setup process for Microsoft Dynamics GP. It’s important that you install and set up Microsoft SQL Server according to these instructions. If you’ve already installed and set up SQL Server using different options, you may have to change those options. Changing options after they’ve been set sometimes involves reinstalling SQL Server.
• SAN and NAS disk support
• Selecting a SQL Server collation
• Understanding sorting options
• Installing Microsoft SQL Server 2005
• Installing Microsoft SQL Server 2005 Express Edition
• SQL Server Agent
• Enabling Delete PJournal job
SAN and NAS disk support
Because Microsoft Dynamics GP relies on SQL Server to maintain databases and make databases available, there are guidelines you must follow when configuring SQL Server disk support.
We recommend that you use a Storage Area Network (SAN) or locally attached disk to store your Microsoft SQL Server database files because this configuration optimizes SQL Server performance. By default, use of network database files stored on a networked server or Network Attached Storage (NAS) is not enabled for SQL Server. However, you can configure SQL Server to store a database on a networked server or NAS storage server. Servers used for this purpose must meet SQL Server requirements for data write ordering and write-through guarantees.
If you are using Microsoft SQL Server Express Edition, SAN and NAS disk support isn’t typically used.
For more information, see Microsoft Knowledge Base article Q304261 (go to support.microsoft.com and search for the article number) or contact the SQL Server Support Team.
Selecting a SQL Server collation
A SQL Server collation—a set of rules that determines how character data is sorted and compared—includes character set, sort order, and locale-specific settings. See your SQL Server 2000 or 2005 documentation for more information about collation settings.
The SQL Server collation you select determines how information is presented in
response to SQL queries and affects the performance of the system.
The code page for character data is defined by the Windows locale selected when the operating system was installed. The code page contains the valid set of
characters in your SQL Server database. A character set consists of 256 uppercase and lowercase letters, numbers, and symbols. The first 128 characters are the same for all character sets. The supported character set in the United States is the 1252/ ISO character set.
It is important to select the correct collation for Microsoft Dynamics GP when
you’re installing SQL Server. Using SQL Server collations that include Binary (sort order 50) or Dictionary Order, Case-Insensitive (sort order 52) sorting is required for Microsoft Dynamics GP. To change these settings at a later time, you must reinstall SQL Server and Microsoft Dynamics GP.
You should check the compatibility of all the products you have that will use SQL Server before deciding on the collation option.
Understanding sorting options
Using SQL Server collations that include Binary (sort order 50) or Dictionary Order, Case-Insensitive (sort order 52) sorting is required.
Binary sort order assigns characters numeric values of 0 through 255. Dictionary Order, Case-Insensitive (DOCI) sort order makes no distinction between uppercase and lowercase characters. DOCI is the most common sort order.
The following table shows the differences between Dictionary Order, Case-
Insensitive and Binary.
Installing Microsoft SQL Server 2005
We recommend that you follow the instructions in this section if you have not yet installed Microsoft SQL Server 2005. For information about upgrading SQL Server, see the SQL Server installation documentation. (In the window that appears when you insert the SQL Server DVD, select Browse Setup/Upgrade Help.)
With SQL Server 2005, you can have multiple instances of SQL Server on the same physical server. We recommend that you have a dedicated a server. See your SQL Server 2005 documentation for more information about multiple instances.

No comments: