Move a SharePoint Content Database / Deploy sharepoint site

  • 6

Move a SharePoint Content Database / Deploy sharepoint site

our Official website (

You have two initial options, doing a backup and restore within MOSS to move the data, or doing it at the SQL/STSADM level.  I prefer the latter, as it isn’t nearly as inclined to fail and leaves you with more flexibility.

1) Find the content Database

These are listed under Central Admin->Application Management->Site Collection List

2) Backup the content database

You could alternatively detach it, and copy it.  Just doing a backup in SQL Server 2005 Management studio is easier.

3) Restore content database to new server

Copy the BAK file to new server.  Create an empty DB in Management Studio, restore from backup, you may need to change an option in the “options” tab of the restore dialog to get it to work.  (Overwrite db).

4) Create Web App on new Server

Central Admin->Application Management->Create or extend Web App->Create New Web App.

5) Associate restored DB with new Web App

Central Admin->Application Management->

SharePoint Web Application Management->Content Databases->

Remove Content Database from your new web app.

Now use STSADM to add restored DB to this web app

c:program filescommon filesmicrosoft sharedweb server extentions12bin on new server is where you can find the STSADM.

run this command from there.

stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver

6) Run ISSRESET from command prompt.

Bookmark and Share

  • 0

Turning off friendly errors in MOSS

Click Here to visit Zonix’s Website

We found many times sharepoint only display some text like unknown/unspecified error occured. If you want to sharepoint display you to proper error follow below given article.

While in development, the friendly error page that SharePoint displays when our page has an error can make debugging master page issues very difficult.
We can make an easy change to the Web config file for the site to turn friendly error messages off, therefore providing us with more useful information if page breaks. Only do the following in a development environment, and we should never want to turn off friendly error messages in a production environment. Also be sure to make a back up of the file prior to editing.
1. On the Web server, navigate to the site directory:Local Drive:InetpubwwwrootwssVirtualDirectories[directory for site]
2. Open Web.config in Notepad.
3. Search for “CallStack”. Change the CallStack status to “true”.
4. Search for “CustomErrors”. Change the mode to “off”.
5. Save and close the file.
Now when the site encounters an error, you will receive a .NET screen outlining the issue instead of the friendly SharePoint error screen. This is particularly useful with dealing with missing Content Placeholders and editing Master Pages. To turn friendly error messages back on, just walk through these steps setting the CallStack to false and CustomErrors mode to On.

Bookmark and Share

Bookmark and Share

  • 15

Advantages of and Sharepoint – Where to use SharePoint

Click Here to visit Zonix’s Website

Here are some of Advantages/Disadvantages of SharePoint apps over ASP.Net apps:




1. Many built-in features are available with MOSS which can be used to easily develop complex solutions.

2. Rich Security features which come built in.

3. Integrated with Content Management.

4. Very less efforts required to create basic sites with lot of features.

5. It is quite scalable.

6. OOB Integration with Office products.

7. Rich backup techniques

8. Business process can be integrated with Workflows.

9. Multiple sites can be created with the help of templates.



1. It is difficult to add custom code in SharePoint. Features and WSP files take time.

2. Difficult to solve the problems in development.

3. Creating pages is easy then creating web parts.

4. Cost is very high.

5. Performance for ASP.NET apps is much better.

6. Very few experts are there.


Advantages/Disadvantages of ASP.Net apps over SharePoint apps:




1. Here we have lot of control on application in terms of DB, UI.

2. Less cost to build.

3. Easy to develop and deploy.

4. Plenty of resources.



1. Takes lot more time to get same functionality as of SharePoint.

2. There is nothing built in. So every solution needs to start from zero.

3. Good DB knowledge is also required to create sites having data.

4. Security needs to build.

  • 0

What’s SharePoint Not Good For

Click Here to visit Zonix’s Website

SharePoint is an excellent way to create data-driven web sites, in my opinion, but there are other times where I don’t think it’s the best choice. For example, SharePoint isn’t a substitute for a code management library, such as SourceSafe. (Microsoft is working on this for Visual Studio 2008, however, so watch out!) Also, SharePoint’s integration with Microsoft Office, Windows, and .NET means that users of other operating platforms (Mac, Linux) or non-Microsoft browsers may have problems using the sites.

In particular, SharePoint authentication does not seem to work with Internet Explorer for the Macintosh or Mozilla prior to Version 1.7.2. In addition, SharePoint pages look different in FireFox, Mozilla, and Netscape Navigator than they look in Internet Explorer. You can compare these differences by using different browsers to view public SharePoint sites.

  • 0

Introduction to SharePoint

Click Here to visit Zonix’s Website

  1. Why Use SharePoint?

a.  SharePoint is a component of Windows 2003 that lets you share Microsoft Office documents with others through web pages. Unlike most web sites, SharePoint sites are designed to be highly dynamic. Team members can easily upload documents, add public announcements, send alerts, track work items, and call meetings right from within Office products. 

2.      What is difference between SharePoint Service and SharePoint Server?

    1. A Sharepoint service is freely downloadable.
    2. The Windows SharePoint Services are primarily focused around workgroup level collaboration . The main purpose for SharePoint Portal Server is to act as an enterprise level portal.
    3. SharePoint Portal Server was built on top of the Windows SharePoint Services. This means that anything that the Windows SharePoint Services can do, SharePoint Portal Server can also do. Windows SharePoint Service’s primary focus is to create workspaces that small groups of users can use to collaborate on projects by sharing a small collection of documents and other data. Where for SharePoint Portal Server is to act as an enterprise level portal. SharePoint server has some advance feature like searching like we can search for specific keyword. The results of the search can then be arranged by document author, site, date, and category. SharePoint Portal Server also offers hierarchical search scopes that allow users to perform searches from within specific topics, categories, or content sources.
  2. What is the  OS requirement for Windows SharePoint Service?
    1. Windows server 2003.
  3. What Software Requirements at client side for use sharepoint  services features?
    1. Microsoft Internet Explorer 5.01 with SP2 or later (best results with Microsoft Internet Explorer 5.5 with SP2 or later), Microsoft Internet Explorer 5.2 or later for Macintosh, Netscape Navigator version 6.2 or later, Mozilla 1.4 or later, or Firefox 1.0.4 or later 
  4. What types of configuration available for Sharepoint Services?
    1. There are two types of configuration available for sharepoint services and farm server.

                   i.      stand-alone server: if our requirement is hosting  very few sites  and for small organization

                  ii.      server farm:If we are supporting Web sites in a large organization or as an Internetserviceprovider (ISP), and anticipate heavy usage and a lot of data, we will most likely want to use the server farm configuration.

Bookmark and Share