Blogroll

Friday, July 25, 2008

Exploring The SharePoint Content Database

There are some cases when we need to look into and read from the content databases.We will begin with some of the basic tables and a very high level diagram on some of the relationships between them.

Features
Table that holds information about all the activated features for each site collection or site.


Sites
Table that holds information about all the site collections for this content database.


Webs
Table that holds information about all the specific sites (webs) in each site collection.


UserInfo
Table that holds information about all the users for each site collection.


Groups
Table that holds information about all the SharePoint groups in each site collection.


Roles
Table that holds information about all the SharePoint roles (permission levels) for each site.


AllLists
Table that holds information about lists for each site.


GroupMembership
Table that holds information about all the SharePoint group members.


AllUserData
Table that holds information about all the list items for each list.


AllDocs
Table that holds information about all the documents (and all list items) for each document library and list.


RoleAssignment
Table that holds information about all the users or SharePoint groups that are assigned to roles.


SchedSubscriptions
Table that holds information about all the scheduled subscriptions (alerts) for each user.


ImmedSubscriptions
Table that holds information about all the immediate subscriptions (alerts) for each user.


Source : www.sharepointblogs.com

Sharepoint Backup

Types of Backup in Sharepoint V3.
As Every product or any business Disaster Recovery is very importand and in similar way, Sharepoint has some very good options for the same. Below are the methods that can be used in WSS 3.0 only or also for MOSS 2007.
1. GUI mode from Sharepoint Central Administration.
This Method is very common and most of the Administrators use this Method.
Go to Sharepoint Central Administration page -> Operations Tab -> Backup Operations.
This method will need a UNC path to store the back. It automatically creates a folder starting which will have various files in it and the most important file is the .xml file which get created, which has all the information about the backup.
The .xml file will contain data about the backup ID, The type of Backup, the Components selected during the backup.
GUI Backup is the same like the stsadm -o backup [catostrophic]. Both work the same way and the backrgound process is the same. Only difference here is the GUI interface.
By Default this backup will take the entire Sharepoint Farm backup
2. STSADM -o backup
This method is a command line backup which needs to be run from the BIN folder of Sharepoint.
This method can backup any top level sites or site collections of a Web application.
You will need to specify the URL address of the site to be backed up.By default in this method the security or permissions are also backed up.
stsadm -o backup -filename c:\back.bak -url http://siteurl/
This is the standard command. It is not necessary to give the backup file extension as .bak, it can be anything or you may not even give any extension. Using this command you can backup only 1 top site at a time within the Web Application. If you want you can create a batch file which will include the commands having different URL's and schedule te batch file to run accordingly. It also includes other parameters for which you can use
stsadm -help backup
3. STSADM -o backup [catostrophic]
This method is similar to GUI Central Adminstration backup, its only Command line interface. You will need to manually specify the parameters and components to be backed up using this command. By default if the component is not specified, Enter Farm level backup is taken. Using this command as well a UNC path is to be given, where again and .xml file will be created.
stsadm -o backup -directory \\server\backup -backupmethod full [This will take the default Farm level backup]

You can use stsadm -o backup -showtree to see the list of the items in the Farm and then use stsadm -o backup -directory \\server\backup -backupmethod full -item
4. STSADM -o export
This method will help you to take backups of subsites separately which is not possible in any of the above backups. Using this method, subsites and top level sites backup can be taken but by default User permissions are not exported, you have to manually specific to export User permissions.
stsadm -o export -filename c:\exp.back -url http://siteURL -includeusersecurity
If you do not use -includeusersecurity, User permissions will not be exported by default.
5. SQL Database backup.
This method is the usuall maintenance method from SQL Management Studio. It is recommended to have the Sharepoint Content Databases backup from SQL as well, just in case Sharepoint Backup's don't work.

Microsoft Search Server 2008

Search Server is one of the other major Enterprise servers of Microsoft which is growing Fast with Sharepoint 2007. With the new release of Search Server 2008 in March, it is expected to take Search functionality and Search Experience to the next level for Microsoft's Customer's.

There are better features than Google's Onebox Search Server Appliance, though I would say both have their own pro's and con's.

Search Server 2008
It's RTM version's are getting released in Express and Full Edition. Express Edition will be downloadable for free whereas Full version is a licensed product. There will be support provided for both these versions from Microsoft.

Express Edition's limitation is that it can be installed only on a SingleServer WSS 3.0 environment, whereas, Full Edition can be installed in a Farm WSS 3.0 enviroment.

Search Server 2008 MOSS patch is expected to be released later this year. When you install Search Server 2008, WSS 3.0 will be installed along with it, with some more cool features of Search which is not available with only WSS 3.0 Another new and cool feature of Search Server is the Federated Search which allows you to render the index of the Search engines on the internet, except for Google Search, Google blocks any search engine to crawl its content.

Search Server needs to get the results returned in XML formart to display those results in the Search query, for any Search engine that cannot return the results in XML format to Search Server, we have Federated Search custom connectors that can be created to re-format the results in XML format and store it locally. Those custom connectors is something that Shareopoint Developers will have to do. There are many 3rd party custom search connectors already available and can be used with Search Server 2008.

Google's Enterprise Search products have limitations of crawling data, depending on the product you buy, the limitations differ. In Microsoft Search Server 2008 there is no limitation to the no of files that be crawled. Also, Google's product expire in 2 years and so will their email support, they do not have any on call support. If you want to renew the support you will have to buy a new license for that to get support. (Email)

More information on the Installation and new features of Search Server 2008 will be posted soon.

Error while creating a new page in MOSS.

Getting the below error while creating a new page in Moss 2007 while using publishing or collaboration portal template.

List does not exist The page you selected contains a list that does not exist.
It may have been deleted by another user.


In ULS Logs the error listed is as below.

05/16/2008 13:13:34.51 w3wp.exe (0x1AF8) 0x148C Windows SharePoint Services General 8kh7 High List does not exist The page you selected contains a list that does not exist. It may have been deleted by another user. 05/16/2008 13:13:34.51 w3wp.exe (0x1AF8) 0x148C Windows SharePoint Services General 8nca Verbose Application error when access /_layouts/AccessDenied.aspx, Error=List does not exist The page you selected contains a list that does not exist. It may have been deleted by another user. at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount) at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt... 05/16/2008 13:13:34.51* w3wp.exe (0x1AF8) 0x148C Windows SharePoint Services General 8nca Verbose ...32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount) 05/16/2008 13:13:34.51 w3wp.exe (0x1AF8) 0x148C Windows SharePoint Services General 0 Verbose Releasing SPRequest with allocation Id {BD5F0900-38A4-40AB-BC1F-E78319A3DD70}

Resolution
=========

Go to Site Settings -> Master page Gallery -> Add Authenticated Users group and give Read Restricted Access rights.

Add the same group in Style Library and give the same permissions.


ShareThis

snow flakes

blogger widgets Blogspot Tutorial

LinkWithin

Related Posts Plugin for WordPress, Blogger...