Dynamic Charts in Sharepoint using JQUery

http://www.endusersharepoint.com/2009/04/20/finally-dynamic-charting-in-wss-no-code-required/

How to hide left side quick naviagation

&lt style &rt
.ms-navframe {
display:none;
} &lt /style &rt


Place this code in Content Editor Webpart of the same page

How to hide left side quick naviagation

This Month/ Today's Birth Days Using [Today] in a Calculated Formula (Birthday Lists)

Using [Today] in a Calculated Formula (Birthday Lists)

It is possible to use "Today" in a function as a reference to today's date

(despite what SharePoint tells you).  There is a very simple work around that

doesn't involve very much effort or complexity.

1. First, create a new column in your list with the column name of "Today".  
   Click "OK".  (It doesn't matter what type of column or data it is, this is
   just a place holder and will be removed later). MK Note: Create column called Today… I also created a column called DOB (date field) where I will enter the birth date.
2. Next, create a column with the data where you would like to use "Today" as a
   reference to today's date.  The column type should be "Calculated".  In the
   formula field, create your formula using "Today" as if it held the column date/time.
   SharePoint will calculate the formula based on the assumption that you will
   be using "Today" as a reference to the new column you just created.MK Note: I created a column called MonthCheck with the formula shown below:
    =IF(MONTH([Today])=MONTH([DOB]),"Birthday","NotBirthday")
3. Next, edit the new column named "Today" that you created in the first step.  
   On the very bottom of the page, click "Delete", to delete the column.  In
   your formula, SharePoint will keep the reference to "Today" but it will
   change from referencing your column, to a reference to the current date.
4. MK Note: Now you can create your new view in the list to display “This Month's Birthdays”.  Just apply a filter to Show only when the following is true: MonthCheck is equal to BirthdayI've also created a BirthDay Column (Capitalized the “D” to note the difference) as well that is a calculated column: =DATE(YEAR(Today),MONTH(DOB),DAY(DOB))
   You can then create a view to display Today's Birthdays by filtering to Show only when the following is true: BirthDay is equal to [Today]

This can be used in any of the Date and Time functions, but I haven't tested

it beyond that.

Notes:

If you want to edit the formula (CheckMonth) containing "Today" SharePoint will not let

you, and will give you the same error about not using Today or Me in a

function.  To get passed this problem you have to temporarily create another

Today column (and then delete it again).

The same functionality will also work with [Me].

Note:
You can only use the TODAY function as a default value; you cannot use it in a calculated column.

SharePoint Document Rating

To Implement Document Rating or Picture ratings in Moss 2007,

 

Use the below third party feature (.WSP) downloads:

 

http://sptoolbasket.codeplex.com/releases/view/21420

 

Refer below PDFs for steps to install and activate this feature:

 

SharePoint content rating: http://sptoolbasket.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=21960#DownloadId=56840

SharePoint Tool Basket: http://sptoolbasket.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=21960#DownloadId=69328

 

Hope it helps!

SharePoint 2007 Maximum Limitations

 

 

Following is a list of names and other parameters with the maximum allowable size on each.

Entity                        Max Permissible Size
Site Name                    128 characters
Site URL                 255 characters
Display name                 128 characters
Connection string                 384 characters
Email address                    128 characters
Version numbers                064 characters
Virtual Server Friendly Name            064 characters
SQL Database Name                123 characters
SQL Database Column                128 characters
SQL Database Table Name            128 characters
SQL Role Name                    128 characters
Server Name                    128 characters
Windows User Name                300 characters
Windows Password                300 characters
Dependencies per object            032 objects
Zone enumeration value            004 zones
Default SQL command timeout             300 seconds
Number of simultaneous
workflows that can be run*             015

If during your course of using the product, you inadvertently cross these limits, then you would end up with errors. These are hard limits.

 
 

* This is the maximum number of simultaneous workflows that can be in memory executing code. (NOTE: there is no limit to the number of workflow instances in progress in the database)

 

SharePoint 2007 figures & numbers

Site object	Guidelines for acceptable performance	Notes	Scope of impact when performance degrades
Site collection	50,000 per Web application	Total farm throughput degrades as the number of site collections increases.	Farm
Web site	250,000 per site collection	You can create a very large total number of Web sites by nesting the subsites. For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The maximum recommended number of sites and subsites is 125 sites with 2,000 subsites each, for a total of 250,000 sites.	Site collection
Subsite	2,000 per Web site	The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000.	Site view
Document	5 million per library	You can create very large document libraries by nesting folders, using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored.	Library
Item	2,000 per view	Testing indicates a reduction in performance beyond two thousand items. Using indexing on a flat folder view can improve performance.	List view
Document file size	50MB (2GB max*)	File save performance is proportional to the size of the file. The default maximum is 50 MB. This maximum is enforced by the system, but you can change it to any value up to 2 GB.	Library, file save performance
List	2,000 per Web site	Testing indicates a reduction in list view performance beyond two thousand entries.	List view
Field type	256 per list	This is not a hard limit, but you might experience list view performance degradation as the number of field types in a list increases.	List view
Column	2,000 per document library4,096 per list	This is not a hard limit, but you might experience library and list view performance degradation as the number of columns in a document library or list increases.	Library and list view
Web Part	50 per page	This figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected.	Page

The following table lists the recommended guidelines for people objects.

People object	Guidelines for acceptable performance	Notes
Users in groups	2 million per Web site	You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users.
User profile	5 million per farm	This number represents the number of profiles which can be imported from a directory service, such as Active Directory, into the people profile store.
Security principal	2,000 per Web site	The size of the access control list is limited to a few thousand security principals (users and groups in the Web site).

The following table lists the recommended guidelines for search objects.

Search object	Guidelines for acceptable performance	Notes
Search indexes	One per SSPMaximum of 20 per farm	Office SharePoint Server 2007 supports one content index per SSP. Given that we recommend a maximum of 20 SSPs per farm, a maximum of 20 content indexes is supported. Note that an SSP can be associated with only one index server and one content index. However, an index server can be associated with multiple SSPs and have a content index for each SSP.
Indexed documents	50,000,000 per content index	Office SharePoint Server 2007 supports 50 million documents per index server. This could be divided up into multiple content indexes based on the number of SSPs associated with an index server.
Content sources	500 per SSP*	This is a hard limit enforced by the system.
Start Addresses	500 per content source*	This is a hard limit enforced by the system.
Alerts	1,000,000 per SSP	This is the tested limit.
Scopes	200 per site	This is a recommended limit per site. We recommend a maximum of 100 scope rules per scope.
Display groups	25 per site	These are used for a grouped display of scopes through the user interface.
Crawl rules	10,000 per SSP	We recommend a maximum 10,000 crawl rules irrespective of type.
Keywords	15,000 per site	We recommend a maximum of 10 Best Bets and five synonyms per keyword.
Crawled properties	500,000 per SSP	These are properties that are discovered during a crawl.
Managed properties	100,000 per SSP	These are properties used by the search system in queries. Crawled properties are mapped to managed properties. We recommend a maximum of 100 mappings per managed property.
Authoritative pages	200 per relevance level	This is the maximum number of sites in each of the four relevance levels.
Results removal	100	This is the maximum recommended number of URLs that should be removed from the system in one operation.
Crawl logs	50,000,000	Number of individual log entries in the crawl log.

The following table lists the recommended guidelines for logical architecture objects.

Logical architecture object	Guidelines for acceptable performance	Notes
Shared Services Provider (SSP)	3 per farm (20 per farm maximum)
Zone	5* per farm	The number of zones defined for a farm is hard coded to 5.
Web application	99 per SSP	This limit includes the number of Web applications on child farms consuming resources on this SSP.
Internet Information Services (IIS) application pool	8 per Web server	Maximum number is determined by hardware capabilities.
Site collection	50,000 per Web application
Content database	100 per Web application
Site collection	50,000 per database

The following table lists the recommended guidelines for physical objects.

Physical object	Guidelines for acceptable performance	Notes
Index servers	1 per SSP*
Application servers running Excel Calculation Services	No limit
Query servers	No limit	Because 100 content databases are supported for each query server, the number of query servers required per farm is based on the number of content databases in the farm. For example, if there are 500 content databases in your farm, you will need at least 5 query servers.
Web server/database server ratio	8 Web servers per database server	The scale out factor is dependent upon the mix of operations.
Web server/domain controller ratio	3 Web servers per domain controller	Depending on how much authentication traffic is generated, your environment may support a greater number of Web servers per domain controller.

You can find the full article on technet, with graphs and test environment settings that will help to complete the scenario.

Hope it helps

Configure usage reporting

About usage reporting
Usage reporting is a service that enables site administrators, site collection administrators, and Shared Services Provider (SSP) administrators to monitor statistics about the use of their sites. Usage reporting also includes usage reporting for search queries that can be viewed by SSP administrators for search and site collection administrators.

To configure usage reporting, a farm administrator must first enable Windows SharePoint Services usage logging for the farm that hosts the Web application containing the SSP. The SSP administrator enables and configures the usage reporting service. Then, site collection administrators can activate the reporting feature to enable usage reports on the site collection.

After usage reporting is enabled, site administrators and site collection administrators can view site usage summary pages that have the following information for their sites and site collections:

Requests and queries in the last day and the last 30 days.

Average number of requests per day over the last 30 days.

A chart of requests per day over the last 30 days.

A list of the top page requests over the last 30 days.

A list of top users over the last 30 days.

A chart of top referring hosts over the last 30 days.

A chart of top referring pages over the last 30 days.

A list of top destination pages over the last 30 days.

Top queries for the last 30 days (if search usage reporting is enabled).

Search results top destination pages (if search usage reporting is enabled).

SSP administrators for the search service can view a search usage reports page that tracks the following information.

Number of queries per day over the previous 30 days.

Number of queries per month over the previous 12 months.

Top queries over the previous 30 days.

Top site collections originating queries over the previous 30 days.

Queries per search scope over the previous 30 days.

Site collection administrators for the SSP site can view a usage summary page that tracks the following information:

Total amount of storage used by the site collection.

Percent of storage space used by Web Discussions.

Maximum storage space allowed.

Number of users for all sites in the hierarchy.

Total hits and recent bandwidth usage across all sites.

Site collection administrators can also view a site usage report that includes monthly and daily page hit totals filtered by the following criteria:

Page

User

Operating system

Browser

Referrer URL

Usage reporting is very useful for managing complex site hierarchies with many sites, a large number of page hits, and a large number of search queries, and it is recommended that the service be enabled for deployments of complex site hierarchies. For less complex deployments, usage reporting might not be necessary. It is also possible to disable the service temporarily to conserve resources when other those resources are needed for other processes.

Enable Windows SharePoint Services usage logging
Before you can enable usage reporting in a SSP, you must first enable Windows SharePoint Services usage logging for the farm hosting the Web application containing the SSP.

Use the following procedure to enable usage logging for the farm.

Enable usage logging for the farm
1.On the Central Administration home page, click Operations.

2.On the Operations page, in the Logging and Reporting section, click Usage analysis processing.

3.On the Usage Analysis Processing page, in the Logging Settings section, select Enable logging.

4.Type a log file location and number of log files to create.

5.In the Processing Settings section, select Enable usage analysis processing, and then select a time to run usage processing.

6.Click OK.

For information about how to perform this procedure using the Stsadm command-line tool, see Usage Analysis: Stsadm properties (Office SharePoint Server).

Enable usage reporting
After Windows SharePoint Services usage logging is enabled in the server farm, SSP administrators must enable the usage reporting service. SSP administrators can control the complexity of usage analysis processing, and select whether or not reporting is enabled for search queries.

Use the following procedure to enable usage reporting.

Enable usage reporting:
1.On the SSP home page, in the Office SharePoint Usage Reporting section, click Usage reporting.

2.On the Configure Advanced Usage Analysis Processing page, in the Processing Settings section, click Enable advanced usage analysis processing.

3.In the Search Query Logging section, select Enable search query logging.

4.Click OK.

If advanced usage analysis processing is not selected, usage reporting statistics will be minimal.

For information about how to perform this procedure using the Stsadm command-line tool, see Usage Analysis: Stsadm properties (Office SharePoint Server).

Activate usage reporting
After usage reporting is enabled for the SSP, site collection administrators must activate the reporting feature. Until the reporting feature is activated on a site collection, usage reports are not available.

Use the following procedure to activate the reporting feature.

Activate the reporting feature:
1.On the Site Actions menu, click Site Settings.

2.On the Site Settings page, in the Site Collection Administration section, click Site collection features.

3.On the Site Collection Features page, click the Activate button for the Reporting feature.

For information about how to perform this procedure using the Stsadm command-line tool, see Usage Analysis: Stsadm properties (Office SharePoint Server).

Monitor usage reporting

Usage reporting can be viewed in several places:

Site administrators, including administrators of the SSP administration site, can view usage reporting for their site by clicking Site usage reports in the Site Administration section of the Site Settings page.

Site collection administrators can view usage reporting by clicking Site collection usage reports in the Site Collection Administration section of the Site Settings page.

Site collection administrators for the SSP administration site can view a usage summary by clicking Usage summary in the Site Collection Administration section of the Site Settings page.

SSP administrators for search can view search usage reports by clicking Search usage reports in the Search section of the SSP home page.

For information about how to perform this procedure using the Stsadm command-line tool, see Usage Analysis: Stsadm properties (Office SharePoint Server).


ref: http://technet.microsoft.com/en-us/library/cc262541(office.12).aspx