I am working with a new customer whose internal security policies will not allow the entry of the SQL SA password into the console. Is there an alternative to using the SA account? This will be a version 7 product update 9 install.
I am working with a new customer whose internal security policies will not allow the entry of the SQL SA password into the console. Is there an alternative to using the SA account? This will be a version 7 product update 9 install.
@Elaine: Did you ever got a solution to your issue? I have also come across a similar situation where the client will not share the 'sa' password due to security reasons. Is it possible to use another account instead of 'sa' during Console configuration?
We were not able to use an account other than SA. The client's SQL team changed the SA account password to a temporary value which they provided to us for the duration of the configuration then changed it back. X3 transactions function fine. When you need to create a folder the SA password has to be changed back to the same temporary value. The copy of users from one folder to another does not work you have to create the users in each folder. There may be other admin type functions that have issues but we have not run into them for this client.
This is a good workaround. We suggested the same to our client, however, they decided not to change the password but instead typed in the password whenever we needed it. Not the best way to work, but it got us through.
*Community Hub is the new name for Sage City