aspx Tutorial

NET Articles,jQuery demo, asp.net with jQuery, online tutorial,Jquery, SilverLight, Javascript, asp.net,JSON, MVC,.NET Articles,demo, Web Services,
Advertise Here

Toolbar

Get our toolbar!

Advertize



Posted by Haseeb Kayani   on Friday, February 14, 2014 Total Views:  

Installing the Operating System and prior to SQL Installation:

  • NTFS Allocation Unit Size must be set to 64K for OS settings. Failing to do so will result in as much as a 32% performance impact for SharePoint.

When configuring SQL Server for use with SharePoint 2013:

  1. SQL Server 2012 is ideal
  2. Install an instance of SQL Server that will be dedicated to SharePoint
  3. SQL instance for SharePoint should be a non-default instance
  4. Max. Degrees of Parallelism must be set to 1
  5. For all SharePoint DB's, set the Default Collation setting to: Latin1_General_CI_AS_KS_WS. 

Recommended Database File Placement:

Database files should NEVER be stored on the system drive (C:). It is always best to put all data and log files on a separate drive. Ideally, the recommended practice is to use a separate, dedicated drive for each of the following.

  1. TempDB
  2. Database transaction log files
  3. Search data files
  4. Content database files

System Database Modifications that must be performed:

TempDB

  1. Initial size è500 MB 
  2. Set to simple recovery mode
  3. Set Auto growth to use MB, not %
  4. Auto growth value è 500 MB 
  5. Put on the fastest available non-system drive. 

ModelDB

  1. Initial size è500 MB
  2. Set to full recovery mode
  3. Set Auto growth to use MB, not %
  4. Initial size è250 MB
  5. Initial log size should be 25% of MDF, so 125 MG in this case
  6. Log growth should set to something like 70 MG

Instance Level Settings:

  1. The Maximum Memory must be set on all SQL instances 
  2. Number of data files less than or equal to number of processor cores
  3. Do not enable auto-create statistics on a server that hosts SQL Server and SharePoint Server.

Database Backups

No need to back up the search databases or the configuration database. 

A full SQL backup of the content databases <<WSS_content_DATABASE NAME >> is done once per week and then differential backups are done on the days in between. So, <<WSS_content_DATABASE NAME >> will be backed up on Friday at 6:00 PM and then Saturday to Thursday differential backups will be taken.

Recovery mode for share-point databases 

Recovery mode for <<WSS_content_DATABASE NAME>> is set to full recovery mode other than that other databases would set to simple recovery mode. 

To avoid huge transaction logs for <<WSS_content_DATABASE NAME >>, the following process should be used:

1.A content database <<WSS_content_DATABASE NAME >> is in Full Recovery mode.

2.Every time a full backup is done for << WSS_content_ DATABASE NAME >>, we would running the following SQL transaction  for <<WSS_content_ DATABASE NAME >> database 

Backup Log<<WSS_content_DATABASE NAME >> to drive:\backup path\ WSS_content_DATABASE NAME_log_CurrentDateTime.bak with INIT

This SQL transaction from step 2 will back up the transaction log and then truncate the log. After this, we will just delete the transaction log backup.

Protected by Copyscape Online Plagiarism Tool

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading

Advertizement 1
Advertizement 2
Advertizement 3
Advertizement 4
Advertizement 5