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

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

Thanks for the response. Do you know how I can specify to the console the account name, it appears to not be editable.

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

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?