11/26/2024 8:26:09 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
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!
Forum for off topic and general discussion. View the code of conduct for posting guidelines.
|
|
|
|
SLX Db Setup
Posted: 12 Feb 08 12:01 PM
|
| I have never really understood the manner in which SLX is installed on our system. We have a SQL Server box, server A, that has our SalesLogix database. However, users connect to server B with the client. Server B also has a SalesLogix database. All of the data seems to make its way to server A, so what is the purpose of server B? Any insight would be appreciated. |
|
|
|
Re: SLX Db Setup
Posted: 12 Feb 08 12:58 PM
|
| What you are describing is *not* a typical setup for SLX. SLX has only one database, so this other database likely has some other purpose. Did a business partner set this up for you? Maybe check with them? |
|
|
|
Re: SLX Db Setup
Posted: 12 Feb 08 1:18 PM
|
| Unfortunately speaking with our original SLX business partner is not an option at this point. I am moreso curious to hear if anyone else has seen a SLX setup similar to this. I have read through the install procedures for SLX, and or setup does not make sense to me. For instance, we also use Mas500, but Mas500 runs solely off of server A. |
|
|
|
Re: SLX Db Setup
Posted: 12 Feb 08 1:24 PM
|
The typical setup for SLX is this:
1) A single database
2) A SLX Server component
3) Sync Server (if remotes are involved)
4) Clients (the SLX installs on the desktops)
1, 2, and 3 can all be on the same server if needed, but they don't have to be. If you have some other database in the picture then there has to be some non-SLX need for it, such as some staging database for imports or something else such as for replication or redundancy of some kind.
SLX itself has only *one* database. |
|
|
|
Re: SLX Db Setup
Posted: 12 Feb 08 4:28 PM
|
Does server B have SQL Server installed too, or just the database?
Try querying some of the entries in the tables to find out when they were last updated
Select Max(CreateDate), Max(ModifyDate)
from Account
etc
Maybe it's just an old db that's not required? Ryan's comments are bang on the mark.
Phil |
|
|
|
Re: SLX Db Setup
Posted: 13 Feb 08 8:58 AM
|
| Good thought Phil, that was my plan for when I got in today. Upon doing so, I can see that both server A and server B have the same minimum dates. However, server A has current maximum dates whereas server B's maximum dates stop around 4/18/2007. I would love to jump the gun and say that this is just an older db that is no longer in use, but then that would bring up the question of why clients connect to server B. I should also note that we use DynaLink, run on server B, to migrate data into Mas500. |
|
|
|
Re: SLX Db Setup
Posted: 13 Feb 08 9:01 AM
|
| Does Server B really contain a database, i.e. a saleslogix.mdf file? It could be that Server B has the SLX Data Provider, perhaps along with sync and other SLX programs. That's why clients would connect to it. I remember attending an Insights session when the presenter suggested that the Provider be installed on the sync server, rather than the database server, when sync is involved. |
|
|
|
Re: SLX Db Setup
Posted: 13 Feb 08 9:18 AM
|
| There are physical db files on server B. We do not have remote users, so we do not run the syn server. |
|
|
|
Re: SLX Db Setup
Posted: 13 Feb 08 9:49 AM
|
Phil & Ryan are both correct. I'd just like to add that SalesLogix employees a "Three Tier" arrangement where the SQL Server is connected to the SalesLogix Server via an ADO access method (either SQL Native Client or OLE-DB). That's the connection which uses the 'sysdba' user. Clients log into the SalesLogix Server at a higher level using the SalesLogix OLE-DB DB Provider access method. Although both SQL Server and SalesLogix Server are usually installed on the same physical server, they can be installed on separate physical servers. The easy way to determine your arrangement is to bring up the SalesLogix "Connection Manager" program which is on your SalesLogix Server (Server 'B'). Look at the definition of the connection name which your clients use. That will show you which SQL Server is being used and the actual database on that server.
Most likely, the additional SalesLogix database was created when the application was first installed. If you look at the size of its physical files (.mdf & .ldf), the used database will be much smaller than the production database.
Also, before changing the existing arrangement, you should really determine why it was originally set up that way. Since you mentioned than your company also has MAS500, the current arrangement may have been employeed to ease the integration between both applications. Do you use Dynalink for integration? If so, there may be hard coded references pointing between the two databases. So, please be very careful.
|
|
|
|
Re: SLX Db Setup
Posted: 13 Feb 08 10:16 AM
|
| Thank you Robert Levine. As soon as you said "Three Tier" I knew you were correct. From the connection manager, server A is our production server, and server B is our development server. As stated above, we do indeed use DynaLink. My reason for question this setup was not to alter it, but to get a better understanding of it. I appreciate all the responses. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|