words from Azhar

Disabling Shutdown Event Tracker from Windows Server 2008 R2

noreply@blogger.com (Azhar Hussain) — Fri, 20 Jan 2012 05:25:00 +0000

The Windows Shutdown Event Tracker is simply annoying on a development machine.

To turn this feature off, following steps need to be taken

click the Start button, select Run…, enter gpedit.msc, and click OK.
Scroll down, right-click on Display Shutdown Event Tracker, and select Edit.
Select the Disabled option and click OK, as shown in the screenshot given below

Disabling Loopback Check from Windows Server 2008 R2

noreply@blogger.com (Azhar Hussain) — Sun, 15 Jan 2012 05:19:00 +0000

A loopback check is a security feature to mitigate against reflection attacks, introduced in Windows Server 2003 SP1.

In order to avoid connection issues with locally hosted websites it is universally recommended that loopback check must be disable on a development server.
This is done from the registry editor following are the steps for disabling loopback check

Click on the Start menu button, choose Run…, enter Regedit, and click OK to open registry editor.
Navigate to HKEY_LOCAL_MACHINE | SYSTEM | CurrentControlSet | Control | Lsa

Right-click the Lsa node and select New | DWORD (32-bit) Value
In the place of New Value #1 type DisableLoopbackCheck.

Right-click DisableLoopbackCheck, select Modify, change the value to 1, and click OK

Congratulations! You have successfully configured Windows Server 2008 R2

Remove multiple lists or libraries from the Quick Launch

noreply@blogger.com (Azhar Hussain) — Wed, 11 Jan 2012 07:18:00 +0000

The following steps to remove multiple lists or libraries from the Quick Launch are required to be perform

On the Site Actions menu, click Site Settings.
In the Look and Feel column, click Navigation. " NOTE The Navigation command appears under Look and Feel only if the publishing features are enabled for your site and you have the Full Control or Design permission level."
In the Navigation Editing and Sorting section, select the list or library that you want to remove from the Quick Launch, and then click Delete.
Repeat step 3 to remove any additional lists or libraries.
When you are finished removing lists and libraries, click OK.

SharePoint 2010 : Workspace limits

noreply@blogger.com (Azhar Hussain) — Fri, 30 Dec 2011 05:43:00 +0000

The following table lists the recommended guidelines for Microsoft SharePoint Workspace 2010.

Limit	Maximum value	Limit type	Notes
SharePoint Workspace synchronization	30,000 items per list	Boundary	SharePoint Workspace will not synchronize lists that have more than 30,000 items. This restriction exists because the time to download a list that has more than 30,000 items is very long, and resource usage is high.
SharePoint Workspace synchronization	1800 documents limit in SharePoint Workspace	Boundary	Users are warned when they have more than 500 documents in SharePoint Workspace, but they can continue to add documents.

Upgrading latest content from SP2007 to SP2010 Portal

noreply@blogger.com (Azhar Hussain) — Sun, 04 Dec 2011 08:20:00 +0000

To export latest content from current SP 2007 site in production and upgrade and import that content to new SP 2010 portal it is recommended to use third party tools available to use for the ease in administrative usage but however the work around to perform this function following steps are required
1. Take the product site down for sometime (users should be informed earlier for this downtime if this activity is performed in office hours)
2. Detach content database from SP 2007 existing SP2007 web application from Central Administration
3. Stop SQL Server services and copy the same content database from SQL Server Database ( same which was detached from central admin in previous steps)
4. Copy the mdf and ldf files and paste to SP 2010 Database server.
5. Restart the SQL Server services.
6. Reattach the Content DB from to the Web Application in Central Admin
7. Now SP 2007 Site should be up and running
8. Now move to the production SQL Server database of SP 2010 portal and repeat the same as done in step 2 and 3 in SP 2010 Central Administration.
9. Attach to mdf and ldf file to SQL Server.
10. On the Start menu, click All Programs.
11. Click Microsoft SharePoint 2010 Products.
12. Click SharePoint 2010 Management Shell.
13. At the Windows PowerShell command prompt, type the following command:
"Mount-SPContentDatabase -Name -DatabaseServer -WebApplication [-Updateuserexperience]"
Where:
a. is the name of the database you want to upgrade
b. is server on which the database is stored.
c. is the URL for the Web application that will host the sites.
d. Updateuserexperience is the choice to update to the new user experience or stay in the old user experience (part of Visual Upgrade).
When you include this parameter, the site is set to preview the new user experience. Omit this parameter if you want the site to remain in the old user experience after upgrade. For more information, see Plan visual upgrade (SharePoint Server 2010).
14. Now reattach this upgraded database as a content database to the SP2010 Portal. For more detail please refer to following technet article http://technet.microsoft.com/en-us/library/cc263299.aspx

SharePoint 2010 : Visio Services limits

noreply@blogger.com (Azhar Hussain) — Fri, 02 Dec 2011 05:34:00 +0000

The following table lists the recommended guidelines for instances of Visio Services in Microsoft SharePoint Server 2010.

Limit	Maximum value	Limit type	Notes
File size of Visio Web drawings	50 MB	Threshold	Visio Services has a configuration setting that enables the administrator to change the maximum size of Web drawings that Visio processes. Larger file sizes have the following side effects: · Increase in the memory footprint of Visio Services. · Increase in CPU usage. · Reduction in application server requests per second. · Increase overall latency. · Increase SharePoint farm network load
Visio Web drawing recalculation time-out	120 seconds	Threshold	Visio Services has a configuration setting that enables the administrator to change the maximum time that it can spend recalculating a drawing after a data refresh. A larger recalculation time-out leads to: · Reduction in CPU and memory availability. · Reduction in application requests per second. · Increase in average latency across all documents. A smaller recalculation time-out leads to: · Reduction of the complexity of diagrams that can be displayed. · Increase in requests per second. · Decrease in average latency across all documents.
Visio Services minimum cache age (data connected diagrams)	Minimum cache age: 0 to 24hrs	Threshold	Minimum cache age applies to data connected diagrams. It determines the earliest point at which the current diagram can be removed from cache. Setting Min Cache Age to a very low value will reduce throughput and increase latency, because invalidating the cache too often forces Visio to recalculate often and reduces CPU and memory availability.
Visio Services maximum cache age (non-data connected diagrams)	Maximum cache age: 0 to 24hrs	Threshold	Maximum cache age applies to non-data connected diagrams. This value determines how long to keep the current diagram in memory. Increasing Max Cache Age decreases latency for commonly requested drawings. However, setting Max Cache Age to a very high value increases latency and slows throughput for items that are not cached, because the items already in cache consume and reduce available memory.

SharePoint 2010 : Web Analytics service limits

noreply@blogger.com (Azhar Hussain) — Wed, 23 Nov 2011 05:39:00 +0000

The following table lists the recommended guidelines for the SharePoint Web Analytics service.

Limit	Maximum value	Limit type	Notes
SharePoint entities	30,000 per farm when Web Analytics is enabled	Supported	Do not enable Web Analytics if your farm contains, or is expected to contain, more than 30,000 SharePoint entities, which include all Web applications, site collections, and sites. This number is not exact, because different combinations of SharePoint entities might have a greater or lesser effect on farm performance than the tested scenario, which is described in the article Capacity requirements for the Web Analytics Shared Service in SharePoint Server 2010. However, as the number of SharePoint entities in your farm closely approaches this limit, farm performance might fall to unacceptable levels.

For more information about boundaries and limits for the SharePoint Web Analytics service, see Capacity requirements for the Web Analytics Shared Service in SharePoint Server 2010.

SharePoint 2010 : Word Automation Services limits

noreply@blogger.com (Azhar Hussain) — Tue, 22 Nov 2011 05:42:00 +0000

The following table lists the recommended guidelines for Word Automation Services.

Limit	Maximum value	Limit type	Notes
Input file Size	512 MB	Boundary	Maximum file size that can be processed by Word Automation Services.
Frequency with which to start conversions (minutes)	1 minute (recommended) 15 minutes (default) 59 minutes (boundary)	Threshold	This setting determines how often the Word Automation Services timer job executes. A lower number leads to the timer job running faster. Our testing shows that it is most useful to run this timer job once per minute.
Number of conversions to start per conversion process	For PDF/XPS output formats: 30 x MFor all other output formats: 72 x M Where M is the value of Frequency with which to start conversions (minutes)	Threshold	The number of conversions to start affects the throughput of Word Automation Services. If these values are set higher than the recommended levels then some conversion items may start to fail intermittently and user permissions may expire. User permissions expire 24 hours from the time that a conversion job is started.
Conversion job size	100,000 conversion items	Supported	A conversion job includes one or more conversion items, each of which represents a single conversion to be performed on a single input file in SharePoint. When a conversion job is started (using the ConversionJob.Start method), the conversion job and all conversion items are transmitted over to an application server which then stores the job in the Word Automation Services database. A large number of conversion items will increase both the execution time of the Start method and the number of bytes transmitted to the application server.
Total active conversion processes	N-1, where N is the number of cores on each application server	Threshold	An active conversion process can consume a single processing core. Therefore, customers should not run more conversion processes than they have processing cores in their application servers. The conversion timer job and other SharePoint activities also require occasional use of a processing core. We recommend that you always leave 1 core free for use by the conversion timer job and SharePoint.
Word Automation Services database size	2 million conversion items	Supported	Word Automation Services maintains a persistent queue of conversion items in its database. Each conversion request generates one or more records. Word Automation Services does not delete records from the database automatically, so the database can grow indefinitely without maintenance. Administrators can manually remove conversion job history by using the Windows PowerShell cmdlet Remove-SPWordConversionServiceJobHistory. For more information, see Remove-SPWordConversionServiceJobHistory.

SharePoint 2010 : OneNote limits

noreply@blogger.com (Azhar Hussain) — Sun, 20 Nov 2011 05:46:00 +0000

The following table lists the recommended guidelines for Microsoft OneNote Services.

Limit	Maximum value	Limit type	Notes
Number of Sections and Section Groups in a OneNote Notebook (on SharePoint)	See limit for "Documents" in List and library limits		Each section counts as one folder and one document in the list. Each section group counts as one folder and one document in the list.
Maximum size of a section	See limit for "File size" in List and library limits		This maximum excludes any images, embedded files, and XPS printouts to OneNote that are larger than 100 KB. Images and embedded files larger than 100 KB are split out into their own binary files. This means that a section with 100 KB of typed data and four embedded Word documents of 1 MB each will be considered a 100 KB section.
Maximum size of an image, embedded file, and XPS OneNote printout in a OneNote section.	See limit for "File size" in List and library limits		Each item is stored as a separate binary file and is therefore subject to file size limits. Each print operation to OneNote will result in one XPS printout binary, even if the printout contains multiple pages.
Maximum size of all images, embedded files, and XPS printouts in a single OneNote page.	Default limit is double the "File size" limit.	Threshold	This applies to embedded content in a single OneNote page, not a Section or Notebook. If users encounter this, they will see the following error in OneNote: jerrcStorageUrl_HotTableFull (0xE0000794). Users can work around this by splitting embedded content into different pages and deleting previous versions of the page. If users have to adjust this value (“Max Hot Table Size”), the effective limit is half of the absolute value they define (for example, specifying a 400 MB max hot table size means that the maximum size of all embedded content on a page is limited to 200 MB).
Merge operations	One per CPU core per Web server	Boundary	OneNote merges combine changes from multiple users who are co-authoring a notebook. If no CPU core is available to run a merge, a conflict page is generated instead, which forces the user perform the merge manually). This limit applies whether OneNote is running as a client application or as a Microsoft Office Web Apps.

SharePoint 2010 : Workflow limits

noreply@blogger.com (Azhar Hussain) — Fri, 18 Nov 2011 05:32:00 +0000

The following table lists the recommended guidelines for workflow.

Limit

Maximum value

Limit type

Notes

Workflow postpone threshold

Threshold

15 is the maximum number of workflows allowed to be executing against a content database at the same time, excluding instances that are running in the timer service. When this threshold is reached, new requests to activate workflows will be queued to be run by the workflow timer service later. As non-timer execution is completed, new requests will count against this threshold. This is limit can be configured by using the Set-SPFarmConfig Windows PowerShell cmdlet. For more information, see Set-SPFarmConfig.

Note: This limit does not refer to the total number of workflow instances that can be in progress. Instead, it is the number of instances that are being processed. Increasing this limit increases the throughput of starting and completing workflow tasks but also increases load against the content database and system resources.

Workflow timer batch size

100

Threshold

The number of events that each run of the workflow timer job will pick up and deliver to workflows. It is configurable by using Windows PowerShell. To allow for additional events, you can run additional instances of the Microsoft SharePoint Foundation Workflow Timer Service.

SharePoint 2010 : Office Web Application Service limits

noreply@blogger.com (Azhar Hussain) — Thu, 17 Nov 2011 05:49:00 +0000

The following table lists the recommended guidelines for Office Web Apps. Office client application limits also apply when an application is running as a Web app.

Limit	Maximum value	Limit type	Notes
Cache size	100 GB	Threshold	Space available to render documents, created as part of a content database. By default, the cache available to render documents is 100 GB. We do not recommend that you increase the available cache.
Renders	One per document per second per CPU core per application server (maximum eight cores)	Boundary	This is the measured average number of renders that can be performed of "typical" documents on the application server over a period of time.

SharePoint 2010 : PerformancePoint Services limits

noreply@blogger.com (Azhar Hussain) — Tue, 15 Nov 2011 05:40:00 +0000

The following table lists the recommended guidelines for PerformancePoint Services in Microsoft SharePoint Server 2010.

Limit	Maximum value	Limit type	Notes
Cells	1,000,000 per query on Excel Services data source	Boundary	A PerformancePoint scorecard that calls an Excel Services data source is subject to a limit of no more than 1,000,000 cells per query.
Columns and rows	15 columns by 60,000 rows	Threshold	The maximum number of columns and rows when rendering any PerformancePoint dashboard object that uses a Microsoft Excel workbook as a data source. The number of rows could change based on the number of columns.
Query on a SharePoint list	15 columns by 5,000 rows	Supported	The maximum number of columns and row when rendering any PerformancePoint dashboard object that uses a SharePoint list as a data source. The number of rows could change based on the number of columns.
Query on a SQL Server data source	15 columns by 20,000 rows	Supported	The maximum number of columns and row when rendering any PerformancePoint dashboard object that uses a SQL Server table data source. The number of rows could change based on the number of columns.

SharePoint 2010 : Business Connectivity Services limits

noreply@blogger.com (Azhar Hussain) — Sat, 12 Nov 2011 05:29:00 +0000

The following table lists the recommended guidelines for Business Connectivity Services.

Limit	Maximum value	Limit type	Notes
ECT (in-memory)	5,000 per Web server (per tenant)	Boundary	Total number of external content type (ECT) definitions loaded in memory at a given point in time on a Web server.
External system connections	500 per Web server	Boundary	Number of active/open external system connections at a given point in time. The default maximum value is 200; the boundary is 500. This limit is enforced at the Web Server scope, regardless of the kind of external system (for example, database, .NET assembly, and so on) The default maximum is used to restrict the number of connections. An application can specify a larger limit via execution context; the boundary enforces the maximum even for applications that do not respect the default.
Database items returned per request	2,000 per database connector	Threshold	Number of items per request the database connector can return. The default maximum of 2,000 is used by the database connector to restrict the number of result that can be returned per page. The application can specify a larger limit via execution context; the Absolute Max enforces the maximum even for applications that do not respect the default. The boundary for this limit is 1,000,000.

SharePoint 2010 : Blog limits

noreply@blogger.com (Azhar Hussain) — Fri, 04 Nov 2011 05:26:00 +0000

The following table lists the recommended guidelines for blogs.

Limit	Maximum value	Limit type	Notes
Blog posts	5,000 per site	Supported	The maximum number of blog posts is 5,000 per site.
Comments	1,000 per post	Supported	The maximum number of comments is 1,000 per post.

SharePoint 2010 : Content deployment limits

noreply@blogger.com (Azhar Hussain) — Sat, 29 Oct 2011 05:23:00 +0000

The following table lists the recommended guidelines for content deployment

Limit

Maximum value

Limit type

Notes

Content deployment jobs running on different paths

Supported

For concurrently running jobs on paths that are connected to site collections in the same source content database, there is an increased risk of deadlocks on the database. For jobs that must run concurrently, we recommend that you move the site collections into different source content databases.

Note:

Concurrent running jobs on the same path are not possible.

If you are using SQL Server snapshots for content deployment, each path creates a snapshot. This increases the I/O requirements for the source database.

For more information, see About deployment paths and jobs.

SharePoint 2010 : Managed Metadata term store (database) limits

noreply@blogger.com (Azhar Hussain) — Fri, 28 Oct 2011 05:20:00 +0000

The following table lists the recommended guidelines for managed metadata term stores.

Limit

Maximum value

Limit type

Notes

Maximum number of levels of nested terms in a term store

Supported

Terms in a term set can be represented hierarchically. A term set can have up to seven levels of terms (a parent term, and six levels of nesting below it.)

Maximum number of term sets in a term store

1,000

Supported

You can have up to 1,000 term sets in a term store.

Maximum number of terms in a term set

30,000

Supported

30,000 is the maximum number of terms in a term set.

Note:

Additional labels for the same term, such as synonyms and translations, do not count as separate terms.

Total number of items in a term store

1,000,000

Supported

An item is either a term or a term set. The sum of the number of terms and term sets cannot exceed 1,000,000. Additional labels for the same term, such as synonyms and translations, do not count as separate terms.

Note:

You cannot have both the maximum number of term sets and the maximum number of terms simultaneously in a term store.

Single-Sign-On - Concept

noreply@blogger.com (Azhar Hussain) — Tue, 25 Oct 2011 20:42:00 +0000

SSO Services provide an SSO ticketing mechanism to enable EAI products to deal with the problem of maintaining a user token across multiple computers and processes when working with Enterprise Single Sign-On. This lets the user achieve a Single Sign-on in a secure manner using Enterprise Single Sign-on. You should be aware that this ticket is not a Kerberos ticket. It is referred to as an SSO Ticket and is for use only within the SSO system. This is based on issuing a ticket on one computer (or by a certain process) and redeeming the ticket on a different computer (or a different process). Issuing a ticket means that a component calls into SSO Service to obtain an SSO ticket that represents the Windows user. Redeeming the ticket means that a component provides the ticket to SSO Service to obtain the Host credentials corresponding to the Windows user who initiated the original request. An SSO ticket is issued only to an authenticated user for making a request on his or her own behalf. In other words, User A can only obtain a ticket for User A. Even an SSO administrator cannot request a ticket for another user. The user making the request to obtain a ticket must be a valid authenticated domain user. This means that if the user is Anonymous or not a valid domain account then access will be denied when a request to obtain the ticket is made. The ticket generated by SSO Services primarily contains the user logon identity (domain\userid) and a time stamp indicating when the ticket was issued. This ticket is also encrypted by SSO Services. There is also a ticket timeout value configured at the SSO system level that determines when the ticket will expire. The ticket can be redeemed by a service account that is a member of the Application Administrators account for an Affiliate Application.

Project Server 2010 limits

noreply@blogger.com (Azhar Hussain) — Mon, 24 Oct 2011 17:51:00 +0000

The following table lists the recommended guidelines for Microsoft Project Server. For more information about how to plan for Project Server, see Planning and architecture for Project Server 2010.

Limit	Maximum value	Limit type	Notes
End of project time	Date: 12/31/2049	Boundary	Project plans cannot extend past the date 12/31/2049.
Deliverables per project plan	1,500 deliverables	Boundary	Project plans cannot contain more than 1,500 deliverables.
Number of fields in a view	256	Boundary	A user cannot have more than 256 fields added to a view that they have defined in Project Web App.
Number of clauses in a filter for a view	50	Boundary	A user cannot add a filter to a view that has more than 50 clauses in it.

Difference between SharePoint 2010 Picture Library and Asset Library

noreply@blogger.com (Azhar Hussain) — Thu, 29 Sep 2011 09:37:00 +0000

SharePoint 2010 is featured with the Asset Library which conceptually is similar to the Picture Library. Asset Library support storing pictures like Picture Library and supports storing video and audio.

Selection between both confuses sometimes, so identifying differences between them should be know to us prior making decision of selecting any one to fit the bill.

Here I will discuss some some of the differences between the two in terms of storing pictures.

The Picture Library does not have the ribbon toolbar. The Asset Library does. The Picture Library toolbar is one of the few places that still has a 2007 style toolbar.
Uploading Multiple Documents to a Picture Library uses Microsoft Office Picture Manager and only displays your "My Pictures" folder. You cannot navigate to other locations on your network without first adding a Picture Shortcut.
Uploading Multiple Documents to an Asset Library uses the standard “Office Document Uploader” that is the same one used in a Document Library. You can browse your entire network by default.
The Picture Library uses the Picture Content Type.
The Asset Library uses the Image Content Type.
These content types have similar fields.
Both have Name, Title, Preview, Keywords, Comments, Date Picture Taken, and Picture Size fields.
The Picture Content Type also has a Preview Image URL field not found in the Image Content Type.
The Image Content Type also has Author and Copyright fields not found in the Picture Content Type.
The Content Class returned for Picture Libraries in Search is STS_ListItem_PictureLibrary
Both libraries will automatically generate thumbnails of the pictures that are uploaded. Both name and store these thumbnails the same way.
Picture Library images will show the thumbnail in searches, while Asset Library images will not however there is a work around for showing thumbnail in asset library searches but it does not support OOB (out of box).

This post will be updated as soon as I find some more differences between them using my working experience/study/research. You can also share any other difference as per you knowledge.

On creating the Server farm SharePoint_Config database name is editable

noreply@blogger.com (Azhar Hussain) — Tue, 27 Sep 2011 19:58:00 +0000

1. You will be presented with the Server Farm Connection screen.

2. VERY IMPORTANT! Select the "No, I want to create a new server farm" option NOT the "Yes, I want to connect to an existing server farm" option if this is your SPWEB server cycle. This is a very confusing option because you already have a server farm and instinctively you would want to just add to the farm as opposed to creating a new. To clarify, we're not doing anything with the old farm which is why we need to create an entirely new farm.

3. Click the "Next" button to continue.

4. Next you will be presented with the Database Settings page.

5. Enter the name of your SQL Server into the "Database Server" edit box e.g. "SPSQL".

6. By default the Config Wizard will have populated the "Database Name" edit box with "SharePoint_Config". You can change this value if you want or you can simply accept the default setting. It is recommended that your retain the "Config" moniker in the name though as it will help you identify your database later on during administration and backups.

SHAREPOINT 2010 : User Profile Service limits

noreply@blogger.com (Azhar Hussain) — Thu, 22 Sep 2011 08:24:00 +0000

The following table lists the recommended guidelines for User Profile Service.

Limit	Maximum value	Limit type	Notes
User profiles	2,000,000 per service application	Supported	A user profile service application can support up to 2 million user profiles with full social features functionality. This number represents the number of profiles that can be imported into the people profile store from a directory service, and also the number of profiles a user profile service application can support without leading to performance decreases in social features.
Social tags, notes and ratings	500,000,000 per social database	Supported	Up to 500 million total social tags, notes and ratings are supported in a social database without significant decreases in performance. However, database maintenance operations such as backup and restore may show decreased performance at that point.

SHAREPOINT 2010 : Security limits

noreply@blogger.com (Azhar Hussain) — Fri, 16 Sep 2011 08:18:00 +0000

Limit	Maximum value	Limit type	Notes
Number of SharePoint groups a user can belong to	5,000	Supported	This is not a hard limit but it is consistent with Active Directory guidelines. There are several things that affect this number: · The size of the user token · The groups cache: SharePoint Server 2010 has a table that caches the number of groups a user belongs to as soon as those groups are used in access control lists (ACLs). · The security check time: as the number of groups that a user is a member of increases, the time that is required for the access check increases also.
Users in a site collection	2 million per site collection	Supported	You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users. This limit is based on manageability and ease of navigation in the user interface. When you have many entries (security groups of users) in the site collection (more than one thousand), you should use Windows PowerShell to manage users instead of the UI. This will provide a better management experience.
Active Directory Principles/Users in a SharePoint group	5,000 per SharePoint group	Supported	SharePoint Server 2010 enables you to add users or Active Directory groups to a SharePoint group. Having up to 5,000 users (or Active Directory groups or users) in a SharePoint group provides acceptable performance. The activities most affected by this limit are as follows: · Fetching users to validate permissions. This operation takes incrementally longer with growth in number of users in a group. · Rendering the membership of the view. This operation will always require time.
SharePoint groups	10,000 per site collection	Supported	Above 10,000 groups, the time to execute operations is increased significantly. This is especially true of adding a user to an existing group, creating a new group, and rendering group views.
Security principal: size of the Security Scope	5,000 per Access Control List (ACL)	Supported	The size of the scope affects the data that is used for a security check calculation. This calculation occurs every time that the scope changes. There is no hard limit, but the bigger the scope, the longer the calculation takes.

SHAREPOINT 2010 : Column limits

noreply@blogger.com (Azhar Hussain) — Fri, 16 Sep 2011 08:02:00 +0000

SharePoint Server 2010 data is stored in SQL Server tables. To allow for the maximum number of possible columns in a SharePoint list, SharePoint Server will create several rows in the database when data will not fit on a single row. This is called row wrapping.

Each time that a row is wrapped in SQL Server, an additional query load is put on the server when that item is queried because a SQL join must be included in the query. To prevent too much load, by default a maximum of six SQL Server rows are allowed for a SharePoint item. This limit leads to a particular limitation on the number of columns of each type that can be included in a SharePoint list. The following table describes the limits for each column type.

The row wrapping parameter can be increased beyond six, but this may result in too much load on the server. Performance testing is recommended before exceeding this limit. For more information, see Designing large lists and maximizing list performance (SharePoint Server 2010).

Each column type has a size value listed in bytes. The sum of all columns in a SharePoint list cannot exceed 8,000 bytes. Depending on column usage, users can reach the 8,000 byte limitation before reaching the six-row row wrapping limitation.

Limit	Maximum value	Limit type	Size per column	Notes
Single line of text	276	Threshold	28 bytes	SQL Server row wrapping occurs after each 64 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 384 Single line of text columns per SharePoint list (6 * 64 = 384). However, because the limit per SharePoint list item is 8,000 bytes, of which 256 bytes are reserved for built-in SharePoint columns, the actual limit is 276 Single line of text columns.
Multiple Lines of Text	192	Threshold	28 bytes	SQL Server row wrapping occurs after each 32 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 192 Multiple lines of text columns per SharePoint list (6 * 32 = 192).
Choice	276	Threshold	28 bytes	SQL Server row wrapping occurs after each 64 columns in a SharePoint list. The default row wrapping value of 6 allows for a maximum of 384 Choice columns per SharePoint list (6 * 64 = 384); ); however because the limit per SharePoint list item is 8,000 bytes, of which 256 bytes are reserved for built-in SharePoint columns, the actual limit should be 276 Choice columns.
Number	72	Threshold	12 bytes	SQL Server row wrapping occurs after each 12 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 72 Number columns per SharePoint list (6 * 12 = 72).
Currency	72	Threshold	12 bytes	SQL Server row wrapping occurs after each 12 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 72 Currency columns per SharePoint list (6 * 12 = 72).
Date and Time	48	Threshold	12 bytes	SQL Server row wrapping occurs after each eight columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 48 Date and Time columns per SharePoint list (6 * 8 = 48).
Lookup	96	Threshold	4 bytes	SQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 96 single value Lookup columns per SharePoint list (6 * 16 = 96).
Yes / No	96	Threshold	5 bytes	SQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 96 Yes / No columns per SharePoint list (6 * 16 = 96).
Person or group	96	Threshold	4 bytes	SQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 96 Person or Group columns per SharePoint list (6 * 16 = 96).
Hyperlink or picture	138	Threshold	56 bytes	SQL Server row wrapping occurs after each 32 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 192 Hyperlink or Picture columns per SharePoint list (6 * 32 = 192) ); however because the limit per SharePoint list item is 8,000 bytes, of which 256 bytes are reserved for built-in SharePoint columns, the actual limit should be 138 Hyperlink or Picture columns.
Calculated	48	Threshold	28 bytes	SQL Server row wrapping occurs after each eight columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 48 Calculated columns per SharePoint list (6 * 8 = 48).
GUID	6	Threshold	20 bytes	SQL Server row wrapping occurs after each column in a SharePoint list. The default row wrapping value of six allows for a maximum of 6 GUID columns per SharePoint list (6 * 1 = 6).
Int	96	Threshold	4 bytes	SQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default row wrapping value of six allows for a maximum of 96 Int columns per SharePoint list (6 * 16 = 96).
Managed metadata	94	Threshold	40 bytes for the first, 32 bytes for each subsequent	The first Managed Metadata field added to a list is allocated four columns: · A lookup field for the actual tag · A hidden text field for the string value · A lookup field for the catch all · A lookup field for spillover of the catch all Each subsequent Managed Metadata field added to a list adds two more columns: · A lookup field for the actual tag · A hidden text field for the string value The maximum number of columns of Managed Metadata is calculated as (14 + (16 * (n-1))) where n is the row mapping value (default of 6).

External Data columns have the concept of a primary column and secondary columns. When you add an external data column, you can select some secondary fields of the external content type that you want to be added to the list. For example, given an External Content Type “Customer” which has fields like “ID”, “Name”, “Country”, and “Description”, when you add an External Data column of type “Customer” to a list, you can add secondary fields to show the “ID”, “Name” and “Description” of the Customer. Overall these are the columns that get added:

Primary column: A text field.
Hidden Id column: A multi-line text field.
Secondary columns: Each secondary column is a text/number/Boolean/multi-line text that is based on the data type of the secondary column as defined in the Business Data Catalog model. For example, ID might be mapped to a Number column; Name might be mapped to a Single line of text column; Description might be mapped to a Multiple lines of text column.

SHAREPOINT 2010 : Search limits

noreply@blogger.com (Azhar Hussain) — Thu, 15 Sep 2011 08:20:00 +0000

Limit	Maximum value	Limit type	Notes
SharePoint search service applications	20 per farm	Supported	Multiple SharePoint search service applications can be deployed on the same farm, because you can assign search components and databases to separate servers. The recommended limit of 20 is less than the maximum limit for all service applications in a farm.
Crawl databases and database Items	10 crawl databases per search service application 25 million items per crawl database	Threshold	The crawl database stores the crawl data (time/status, etc.) about all items that have been crawled. The supported limit is 10 crawl databases per SharePoint Search service application. The recommended limit is 25 million items per crawl database (or a total of four crawl databases per search service application).
Crawl components	16 per search service application	Threshold	The recommended limit per application is 16 total crawl components; with two per crawl database, and two per server, assuming the server has at least eight processors (cores). The total number of crawl components per server must be less than 128/(total query components) to minimize propagation I/O degradation. Exceeding the recommended limit may not increase crawl performance; in fact, crawl performance may decrease based on available resources on the crawl server, database, and content host.
Index partitions	20 per search service application; 128 total	Threshold	The index partition holds a subset of the search service application index. The recommended limit is 20. Increasing the number of index partitions results in each partition holding a smaller subset of the index, reducing the RAM and disk space that is needed on the query server hosting the query component assigned to the index partition. The boundary for the total number of index partitions is 128.
Indexed items	100 million per search service application; 10 million per index partition	Supported	SharePoint Search supports index partitions, each of which contains a subset of the search index. The recommended maximum is 10 million items in any partition. The overall recommended maximum number of items (e.g., people, list items, documents, Web pages) is 100 million.
Crawl log entries	100 million per search application	Supported	This is the number of individual log entries in the crawl log. It will follow the "Indexed items" limit.
Property databases	10 per search service application;128 total	Threshold	The property database stores the metadata for items in each index partition associated with it. An index partition can only be associated with one property store. The recommended limit is 10 property databases per search service application. The boundary for index partitions is 128.
Query components	128 per search application; 64/(total crawl components) per server	Threshold	The total number of query components is limited by the ability of the crawl components to copy files. The maximum number of query components per server is limited by the ability of the query components to absorb files propagated from crawl components.
Scope rules	100 scope rules per scope; 600 total per search service application	Threshold	Exceeding this limit will reduce crawl freshness, and delay potential results from scoped queries.
Scopes	200 site scopes and 200 shared scopes per search service application	Threshold	Exceeding this limit may reduce crawl efficiency and, if the scopes are added to the display group, affect end-user browser latency. Also, display of the scopes in the search administration interface degrades as the number of scopes passes the recommended limit.
Display groups	25 per site	Threshold	Display groups are used for a grouped display of scopes through the user interface. Exceeding this limit starts degrading the scope experience in the search administration interface.
Alerts	1,000,000 per search application	Supported	This is the tested limit.
Content sources	50 per search service application	Threshold	The recommended limit of 50 can be exceeded up to the boundary of 500 per search service application. However, fewer start addresses should be used, and the concurrent crawl limit must be followed.
Start addresses	100 per content source	Threshold	The recommended limit can be exceeded up to the boundary of 500 per content source. However, the more start addresses you have, the fewer content sources should be used. When you have many start address, we recommend that you put them as links on an html page, and have the HTTP crawler crawl the page, following the links.
Concurrent crawls	20 per search application	Threshold	This is the number of crawls underway at the same time. Exceeding this number may cause the overall crawl rate to decrease.
Crawled properties	500,000 per search application	Supported	These are properties that are discovered during a crawl.
Crawl impact rule	100	Threshold	Recommended limit of 100 per farm. The recommendation can be exceeded; however, display of the site hit rules in the search administration interface is degraded. At approximately 2,000 site hit rules, the Manage Site Hit Rules page becomes unreadable.
Crawl rules	100 per search service application	Threshold	This value can be exceeded; however, display of the crawl rules in the search administration interface is degraded.
Managed properties	100,000 per search service application	Threshold	These are properties used by the search system in queries. Crawled properties are mapped to managed properties.
Mappings	100 per managed property	Threshold	Exceeding this limit may decrease crawl speed and query performance.
URL removals	100 removals per operation	Supported	This is the maximum recommended number of URLs that should be removed from the system in one operation.
Authoritative pages	1 top level and minimal second and third level pages per search service application	Threshold	The recommended limit is one top-level authoritative page, and as few second -and third-level pages as possible to achieve the desired relevance. The boundary is 200 per relevance level per search application, but adding additional pages may not achieve the desired relevance. Add the key site to the first relevance level. Add more key sites at either second or third relevance levels, one at a time, and evaluate relevance after each addition to ensure that the desired relevance effect is achieved.
Keywords	200 per site collection	Supported	The recommended limit can be exceeded up to the maximum (ASP.NET-imposed) limit of 5,000 per site collection given five Best Bets per keyword. If you exceed this limit, display of keywords on the site administration user interface will degrade. The ASP.NET-imposed limit can be modified by editing the Web.Config and Client.config files (MaxItemsInObjectGraph).
Metadata properties recognized	10,000 per item crawled	Boundary	This is the number of metadata properties that can be determined and potentially mapped or used for queries when an item is crawled.

Deploying SharePoint Solution - IIS Restart issue : Recycle IIS Application Pool': 0x80070005 Access denied

noreply@blogger.com (Azhar Hussain) — Tue, 13 Sep 2011 15:46:00 +0000

While deploying the (WSP) solution in VS2010 running on Windows 2008, you may face the IIS Restart Issue sometime,especially if you are not logged in as and administrator.
'Recycle IIS Application Pool': 0x80070005 Access denied is the error message you get on deployment using VS 2010
The root cause of this issue is

You don't have IIS restart privilege on windows OS
Even if you have it, you have not added your login account in to SharePoint SiteCollection administrator.

Solution:

1. Open a command prompt and type "iisreset". If you able to restart, then it will restart successfully otherwise it will deny it. The reason is, Though you are in administrators group, windows 2008 will not run on the administrator privilege. Every time when you do an operation like IIS restart or Installation, it will prompt for UAC (User Account Control). You should accept the dialog box and elevate the privilege to run the operation or you can right click the application whatever you want to run and click the menu option "Run as Administrator" which will solve the issue.
If you want to avoid UAC and directly run through you admin account then, go to Control panel -> Manage account -> Hide UAC

2. If you have all the privilege and still you are getting error in VS2010 as "'Recycle IIS Application Pool':0x80070005Access denied, then you have to add your account in to site collection admin.
1) You can do this by going to Sharepoint Administration page.
2) Navigate to the site collection administration option
3) Add your name into site collection administrator as a second owner. SharePoint will allow a second owner for site colleciton
After adding it , now you can deploy the solution through VS 2010.