The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Is there a need to cut new remote client databases going from 7.0.1 to 7.5.1?
Posted: 17 Jun 09 9:29 AM
|
I have looked through the 'Upgrading Sage SalesLogix from Version 7.0.1 to 7.5.1 document and I do not see anything that says a new remote client database is required for users when you make this upgrade.
We have received mixed responses from business partners with one saying that we would want to cut new remote client databases due to the schema changes.
Does anyone have any solid information on this that would confirm it?
Thanks |
|
|
|
Re: Is there a need to cut new remote client databases going from 7.0.1 to 7.5.1?
Posted: 18 Jun 09 12:39 AM
|
| We cut new databases when we upgraded. We don't have a lot of trust in synchronization, as no matter what we do, the data degrades over time. Adding that to the larger set of changes in the upgrade process, we didn't want to take any more risk. We looked at the upgrade as an opportunity to get new remote databases set up everywhere. |
|
|
|
Re: Is there a need to cut new remote client databases going from 7.0.1 to 7.5.1?
Posted: 30 Jun 09 3:36 AM
|
My take (keeping in mind that you are upgrading through 2 major versions (7.2 and 7.5)):
Rather than interpreting the fact that the documentation may have failed to mentioned cutting a new DB as not needing it, I would interpret it as an Implicit "you should cut a new DB".
I will only assume that you don't need to cut remotes it if the documentation expressly states so.
|
|
|
|
Re: Is there a need to cut new remote client databases going from 7.0.1 to 7.5.1?
Posted: 24 Nov 09 5:33 PM
|
My two cents:
The documentation simply says in effect: run the Remote Client Installation (and the service pack), launch the sync client, run a sync and you're ready to go.
What I have found in practice is this:
When the servers hosting the SLX Services (Sync Server is probably the key here) before and after the upgrade are the same, then the instructions above work and we've had few problems with remotes. This includes at least one 6.2 to 7.5.1 upgrade.
But very often customers want to use the upgrade as a chance to move SLX to newer more powerful servers. Every time I do that remotes get corrupted and we have to cut all new databases. There my be a sequence of steps involving final syncs, copying the log files to the new server, and reconfiguring sync that allows you to upgrade SLX and move it to a new server while keeping all your remotes, but I haven't found it yet. |
|
|
|
Re: Is there a need to cut new remote client databases going from 7.0.1 to 7.5.1?
Posted: 17 Sep 10 10:40 AM
|
Raul,
We would absolutely tell you when a DB needs to be cut. If we don’t say this explicitly, it does not need to be done.
There were times in the past when we had no choice and introduced an incompatibility that forced an upgrade to require new remotes OR the Provider on the server or client had to be upgraded simultaneously. We go out of our way not to cause these types of troublesome upgrades.
Unless stated in the doc – no new databases are required.
Thanks
Mim |
|
|
|
Re: Is there a need to cut new remote client databases going from 7.0.1 to 7.5.1?
Posted: 17 Sep 10 12:22 PM
|
Mimi,
Thank you for the response.
I failed to point out that most of the times there are external factors that I consider would force a new Remote, but at least this gives us an official stance from SAGE.
That being said, I still suggest that anyone considers their own Infrastructure and known challenges before making a decision.
|
|
|
|