which country user step here?

Tag Cloud

MOSS (47) SharePoint 2007 (37) SharePoint 2013 (23) SharePoint 2010 (22) MOSS admin (17) admin (17) PowerShell (16) developer (16) List (15) WSS (14) sql query (14) MOSS SP2 (13) end user (11) scripting (11) wss V3 (11) Moss issue (8) search (8) permission (7) sql (7) Service Pack (6) database (6) reportadmin (6) workflow (6) Excel (5) client object model (5) CU (4) Client Code (4) Command (4) Cumulative Updates (4) Patch (4) SharePoint designer (4) stsadm (4) ASP.NET (3) Content Database (3) Groove (3) Host Named Site Collections (HNSC) (3) IIS (3) RBS (3) Tutorial (3) alert (3) batch file (3) codeplex (3) error (3) incomming email (3) restore (3) upload (3) Caching (2) Folder (2) Index (2) Internet (2) News (2) People Picker (2) Share Document (2) View (2) Web Development with ASP.NET (2) add user (2) authentication (2) coding (2) column (2) deploy solution (2) domain (2) download (2) enumsites (2) exam (2) export (2) issue (2) june CU (2) mySites (2) network (2) office 365 (2) orphan site (2) performance (2) profile (2) project server (2) query (2) server admin (2) theme (2) timer job (2) training (2) user porfile (2) web master (2) web.config (2) wsp (2) 70-346 (1) 70-630 (1) AAM (1) Anonymous (1) Approval (1) Cerificate (1) Consultants (1) Content Deployment (1) Content Type (1) DOS (1) Document Library (1) Drive Sapce (1) Excel Services (1) Export to Excel (1) Feature (1) GAC (1) Get-SPContentDatabase (1) Get-WmiObject (1) HTML calculated column (1) ISA2006 (1) IT Knowledge (1) ITIL (1) Install (1) Link (1) MCTS (1) Macro (1) Migration (1) My Site Cleanup Job (1) My Sites (1) NLBS (1) Nintex (1) Office (1) Open with Explorer (1) ROIScan.vbs (1) Reporting Services (1) SPDisposeCheck.exe (1) SQL Instance name (1) SSRS (1) SharePoint farm (1) Shared Services Administration (1) Site Collection Owner (1) Site template (1) Steelhead (1) URLSCAN (1) VLOOKUP (1) WSS SP2 (1) XCOPY (1) admi (1) app (1) application pool (1) aspx (1) audit (1) availabilty (1) backup (1) binding (1) blob (1) branding sharepoint (1) cache (1) calendar (1) connection (1) copy file (1) counter (1) crawl (1) custom list (1) event (1) excel 2013 (1) facebook (1) filter (1) fun (1) group (1) iis log (1) import (1) import list (1) improment (1) interview (1) keberos (1) load balance (1) log in (1) metada (1) migrate (1) mossrap (1) onedrive for business (1) operation (1) process (1) publishing feature (1) resource (1) security (1) send email (1) size (1) sps2003 (1) sql201 (1) sql2012 (1) sub sites (1) system (1) table (1) task list (1) today date (1) vbs (1) video (1) web part (1) widget (1) windows 2008 (1) windows 2012 R2 (1) windows Azura (1) windows account (1) windows2012 (1) wmi (1)

Thursday, August 27, 2009

Use program to create attach\detach script file

If you are working on MOSS Large farm then i think you will need to create some script to detach\attach your content DB.

As i have share before the step by step to deploy MOSS SP2 blog have share about the great coding to help us to generate the share file. After try on this , i feel great!! is really very simple and usefull code for us to generate the batch file for script. Thanks to CJG.

The reasons i like to use to detach and attach the DB becuase :
  1. Is a very faster way to get the latest update information at our farm
  2. Auto generate the latest script ( no need manually create the script one by one)
  3. with the simple coding we can edit it accordingly to our need

You can also create a command line utility to do this:
  • Open Visual Studio
  • Click “File->New Project”
  • Select “Console Application”
  • For name, type “ContentDetachAttachScript”
  • Copy the following into the program.cs file:


using System;
using System.IO;
using System.Collections.Generic;
using System.Text;

using Microsoft.SharePoint;
using Microsoft.SharePoint.Administration;

namespace ConsoleApplication1
{
class Program
{
static void Main(string[] args)
{
TextWriter tw = File.CreateText("C:/detachall.bat");
TextWriter tw2 = File.CreateText("C:/attachall.bat");

SPFarm farm = SPFarm.Local;
SPAlternateUrlCollectionManager mgr = farm.AlternateUrlCollections;

foreach (SPAlternateUrlCollection altColl in mgr )
{
foreach (SPAlternateUrl url in altColl)
{
if (url.UrlZone == SPUrlZone.Default)
{
try
{
SPSite site = new SPSite(url.IncomingUrl);

SPWeb root = site.RootWeb;
if (root.WebTemplate != "CENTRALADMIN")
{
//get the web application for the site collection
SPWebApplication webApp = site.WebApplication;

foreach (SPContentDatabase cd in webApp.ContentDatabases)
{
tw.WriteLine("stsadm -o deletecontentdb -url " + url.IncomingUrl + " -databasename " + cd.Name + " -databaseserver " + cd.Server);

tw2.WriteLine("stsadm -o addcontentdb -url " + url.IncomingUrl + " -databasename " + cd.Name + " -databaseserver " + cd.Server);

//Console.WriteLine("Content Database [" + cd.Name + "] was detached");

//cd.Delete();

}
}
}
catch (Exception ex)
{
Console.WriteLine(ex.Message);
}
}
}
}

tw.Close();
tw2.Close();

Console.WriteLine("Press enter to close");
Console.ReadLine();

}
}
}

    • Compile the program, press F6
    • Copy the executable to your SharePoint Farm
    • Run the executable
    • Open the C:\detachall.bat file , this file will contain all the stsadm commands that will detach all your content databases
    • Open the C:\attachall.bat file, this contains all the stsadm commands to reattach your databases (NOTE: you should attach one at a time in the later steps).

No comments: