Disable Quick Edit in SharePoint 2013 Lists

In SharePoint 2013, there is a new feature in lists which is Quick Edit.

When you click on “edit” the below screen appear:

To disable this feature:

Go to “List Settings

Click on “Advanced settings

Click “OK

Result is :


Approve Multiple Items in SharePoint 2013

If you need to approve multiple items in SharePoint 2013, follow the below steps:

Go to Site Settings

Under “Site Administration” click on “Content and structure logs”

When the page open, click on your document library on left pane

On right pane, click on “All Documents” and choose “Pending Approval” to change the view.

Deploying SharePoint 2010 Solution on SharePoint 2013

As you know, in SharePoint 2010 there was 14 hive where you deploy your files. And then you reference them like below:


Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS

Virtual Path: “/_layouts/<your folder>/<your files>”


In SharePoint 2013, there is new 15 hive

Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS

Virtual Path: “/_layouts/15/<your folder>/<your files>”


If you have SharePoint 2010 solution (.wsp file) and you need to deploy it on SharePoint 2013, then you have the following options:

First, you have to add the solution to your farm using PowerShell as following:

  • Add-SPSolution C:\SP2010Project.wsp


  • Deploy to 14 hive è
    Install-SPSolution sp2010project.wsp
  • Deploy to 15 hive è Install-SPSolution sp2010project.wsp -CompatibilityLevel 15

Virtualizing SQL Server in SharePoint 2010 Farm is not Recommended

The database server is responsible for storing, maintaining, and fetching data for other server components and services.

Virtualization of the database server is not recommended. Reasons to avoid virtualizing the database server are as follows:

  • Virtualization introduces latency downstream in the application and UI server components of a SharePoint farm. If every data request takes more time, the scenario quickly becomes a challenge, especially when a single transaction needs multiple round trips for completion.
  • The database server experiences heavy CPU, memory, disk I/O, and NIC usage.
  • If overall performance evaluation or virtual machines are not adequately specified, end users may experience slower response times and, in background processes, slower performance of long-running operations, which can increase operation timeouts.

for more details, visit this link  [Page 24]  http://www.microsoft.com/en-us/download/details.aspx?id=19508