Is there an alternative to using SA account when configuring the Safe X3 management console

SOLVED

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.

  • 0
    SUGGESTED
    Hi Elaine,

    You can create an account equivalent to the SA and use that instead if you like.

    Sage has never published a minimum set of permissions required for SQL Server to complete an installation that I've seen, so that will be out of reach if that is your next question. Some of the things we do execute during the console database set up include database creation, alter database commands, bulk copy (BCP) and other things like that. You can see the scripts inside the installation folders that the console uses, just search for *.sql. Sage Support will only support the officially documented approach. If you really must avoid the sa account, you can go through all the activities in the console with SQL profiler turned on and distill all the commands and reason out the best SQL Server role to provide it, which is a lot of work by the way.

    Another approach could be to use an equivalent account to the SA, configure X3 with the console, then disable that account inside SQL Server until you are ready to make another configuration within the console, at which point you re-enable the quasi SA account.

    Hope this helps.
    Bob
  • 0 in reply to Delamater
    Thanks for the response. Do you know how I can specify to the console the account name, it appears to not be editable.
  • 0 in reply to Elaine Pigott
    Oh my gosh Elaine! I totally missed this! What the heck was I thinking? I guess I was rushing on my reply. Very sorry about that. Yes, it must take the sa in the console. I checked the xml file in the background, and it is not allowing you to set the account their either.

    So sorry I missed that.

    Bob
  • 0 in reply to Delamater
    I was afraid of that. Based on your first response do you think it would be possible to do the install with the SA account and password then have the customer change the password? In other words at what points does X3 need the current SA password to be in the console - during initial installation and for folder creation or does it need to be correct for normal operations?
  • 0 in reply to Elaine Pigott

    @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?

  • +1 in reply to Leonard Chirongo
    verified answer

    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.

  • 0 in reply to Elaine Pigott

    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.