Instead of using a SQL local account, it is preferable to use Active Directory-based account authentication. A few reasons are:
1. Only Windows AD accounts need to be managed
2. SQL Account will have to have a password reset and the Statistica DSN will have to be updated. This could cause downtime
*undisclosed password
Hi,
I assume you refer to the repository connection?
I think from a technical perspective this is already possible (I recall customers who did this) but it is simply not recommended since Enterprise users usually have alternative sql clients (Management Studio) and therefore could alter (since the repository connection needs write permissions) the repository content without Statistica audit log entries. This would likely break validation for pharmaceutical customers. Therefore a SQL account with disclosed password is recommended.
Best regards,
Sören