Question:

I am a SQL Server developer who is trying to learn/support a SalesLogix implementation. Without understanding the synchronization process between the main database and the remote user databases, I made a lot of changes to territory assignments in the database based on state codes. My boss thought this would be easier and faster than making the changes one by one in the front end. However, now my changes have not been roled out to the remote databases. I have discovered that there needs to be a TEF file for each change I made in order for the remote databases to pick up those changes. At this point, can I backup and restore the main database to each of the remote databases? Is it possible to make changes in the database and roll them out to the remote databases any other way?

Answer:

Practically all of the maintenance, support and customizations for SalesLogix is done with tools built-in SalesLogix. The first thing you need to do is find out what computer the Administrator workstation is installed on.

I suspect you made the database changes using SQL Server Management Studio. This will never roll out to remotes. In the future you need to use the SalesLogix Administrator "Execute SQL..." function found under the "Tools" menu. Through this tool you can make global changes using SQL statement and they will roll out to remotes.

Your current situation cannot be easily fixed by making a backup of the main db and restoring it to the remotes. What you have to do is "cut" a new database for each remote. This is done from the SalesLogix Administrator as well. Under the "Tools" menu is a "Create Remote User Databases..." option. Select this and you'll be able to select the users you want to create the new databases for. Once the databases are created you will have to get them to the appropriate uses and then they will have to attached the new database using the "Attach Remote" utility.