Moving or Renaming a Web Application Content Database

When creating a web application in SharePoint 2013 it will communicate with SQL Server to create the supporting content database. Depending on what steps are used to create the Web Apps it sometimes creates the SharePoint database with a not-so-‘friendly’ database name and it may contain a ginormous GUID, (which I pronounce Goo-id) as part of the database name. When working with these databases it can become challenging to specify the name of the database within PowerShell or SQL Server so you’ll want to rename the database to a more user-friendly name. You may also decide you need to move the database to a different location on your hard drives, but you don’t want to recreate the Web… Read More

Continue Reading

Configuring SQL Server Log Shipping on SharePoint Content Databases

Implementing data redundancy is one of the most effective ways to avoid data loss in any application. Although this article discusses configuring redundancy for SharePoint content stored in SQL Server by configuring SQL Server log shipping, redundancy should not be limited to only data redundancy. Any possible single point of failure, including hard drives, cables, and DNS or IIS entries should be taken into consideration to ensure you are able to quickly recover from what could be a disaster. There are several methods to choose from when determining the type of data redundancy you need to ensure business continuity. A few of these methods include; SQL Server clustering, database mirroring,… Read More

Continue Reading