SharePoint Content Database Tables

Here are some importent tables of SharePoint Content Database

• 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.

Configuring Usage Analysis Processing using stsadm

I ran into a problem recently when attempting to enable and configure Usage Analysis Processing (UAP)using stsadm, I needed to do this as part of a fully scripted installation of MOSS 2007 that I was assisting a customer with. Looking at the stsadm documentation, the following commands are available:

stsadm -o setproperty
-propertyname usageprocessingenabled
-propertyvalue {Yes | No}
stsadm -o setproperty
-propertyname job-usage-analysis
-propertyvalue {Yes | No}

I then ran the following two commands to configure UAP:
stsadm -o setproperty -pn job-usage-analysis -pv "daily between 08:00 and 09:00" To configure the time that the process runs.
stsadm -o setproperty -pn usageprocessingenabled -pv "Yes” To enable Usage Analysis Processing.
However when I browsed to Central Administration – Operations – Usage analysis processing the following was displayed



If you look closely you can see that the time has been set correctly but it hasn’t enabled usage analysis processing. As you can see this is grayed out meaning that Enable logging must be selected before it can be enabled – but how do I enable logging? After much investigation I eventually found out (from a colleague- thanks Kirk) that the following stsadm can be used to enable this.
stsadm -o setproperty -pn loggingenabled -pv "Yes”To put this all together I need to run the commands in this order to achieve my objective:

• stsadm -o setproperty -pn loggingenabled -pv "Yes”
• stsadm -o setproperty -pn job-usage-analysis -pv "daily between 08:00 and 09:00"
• stsadm –o setproperty -pn usageprocessingenabled -pv "Yes”

Enterprise Content Management (ECM)

Hi All These are some good blogs and links for Enterprise Content Management

Blogs
==============
blogs.msdn.com/ecm/
blogs.msdn.com/ecm/archive/2006/06/09/624520.aspx
blogs.msdn.com/sharepoint/archive/2008/01/03/new-beta-extranet-collaboration-toolkit.aspx
blogs.msdn.com/.../30/announcing-the-first-release-of-the-microsoft-sharepoint-administration-toolkit.aspx

Sites
==============
office.microsoft.com/en-us/sharepointserver/HA101747881033.aspx
office.microsoft.com/en-us/sharepointserver/HA102063591033.aspx
msdn.microsoft.com/en-us/library/aa830818.aspx

YouTube
==============
www.youtube.com/watch?v=8zT4NsSSa6g

Other resources
===============
www.andrewconnell.com/blog/articles/MossWcmResources.aspx
www.microsoft.com/downloads/details.aspx?FamilyID=6D94E307-67D9-41AC-B2D6-0074D6286FA9
www.1stafftraining.com/b2b/outlines/1Staff_50003.pdf

PRESCAN KB Articles

If you you are not able to run Prescan or receive errors in Prescan logs please follow these KB Articles. They will help you to resolve issue

Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services 2.0 and SharePoint Portal Server 2003
http://support.microsoft.com/kb/918744

You receive an error message when you run the pre-upgrade scan tool (Prescan.exe) to scan Windows SharePoint Services 2.0 sites before you upgrade to Windows SharePoint Services 3.0
http://support.microsoft.com/kb/937291/en-us

Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services 2.0 and SharePoint Portal Server 2003
http://support.microsoft.com/kb/918744/en-us

Error message when you try to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0: "Upgrade has encountered one or more lists that were not updated by Prescan.exe and must exit"
http://support.microsoft.com/kb/923904/en-us

Problem: migrate frontend of wss2 to moss2007
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2605512&SiteID=1

Connecting SQL SSEE to SQL Management Studio

If you are using SQL 2005 SSEE & wants to edit permission or take SQL backup

Actual place where the database is Stored.
C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data

You can See the databases in SQL by Downloading Microsoft SQL Server Management Studio Express from the below link

https://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en

After you install this application Copy & paste

\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

On the Authentication Window Under server name. & you will be able to See all the databases

Install Application Template(.WSP) in WSS 3.0 & MOSS 2007

Before install any application template, First you install Application Template Core

Windows SharePoint Services 3.0 Application Template: Application Template Core
Download URL: http://www.microsoft.com/downloads/details.aspx?familyid=C1039E13-94DA-4D7D-8CAE-3B96FA5A4045&displaylang=en

To Download All Templates
URL: http://www.microsoft.com/downloads/details.aspx?familyid=5807B5EF-57A1-47CB-8666-78C1363F127D&displaylang=en

Pull the core file, ApplicationTemplateCore.wsp, from the extracted distribution in C:\PROGRAM FILES \common files\microsoft shared\web server extensions\12\bin

Installing the core:
Go to C:\PROGRAM FILES\common files\microsoft shared\web server extensions\12\bin and run these 3 commands


1) stsadm -o addsolution -filename ApplicationTemplateCore.wsp
2) stsadm -o deploysolution -name ApplicationTemplateCore.wsp -allowgacdeployment
3) stsadm -o copyappbincontent

Removing the core:

1) stsadm -o retractsolution -name ApplicationTemplateCore.wsp
2) stsadm -o deletesolution -name ApplicationTemplateCore.wsp


To Install All WSP Files in one single Script, please create a .bat file (Install.bat) and paste these codes in that

for %%f in (*.wsp) do stsadm.exe -o addsolution -filename %%f
for %%f in (*.wsp) do stsadm.exe -o deploysolution -allowgacdeployment -immediate -name %%f
stsadm -o copyappbincontent

Save the batch file in C:\PROGRAM FILES\common files\microsoft shared\web server extensions\12\ and copy all .WSP file on the same location.

Then Run the Install.Bat file and enjoy :)

PSConfig.exe (Command Line operations) for Configuration

PSConfig.exe (Command Line operations) for Configuration

The PSConfig.exe command line tool is used to configure the product after setup has completed. The default location of the tool: c:\program files\common files\microsoft shared\web server extensions\12\bin.
To create a new server farm or connect to an existing server farm the following steps will need to be run in the following order:

1. Create the ConfigDB:
PSConfig.exe -cmd configdb -create -server -database
-dbuser -dbpassword
-user -password
-addomain -adorgunit
-admincontentdatabase

Note that if you wish to connect to an existing configuration database and join the server to an existing server farm you will need to perform the ConfigDB command with the -connect parameter

2. Install all HelpCollections
psconfig.exe -cmd helpcollections installall

3. Perform resource security enforcement
psconfig.exe -cmd secureresources

4. Register the services in the server farm
psconfig.exe -cmd services -install

Note that before you can provision we will need to start and configure the Search service via the STSADM.exe command (more information about STSADM.exe later on):

Start the Windows SharePoint Services Search:
stsadm -o spsearch -action start -farmserviceaccount Redmond\user -farmservicepassword MyPassword

Start the Office SharePoint Server Search service:
stsadm -o osearch -action start -role IndexQuery -farmserviceaccount Redmond\user -farmservicepassword MyPassword -farmcontactemail user@ms.com

psconfig.exe -cmd services –provision

5. Register all features
psconfig.exe -cmd installfeatures

6. Provision the SharePoint Central Administration Web application
psconfig.exe -cmd adminvs -provision -port -windowsauthprovider onlyusentlm

7. Install shared application data
psconfig.exe -cmd applicationcontent –install