12-05-2017 10:32 AM
ACT Version: ACT! Premium v20
Database Location: We need the database to be located on a separate machine from the ACT! Application accessed by the users
Database Version: We are looking to install ACT! on SQL Server 2008R2
Operating System: Windows Server 2008R2
We host various clients ERP instances in our hosted environment and have the need to deploy ACT! Premium v20 for different clients. We have 4 application servers (virtualized servers) and 4 SQL servers. Our need is for our clients to launch ACT! from the application server accessing the ACT database on one of the 4 SQL servers.
Given that we have multiple clients in this environment we need to ensure that their ACT! Instances are on separate SQL databases.
All of the literature I’ve read (and received talking to the tech support chat) has been that ACT! must be installed on the same machine as the database and the database must be named ACT7. These requirements won’t work for us since we do not allow direct access to the SQL server by our client’s users and we can’t have multiple clients all accessing the same ACT7 database.
Has anyone deployed ACT in this manner and have information/literature they can share for how to deploy in this manner?
12-06-2017 01:48 AM
In order to install the ACT7 instance correctly, we recommend using the Act! installation. However, once the SQL instance is created and the databases are created/imported, Act is no longer necessary on the SQL server and the database can be remotely accessed from other Act installations on the network.
Essentially, once the database instance is created, you can have your clients access the database from the application server - no additional work needed for this. We do recommend keeping a copy of Act on the SQL server for troubleshooting purposes though.
While Act! will only work with an SQL "instance" named ACT7, you can host multiple separate databases, each with separate log-in credentials, on that one instance. Act database logins are completely localised to the database they're created in - so Act! database logins, even for an administrator, will not allow access to the other databases - or access to the SQL Server instance.
If for whatever reason, you really don't want to host more than one client's database on a single SQL instance - you'll need to create multiple SQL servers - either through VMs or physical machines, as unfortunately Act is 'hard-coded' to only work with an SQL instance called ACT7.