2

SharePoint Server farm creates 4 types of databases Configuration Database (SharePoint_Config ) Central Admin Database (SharePoint_AdminContent_ ) Service applications Database Content database Configuration databases, central admin and service application database are created when we run SharePoint configuration wizard. Configuration database - This ...


2

No, SQL Server 2016 is not supported with SharePoint 2013. As noted, maximum is SQL 2014 although that requires a baseline patch level (which you should have well exceeded by now given you're current on SharePoint patches).


2

Nope, you can't create a content database through CSOM.


2

Only when you (re)run Convert-SPWebApplication will this be permanent -- unless it came from another farm with either a different version of SharePoint or lower patch level on the same version of SharePoint. Make a SQL backup first!


1

I'm sure there are other, more optimal, solutions but this gets the job done: $spDbs = Get-SPDatabase $db = $spDbs[0] [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO') | out-null $s = New-Object ('Microsoft.SqlServer.Management.Smo.Server') $db.ServerName $dbs = $s.Databases #Retrieves the last backup dates - both for FULL and ...


1

Did you have a custom solution/feature related to "VDR_Mail_Event_Solution" on you SharePoint 2013 farm? If you have deployed custom solutions/features on your SharePoint 2013 farm, to make sure them work on your SharePoint 2016, you need to re-deploy them on your SharePoint 2016 before you mount database on SharePoint 2016 farm. Or, if you don't continue ...


1

I've had this happen before, I ended up using backup-spsite and restore-spsite commands instead. It is not fast but you can accomplish the same end result.


1

I fixed it by doing the following: Get the GUID of your mounted content DB from the new web app. Get the GUID of your original Content DB from the new wep app. Update your mounted content DB GUID in the new web application with the help of your databases team or thru the PowerShell


1

This error is usually caused by lack of registered assemblies in web config. Review the webconfig files and confirm that you have all necessary assemblies registered. To further troubleshoot I would review the Windows event logs, and use process monitor to see what issues are occurring with your IIS process.


1

you can have multiple database across multiple SQL server for the same web applications. I have same kind of requirement and working without any issue. Yes farm backup and restore method will work as well, because when you perform the restore it will ask you where to restore. at that time you can tell the sql instance name.


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