Add existing Content database to a Site collection using STSADM

August 25, 2009

Stsadm Addcontentdb

– You have an old content database (mdf/ldf or a backup) that you want to use as a content database for a new site collection.
– You want to create a new site collection, and to use an already existing content database (that holds your old data) for this site collection.

– At the back-end SQL server you have a content database (in this example i will name it WSS_Content_Web1) attached to the SQL server, that is not linked to any site collection yet.
-At the back-end SQL server you’ve created a new database (in this example i will name it WSS_Content_Web1) using SQL management studio and restored a backed-up content database to it, to be used as a content database for you new site collection.

I will refer to this content database as WSS_Content_Web1, and the site collection as


What we are up to do is:

  1. Create a content database using Sharepoint central administration.
  2. Create site collection that will use this content db.
  3. delete this content db.
  4. use STSADM to link this newly created site collection to the existing content database (in this example i will name it WSS_Content_Web1) in the back-end SQL.


So let us start:

  1. Launch “SharePoint 3.0 Centeral Administration”, and under the category “SharePoint Web Application Management” Select “Web application list” then select the web application that will contain the site collection.
  2. Select content databases, and click to add a new content database, name it WSS_Content_test and click ok.
  3. Create a new site collection, name it Web1. (notice that the new site collection will be attached to the newly created content database (WSS_content_test).
  4. Go back to the link “content databases” and delete the content database you’ve created “WSS_Content_test”.
  5. Launch Command prompt (CMD) … Start > Run > cmd and hit enter.
  6. write the following command line:
    Stsadm –o addcontentdb –url –databasename WSS_Content_Web1
  7. press enter to execute the command.

Go and browse to your newly created site collection, and enjoy.



  1. The STSADM tool is usually located in the following path (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN).
  2. For details about using the command addcontentdb visit this article in TechNet Addcontentdb: Stsadm operation (Office SharePoint Server).

SharePoint 2010 … Get a Sneak Peek now!

August 8, 2009


On their home page, Microsoft SharePoint Server 2007 is to announce the release of their new SharePoint 2010 Server.

Keep your eye on it, Microsoft SharePoint Server 2007 Website, and here you can take the sneak peek (Click Here)

Yet another way of writing code in SharePoint2007

August 7, 2009

Hi all;

Remember my post “Publish Your .ASPX Page With Code Behind To SharePoint 2007“, here is a simpler way of creating no code behind aspx page in SharePoint2007.

Here we will go through 3 steps:

  1. Build a simple aspx page in Visual Studio 2005 (with no separate code file).
  2. Tweak the SharePoint Web application Web.config file to accept running codes.
  3. Copy the aspx code to a new aspx page in SharePoint.

So lets start:

Building the aspx page

  1. open up Visual Studio 2005 or 2008, and make a new web site name it whatever.
  2. add another aspx page to the web site, but here uncheck the checkbox titled “Place code in separate file“.
  3. open this aspx page, and switch to design view.
  4. drop a TextBox, name it txtHello, and drop a Button name it btnHello.
  5. double click the btnHello command button.
  6. in the btnHello_Click protected sub, write this simple line code
  7. txtHello.text = “Hello World”. run your web site to test if every thing works fine.


Modify the web.config file of the SharePoint Web application:

  1. Open your Web application web.config file (which is found in this path –> C:\inetpub\wwwroot\wss\VirtualDirectories\xxxx   , the xxxx is the port number of your web application but in most cases for the default website its 80).
  2. add the following lines to the web.config file, directly inside the <configuration<SharePoint> directive and save.

<SafeMode MaxControls=500 CallStack=false DirectFileDependencies=10 TotalFileDependencies=50 AllowPageLevelTrace=false>


<PageParserPath VirtualPath=/* CompilationMode=Always AllowServerSideScript=true IncludeSubFolders=true ></PageParserPath>



here we are telling SharePoint to accept running codes from the root path including all sub folders by using “/*” , but i prefer that you create a folder in your site collection, naming it “Applications”, and put all aspx pages that contains code in it, then change the path in the VirtualPath=/*  to be VirtualPath=/Applications/* .


Finally, copy the code in this aspx page to a new aspx page in SharePoint using SharePoint Designer:

  1. Open SharePoint Designer 2007, create a new aspx page, back to your web site which you created in, open the aspx page that you’ve created and tested, switch to code view, select all (Ctrl+A) and Copy (ctrl+C) code, paste the code in the SharePoint aspx page.
  2. Save & Check-In the SharePoint aspx page, run and have fun.

SharePoint Server 2007 SP2 … Slipstream!

August 7, 2009

In the scenario of installing a fresh new SharePoint2007, its a good idea to install it once with all the updates & service packs available.

Here i will go through bundle every thing in one MOSS2007 installation folder, including MOSS2007 Setup, WSS v3 SP2, microsoft office sharepoint server2007 SP2 and the cumulative update (15 july 2009) for both WSS v3 and MOSS2007.

To get started, we will need the SharePoint 2007 installation media, the SP2 for both WSS and MOSS, and the latest Cumulative Updates for both WSS and MOSS. so here are the links for downloading SP2 & the latest CUs:

To begin make a folder named c:\MOSS2007, and copy the MOSS2007 installation files and folders into it. (the folder will look similar to the following pic)


Notice that theres a folder called Updates , here we will extract the SP2s and CUs files. as follows:

  1. open up command propmt . start > run > cmd.
  2. extract the four files (SPs & UCs) by writing EXTRACT command as follows depending on the path of each one (i prefer to put them all in one folder in the C:\ root to narrow the extraction command statement):

– c:\wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:c:\MOSS2007\updates

c:\officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract:c:\MOSS2007\updates

 – c:\wss-kb968850-fullfile-x64-glb.exe /extract:c:\MOSS2007\updates

c:\office-kb968851-fullfile-x64-glb.exe /extract:c:\MOSS2007\updates

And after completing the extraction proccess for all files, you shall notice that the Updates folder will be filled with many msp files, also you will notice that there are two DLL files named svrsetup.dll and wsssetup.dll, you must delete the file wsssetup.dll because its causing a Setup Error (Language not supported by your system), and conflecting with the other file svrsetup.dll.

Now you are ready to install a complete fully updated MOSS2007.

Recommended installation sequence for updates

Also if you are making a separate Updates installation, like say you have MOSS already installed, and want to update to Service Packs 2 and cumulative updates, then Microsoft enforces the installation order of service packs, but does not enforce the installation order of packages or patches. You can install packages or patches in any order you want, so long as every server in your farm is updated to the same level when you are done. In addition, there is no requirement to install an update unless your servers are affected by the problem described in the KB article for the update.

Although Microsoft does not enforce the update installation sequence, we recommend that you install the post-RTM updates for Office SharePoint Server that you require in the following sequence:

  1. Service Pack 2 for Windows SharePoint Services 3.0 (KB 953338)
  2. Service Pack 2 for Office SharePoint Server 2007 (KB 953334)
  3. The June CU for Windows SharePoint Services 3.0 (KB 971538)
  4. The June CU for Office SharePoint Server 2007 (KB 971537)
Important Important:
Remember to run either the SharePoint Configuration Wizard or Psconfig.exe at the command prompt on every server in your farm to complete the update. You are not required to run the SharePoint Configuration Wizard or Psconfig between each step in the sequence. You can to wait until all updates are installed on a given server before you run the SharePoint Configuration Wizard or PSconfig.

10 new SharePoint Themes!

August 7, 2009

Microsoft has released 10 new themes for Sharepoint to make Sharepoint not look like Sharepoint!

You can download the package from here :


And the good thing here is that they are packaged as a solution.

And here are the instructions

Download the installer Run the installer and accept the End User License Agreement Once installed locate the Ten Themes for SharePoint in the start menu You can view all the themes at once by choosing the AllThemesPreview.jpg Locate in the start menu Uncompress the ZIP file to obtain the ten theme projects Load one a selected project in Visual Studio 2008 Use VSeWSS to deploy the project to view the final theme

For those who need to download the new sharepoint themes as a single WSP visit this link:

10 SharePoint Theme WSP

How to shrink Huge SharePoint Content Database Log file?

August 1, 2009

After facing the problem of not being able to perform any action, like deleting, adding new list items, and after viewing WFE server application event viewer, i’ve figured out that my Back-end SQL server is out of space (the drive that holds the content databases and DB log files).

So after surfing microsoft’s website, i’ve found the best way to shrink the log file which was about 60 GB to be any size that i want (say 10 MB).

  1. open up SQL management studio.
  2. open a new query window.
  3. paste the following command lines:

USE WSS_Content_Web;
-- Truncate the log by changing the database recovery model to SIMPLE.
-- Shrink the truncated log file to 10 MB.
DBCC SHRINKFILE (WSS_Content_Web_log, 10);
-- Reset the database recovery model.

 Execute (F5).