When I setup the SharePoint 2010 on Windows7 x64 system I was quite satisfied by my laptop performance but as development and customization begins, IIS, Windows Services and SharePoint instance became more resource intense. See the following task manager graph it tells the major difference.
|Stats before SharePoint 2010.||Stats after SharePoint 2010 installation.|
Though I use to work in SharePoint occasionally so I don’t need the instance running 24/7 on my development machine. While looking in to the core I figure out that we need couple of SharePoint\SQL(SharePoint Services [SPTimerV4,DCLoadBalancer14,DCLauncher14,SPWriterV4,SPUserCodeV4,SPTraceV4,SPAdminV4,WebAnalyticsService] and SQL Server services [MSSQLSHAREPOINT,SQLWriter,SQLSERVERAGENT]) services to keep the SharePoint instance live and off course an IIS instance as well; but it seems quite hectic to start\stop such services\software’s on demand as allot of clicks and software switching was required; other big disadvantage was that you have to keep a particular order to start such services else some of the services wont either start or they will eventually fill your event log.We learned that Microsoft did introduce PowerShell to automate such hectic routines, while reading the MSDN and some technical blogs I came to a really good script written by Emmanuel Bergerat which I really love to share as it saved allot of typos for me. To automate the process follow the steps below:
Important: Modify services startup type
You need to modify the startup type of some services; this will not allow the SharePoint instance to start automatically.This step is required once you setup your workstation.
Manual way: Navigate to Control Panel –> Administrative Tools –> Services, locate the following services and change their startup type from automatic to manual save the service setting and close the dialog accordingly.