New answers tagged

0

Make sure You are backing proper content database Customisations that are made to file system you need to manually copy over


0

You may have backed up the wrong database. From Central Admin -> Manage Content databases, get the correct content DB name for your production web application and make sure that DB is backed up. Before backing up it is good to set the DB to read only. Before restore to Dev farm, make sure all the solutions in your Production farm are available in the dev ...


0

Just to clarify, are you saying you export the Sharepoint list to excel and then upload it to somewhere else outside of Sharepoint? Depending on why you upload it to somewhere else, why don't you use SQL Server Reporting Services to create a report on the data and have that report saved as a pdf/excel file to a set location at timed intervals? ...


1

We are using the same way, we have DNS entry which points to SQL server. We prefer the DNS entry upon SQL alias. For DNS entry, in case of failover down timer is higher then sql alias. You can go either SQL Alias or DNS entry. You can read the below blog for nice comparison: https://junfengzhang.com/2014/08/16/dns-alias-vs-sql-server-alias/


1

My answer for the question is simply NO. Your SharePoint Server is no more live. As you have already mentioned in the question that you have uninstalled the SQL server from Windows Server 2012, then all databases deleted from the server. As we all know that, SharePoint works on SQL server database as it's a back-end. So in your case SharePoint is ...


0

We determined that there was a load-balancing issue affecting the SharePoint environment overall which contributed to the (otherwise inexplicable) performance issues in the update query. N.B. - the performance issue stemmed from SharePoint Designer 2010 enabled sites. The Microsoft guidance on partitioning suggested that our environment could handle more ...



Top 50 recent answers are included