The Stack Overflow podcast is back! Listen to an interview with our new CEO.

Hot answers tagged

2

I think, check the configuration database server name. Because Config db is the 1st database which is configured during the SharePoint deployment, DB server name will tell you If that is using the SQL Alias or SQL instance name? i usually use the following script to get the config db server name: (Get-SPDatabase | ?{$_.Type -eq "Configuration Database"})....


2

Microsoft Flow could be a good tool to export information from multiple sources like an Azure SQL database. But you should check Azure Functions and Office Graph API as well. This couldn't be a solution if you are thinking in a non code solution but I think it could be great because of all the possibilities that opens up for logging, tracing, checking and so ...


2

MS SQL 2017 is not supported for SP2013 REF: https://blog.stefan-gossner.com/2016/11/04/sharepoint-2013-and-sql-server-2016/


1

You'll likely need to create your own SQL server. SharePoint on prem is designed for SQL on prem. It's definitely going to fall under unsupported by Microsoft if you do manage to get it working anyways.


1

It's a supported case. Check the https://docs.microsoft.com/sharepoint/install/hardware-and-software-requirements#software-requirements-for-sharepoint-server-2016 : Minimum requirements for a database server in a farm One of the following: * The 64-bit edition of Microsoft SQL Server 2014 Service Pack 1 (SP1) * Microsoft SQL Server 2016 RTM * ...


Only top voted, non community-wiki answers of a minimum length are eligible