Dear Team,
We are planning to change the SQL server in SharePoint farm due to the lifetime expiration of the server by using the below article. Before changing the server we are checking the UDL test.
https://learn.microsoft.com/en-us/sharepoint/troubleshoot/administration/how-to-change-the-database-in-farms
Without the UDL result, we cannot take call to change the SQL Server in SharePoint
UDL test connection is getting failed, but on local and remote servers we are able to connect.
Farm details::
OS 2016
SQL 2016
SharePoint 2019 (2 SharePoint servers APP & WFE)
We are able to connect the SQL instance with the named instance from the local server via ssms.
We are able to connect the SQL instance with the named instance from the remote server via ssms.
We are able to connect the SQL instance with the Alias name from the local server via ssms.
4**. We are unable to connect the SQL instance with the Alias name from the remote server via ssms.**
UDL test connection is getting failed for both the named instance and alias name from the remote server via UDL.
TLS 1.2 is enabled on the SharePoint server and SQL server for both the client and server.
Please provide the best solution to pass the UDL connection.
Hi
@Rahul Gollapalli
,
All Microsoft OLEDB providers are deprecated, and NOT recommended to be used, except
Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL)
.
Check it out here:
https://learn.microsoft.com/en-us/answers/questions/1029316/ssis-connect-to-azure-sql-database-with-mfa.html
The Microsoft OLE DB Provider for SQL Server ships with the OS, but it is more than 20 years old. SQL Server Native Client 11.0 is a little better.
The most recent OLE DB provider is MSOLEDBSQL19, you can download it
here
.
