1. Backup & Restore a copy of the Production Database:
1. Create a backup of the SalesLogix database. Restore the backup with a new name on the database server.
2. Run Sysdba Update Script against the development SalesLogix database.
sp_change_users_login ‘Update_One’, ‘sysdba’, ‘sysdba’
2. Move the Production logging path to the development server:
1. On the development environment server, create a folder to act as the development logging path directory.
Example: C:\SalesLogixQA
2. Right-click the C:\SalesLogixQA folder, then click Properties.
3. On the SalesLogixQA Properties window, click the Sharing tab.
4. Select the Share this folder radio button
5. Click the Permissions button.
6. On the Permissions for SalesLogixQA window, click the Add button.
7. On the Select Users, Computers, or Groups window, in the Enter the object names to select field, enter the name of the domain user running the SalesLogix services.
User: slxservice
8. Click the Check Names button
9. Click the OK button.
10. On the Permissions for SalesLogixQA window, in the Group or user names field, click slxservice.
11. In the Permissions for slxservice area, select the Full Control checkbox
12. Click the Apply button.
13. Click the OK button.
14. On the SalesLogixQA Properties window, click the Security tab.
15. Repeat steps 6-13 to add the slxservice user to the folder’s security properties.
16. On the SalesLogixQA Properties window, click the Apply button.
17. Click the OK button.
18. Copy the Documents and Library folders from the production logging path to the C:\SalesLogixQA folder.
Note: For each development environment, create a separate logging path to avoid cross-environment contamination.
3. Change the Logging Path for the development database:
1. Use a SQL tool such as SQL Server Management Studio to perform the following statements:
Note: The following statements must not be executed through the Execute SQL tool in the SalesLogix Administrator. Doing so will cause data corruption in the production environment. These steps MUST be performed before creating a connection to the development database via Connection Manager.
For environments that do not contain a Synchronization Server license, steps 1 and 2 below must still be followed to avoid accidental deletion or corruption of production attachments and library documents.
§ UPDATE sysdba.BRANCHOPTIONS SET AttachmentPath = '\\SERVERNAME\SalesLogixDevSync\Documents' WHERE SiteCode = (SELECT PrimaryServer FROM sysdba.SYSTEMINFO WHERE SystemInfoID = 'Primary')
§ UPDATE sysdba.BRANCHOPTIONS SET SalesLibraryPath = '\\SERVERNAME\SalesLogixDevSync\Library' WHERE SiteCode = (SELECT PrimaryServer FROM sysdba.SYSTEMINFO WHERE SystemInfoID = 'Primary')
§ UPDATE sysdba.SYNCSERVER SET ServerPath = '\\SERVERNAME\SalesLogixDevSync' WHERE SiteCode =(SELECT PrimaryServer FROM sysdba.SYSTEMINFO WHERE SystemInfoID = 'Primary')
§ DELETE FROM sysdba.SYNCSERVICEFILE
§ DELETE FROM sysdba.SYNCTRANSFER
§ DELETE FROM sysdba.SLXWEBSERVER
4. Create a new connection in the SalesLogix Connection Manager.
For SQL 2008 database servers you must perform the following steps in order with creating a new connection.
1. Provide connection name and the new connections property dialog window will open.
2. On the Connection tab provide database server name.
3. Enter sysdba user name and password.
4. Check the box to remember password.
5. Select the SalesLogix database for the connection. DO NOT TEST CONNECTION AT THIS POINT.
6. Navigate to the tab named ‘All’.
7. Scroll down to Persist Security Info and double click to open. Set the value as True.
8. Click OK.
9. On the All tab, scroll up to Integrated Security and double click to open.
10. Click reset value. Although the value is initially blank, after resetting value should still be blank.
11. Navigate back to the Connections tab.
12. Test Connection.
13. If connection test succeeds click OK to save connection and exit the Connection Manager.
5. Navigate to SalesLogix Client and set up datalink to the development database.
