A few database thoughts for Sage SalesLogix installation considerations and planning
I had a dream last night that I was running queries in a database. I ran the following query:
SELECT * FROM [paul].[thoughts]
The result was no records found.
Who knew?
I wanted to write an article that might provide assistance with installation and planning for SalesLogix with MS SQL Server with a focus on MS SQL Server 2008 considerations in particular. My intention is this: To help the average IT Administrator plan for a Sage SalesLogix deployment of less than fifty (50) user seat client side installation for an on-premise solution and answer some common questions.
1. Database Qualifications with SalesLogix
SalesLogix v7.5 works with both MS SQL Server and Oracle. With Oracle, that is Oracle 11g or Oracle 10g R2. With MS SQL Server, there are two versions available for compatibility: MS SQL Server 2005 and MS SQL Server 2008. MS SQL Server 2008 came into compatibility with SalesLogix v7.5 SP2 but worked just fine before that qualification announcement.
Disclaimer: Please refer to the Sage SalesLogix system requirements for the exact and current details, like the SalesLogix Service Packs, etc., because future releases from both Sage and Microsoft make these items a fast moving target.
2. MS SQL Server installation with SalesLogix
I get asked about how to install MS SQL Server for SalesLogix with some regularity. The frequent requests are especially understandable for the server-side installation tasks as they are not documented well because of the nature of the rapid changes by both Microsoft and Sage. Many times a client is doing the planning far in advance of having the software media in hand as well. Here is my answer for the bare minimum installation:
When MS SQL Server is installed there are a few services that can be installed, like Database Services, Analysis Services, Reporting Services, Notification Services, Integration Services, Client Components and Documentation & Sample Data. Most of them are not needed unless they are being shared with other applications or other factors like advanced requirements.
Here is what is recommended for SalesLogix to run properly:
- Under Instance Features: Database Engine Services. Under shared features: Client tools Connectivity, Client tools backwards Compatibility, SQL Server Books Online, Management tools – basic and complete, the two SDK options are fine. The rest are not needed.
- Use Mixed Mode for the security model; record the SA user password for database creation and for best management practices.
- The other installation screens are defaulted for Sage SalesLogix usage.
3. Server Configuration Tips
For sizing the RAM for the data load, I am going to assume that we are dealing with a single application database and a single purpose server for the database services functionality. This is not always true, esp. in today’s “do more with less” IT world. But let us begin with this ideal, as adjustments can be made according to the particular needs of a given situation.
A good minimum would be 3 Gb of RAM; for Windows 2003 Server that is 32 bit. If you are running Windows 2008, consider more, especially if 64 bit. I also recommend one Gb for each Gb of database size; in other words, if the database has 4 Gb of data and you have 50 users. You will want to consider having 7 Gb of RAM as a good starting point for responsiveness.
For configuring SalesLogix Connection Manager with MS SQL Server 2008, there is a tweak that is needed for the Connection settings:
- Open the SalesLogix Connection Manager
- Add or Edit the required connection to ensure you select the SQL Server Native Client 10.0 provider.
- Make the normal changes to define the Server/Database and sysdba/password settings.
- Select the All tab
- Locate the option Persist Security Info option and change the setting to True
- Locate the option Integrated Security and press the Edit Value button, then press the Reset Value button.
- Ok.
This should correct the issue for the client connections with the connection resetting to blank password. Confirm by logging in to a SalesLogix application.
The matching SQL Native client tool will need to be installed on each additional server that has components that will be connecting and opening the SalesLogix database.
4. Client Installation tips for SQL Native Client Components.
Always make sure that the SQL Native client tool for the network users matches the server edition (2005, 2008, etc.) and database service pack.
Let’s assume that you have MS SQL Server 2008 SP1 (10.00.2531.00). You will want to locate and download the matching SQL Native client for the client workstations.
- I will start a web search for the matching Microsoft SQL Server 2008 Feature Pack web page that has the download installation files. In this case, the matching Service Pack is 10.00.2531.00, and I will confirm to make sure that there is an exact number match. This can be tricky because Microsoft will release a Feature Pack for each Service pack that is released.
- Once the right page is found, I will need to scroll down the page to find the Microsoft SQL Server 2008 Native Client files.
- Download the appropriate installation files for the bit edition of the client workstations (32 bit vs. 64 bit etc.) The download file will be named (sqlncli.msi).
- Copy the file(s) to an installation point, usually a shared folder, on the network. A good tip is to place them in the folder where the network client build is located.
Note: The MS SQL Native client doesn’t need to be downloaded for disconnected remote users. The MS SQL Express will install the SQL Native Client Components.
The installation step for the SQL Native Client can be performed on the client network workstations independent of the Sage SalesLogix application. Installing this program will save time on the client network workstation for a deployment for upgrade.
Hopefully this article answers some common questions for planning out MS SQL Server installation tasks for an on-premise deployment related to the database.
“I have traveled the length and breadth of this country and talked with the best people, and I can assure you that data processing is a fad that won’t last out the year.” –The editor in charge of business books for Prentice Hall, 1957
If you would like to learn more tips or have a CRM topic you would like us to write about please contact Simplesoft Solutions, Inc. in one of our Cincinnati/Dayton (OH), Charleston (WV), or Charlotte (NC) surrounding area office locations:
Dayton, Ohio Office:
Simplesoft Solutions, Inc.
550 N. Main St. Suite A
Springboro, OH 45066
Phone: (937) 885-1204 x 3204
Fax: (937) 885-3580
sales@simplesoft.net
Ripley, WV Office:
Simplesoft Solutions, Inc.
710 Random Rd.
Ripley, WV 25271
Phone: (304) 521-2387
Fax: (937) 885-3580
sales@simplesoft.net
Charlotte, NC Office:
Simplesoft Solutions, Inc.
3635 Eastover Ridge Drive
Charlotte, NC 28211
Phone: (704) 910-3872
Fax: (937) 885-3580
sales@simplesoft.net