I have SP2016 and SP2013 On-Premises farms. I would like to consume User Profile Application from SP2016 on SP2013. All the configuration was done successfully but I have SQLAlias with same name (alias name) on both SP2016 and SP2013 Farms, but pointing to a different SQL instances. I am getting an error since SP2013 UPA (consumer) is trying to find the Profile_DB on SP2013's SQL Server instead of SP2016's SQL instance. Is there any workaround without updating SQLAlias at all?

Thanks in advance.

up vote 2 down vote accepted

SharePoint will always call the alias. Because the reference databases (publisher farm) has the same alias, when the consumer farm looks for the Profile database, as an example, it will make a call to the SQL Server used by the Profile database. Because the Profile database is using the alias, ultimately the consumer farm will end up calling it's own SQL Server rather than the SQL Server where the database is hosted.

While you can certainly change the alias for all databases sans the Admin/Config databases of a farm, that is an option but if I recall calls are still made by the consumer farm to the Config database of the publishing farm.

The solution here would be to rebuild one or the other farms using a different alias. If you're using SQL Server AOAG, do not use an alias.

Your Answer


By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.