Greetings,
I'm just looking for opinions here. An organization I work with currently has six salespeople. The organization is using Active Directory. Four of the six people are in the "main" office, and the other two have their own offices. As of now, each of the six salespeople have their own unique database.
The manager wants to merge all of these databases into a centralized database. The best option I have in mind for this is to install ACT on the main offices domain controller and import all of the data from the six databases.
The four users that have LAN access can log into the centralized database without too much performance impact, but what about the two users on the WAN? Through drive mapping, I could easily give them access to new "main" database and have them log in like the other users, but I'm afraid that would be extremely slow.
The other option I have in mind, for these two, is to create remote databases - that way their only interactivity with the main database is when they're synchronizing. The sync might be a little slow, but otherwise they would be working out of a local copy of the database.
Ultimately, management wants to have access to every record for every salesperson. I think this route will accomplish this with minimal performance impact to the users. What do you think?
Thanks in advance.
~Melagan
______
"It's never too late to become what you might have been.
I'm just looking for opinions here. An organization I work with currently has six salespeople. The organization is using Active Directory. Four of the six people are in the "main" office, and the other two have their own offices. As of now, each of the six salespeople have their own unique database.
The manager wants to merge all of these databases into a centralized database. The best option I have in mind for this is to install ACT on the main offices domain controller and import all of the data from the six databases.
The four users that have LAN access can log into the centralized database without too much performance impact, but what about the two users on the WAN? Through drive mapping, I could easily give them access to new "main" database and have them log in like the other users, but I'm afraid that would be extremely slow.
The other option I have in mind, for these two, is to create remote databases - that way their only interactivity with the main database is when they're synchronizing. The sync might be a little slow, but otherwise they would be working out of a local copy of the database.
Ultimately, management wants to have access to every record for every salesperson. I think this route will accomplish this with minimal performance impact to the users. What do you think?
Thanks in advance.
~Melagan
______
"It's never too late to become what you might have been.