Difference between ghosted and unghosted and what does it mean anyway?

This question is often asked by our SharePoint students.  To keep it short and sweet, ghosted means not customized and unghosted means customized. 
I'm sure everyone knows by now that SharePoint stores web pages like .aspx and other items in a few different places. 

• The 12 Hive
• The Content Database
• IIS (in a virtual directory)
  • Some content in the 12 Hive
  • Some content nested under the InetPub folder

Well, let's say that there is a web page or other type of document that SharePoint uses that is stored in the 12 hive.  Like the default.aspx for example.  When it is first create during the install and placed in the 12 hive, it is considered to be ghosted.  An odd word for some that basically means that when the page needs to used it will be read from the folder somewhere in the 12 hive.  When your SharePoint site is created several entries are made in the Content Database (in SQL Server).  These entries tell SharePoint what Pages, List, Libraries, etc are associated with your SharePoint site.  But even though there is an entry in the database showing that your site uses the default.aspx page, it doesn't mean that the default.aspx page is stored in the database.  If you change the default.aspx (using SharePoint Designer for instance), you have customized the page and your version of the page will now be stored in the content database that stores the entries for that specific site.  The customized version of the default.aspx page is now considered unghosted for that specific site.
In other words, Ghosted pages become unghosted pages once a file has been modified.  There are several good reasons for this and there is more to the story. 

Difference between PowerShell and Stsadm in SharePoint

• Windows PowerShell is built on the Microsoft .NET Framework and accepts and returns .NET Framework objects. Hence, can interact with .Net objects directly.
• Here we use commandlets (cmdlet) instead of commands. Commandlet is a instance of .Net objects
• We can automate the tasks using power shell scripts.
• Windows PowerShell also gives you access to the file system on the computer and enables you to access other data stores, such as the registry and digital signature certificate stores.

Difference between webpart and user control in SharePoint I feel the most important difference is that the webparts supports personalization which means that changes in the personal view will be stored per user basis. Also as Rob said, the user has the freedom to add/remove as per his need. On the other hand a usercontrol is more of a kind of static one. So you need to provide a functionality that is not required to be added and removed every now and then.

Splitting large Content DB into multiple content DBs in SharePoint/MOSS 2007

Very Exciting. Getting ready to split up a large content DB on a large enterprise level moss farm deployment. The idea is to distribute data that has grown over time into multiple content databases for performance and reliability. The plan is to use stsadm -o mergecontentdbs. However this is known to have implications and issues - http://support.microsoft.com/kb/969242. We are taking all necessary steps to avoid any problems. I'll update this post later on how our operation does.
 Update - Sorry for the late update guys. heres how it went.
 We had 2 tasks ahead of us. One was to move a content db from one database server to another in the cluster. The other was to split up a large content db on one of the servers into multiple content dbs.
Splitting the large content db into multiple content DB's:
 Microsoft recommended that we do not run the merge content db command on databases larger that 10 GB in size. So instead of moving out the larger site collections into new content databses, we decided to move all of the smaller site collections out instead. This would take much longer, but would be safer so we went that route.

1. Make sure we stop all search crawls. This is important. Not pause but completely stop the search crawls. Let the running crawls complete and remove the schedule for all future crawls. If we do not do this, we take the risk of corrupting our search indexes.
2. Create the new content databses
3. Run stsadm -o preparetomove on the content db to be split
4. Create a sites.xml using stsadm -o enumsitecollections on the source content database
5. split up the sites.xml into manageable chunks containing the site colllections that we which to split out
6. run stsadm -o mergecontent dbs on the source and destination content databases using the site.xml files created in step 5 to move the site collections from source to destination database to the destination content databases
7. run stsadm -o databaserepair command on the source and destination databses to remove any orphan records - we had none
8. test

we moved approximately 150 GB of data from a large content database into 5 diffenet new content databases. It took us approximately 18 hours including testing. After the maintennance, we improved page response times for the site collections. We also reduced app pool recycles for our web applications due to processes hitting their virtual memory limits. These almost seemed to dissapear after the maintennance. Overall we were very happy with the results.
Moving a content db from one server to another:
We had multiple large content databases on one server and we wanted to balance it out by moving a large content database from one server to another in the cluster.

1. Run stsadm -o preparetomove on the content db to move
2. detach the content db by running stsadm -o deletecontentdb
3. using sql management studio, detach the content database from the server instance
4. move the databse files from the source server to the destination server
5. using management studio, re-attach the content database on the new sql server
6. add the content database by ising stsadm -o addcontentdb
7. Test

that was pretty much it. After our maintennance, we started our search crawls and reset the schedule. balancing out the databases also increased performance on our web applications.

Configuring BLOB storage in SharePoint2010

With Sharepoint 2010, the Remote Blob Storage (RBS) functionality, which allows putting documents into the database filesystem instead of the database itself, came into focus again. To make that happen each content database is located in a specific section of the file system where all the documents are stored. This documents are none the less managed by Sharepoint, a database is mandatory even if the documents are stored as BLOB because metadata is written exclusively into databases.

The following installation routines and steps to activate RBS are based on Technet and the blogs of Jie Li and Todd Klindts.

All the following installations have been done on Microsoft Windows Server 2008 R2 and Microsoft SQL Server 2008 R2 as there is no support for RBS on Microsoft SQL Server 2005.

First of all we have to activate FILESTREAM on the SQL instance that you want to put to the BLOB.

1. Connect to SQL Server
   Start –> All Programs –> Microsoft SQL Server 2008 R2 –> Configuration Tools –> SQL Server Configurations Manager
2. In the Services list, click “SQL Server Services”
3. Choose your SQL instance (here “SQL Server (MSSQLSERVER)”) and right click Properties.
4. Switch to the FILESTREAM tab and check all the available checkboxes
5. Click Apply –> OK
   
6. Now start SQL Server Management Studio
   Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio
7. Open a query windows and start the following SQL statement
   For easier reference, just copy the text below

   ---

   EXEC sp_configure filestream_access_level, 2
   RECONFIGURE

   ---

This was the first step, FILESTREAM is now successfully activated.
All further steps requires SharePoint to be installed properly and that a WebApplication has already been created. The Content Database in this case I created by Powershell:

1. Connect to a Front End Server Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Management Shell Create a Content Database
   For easier reference, just copy the text below

   ---

   New-SPContentDatabase –name WSS_Content_Blob_001 –WebApplication http://sp2010 –MaxSiteCount 1 –WarningSiteCount 0

   ---

Now the new content database (in this case “WSS_Content_Blob_001”) has to be prepared for use with FILESTREAM.

1. Connect to your SQL Server
   Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio

Open a query and execute the statement below. Replace “C:\Blobstore“ by your storage-path. The directory must not exist when executing the statement, otherwise an error will be given. For easier reference, just copy the text below

---

use [WSS_Content_Blob_001]


if not exists (select * from sys.symmetric_keys where name = N'##MS_DatabaseMasterKey##')create master key encryption by password = N'Admin Key Password !2#4'

---

use [WSS_Content_Blob_001]
if not exists (select groupname from sysfilegroups where groupname=N'RBSFilestreamProvider')alter database [WSS_Content_Blob_001]  add filegroup RBSFilestreamProvider contains filestream

---

use [WSS_Content_Blob_001]
alter database [WSS_Content_Blob_001] add file (name = RBSFilestreamFile, filename = 'c:\Blob_001') to filegroup RBSFilestreamProvider

---

Now the direcory for the Blobstore has been created in “C:\Blob_001”
Next you have to download the EXE for RBS, and it has to be copied to each Web Frontend Server. During all the following steps mind checking the log files for errors.

1. Connect to the Web Front End hosting the Central Admin Console
2. Open a Command Prompt (IMPORTANT -> run with elevated permissions)
   
3. Change to the directory containing the previously downloaded RBS_X64.exe
4. Delete or rename a already existing „rbs_install_log.txt“ if applicable.
5. Run the follwoing command, replace DBNAME with your content database and DBINSTANCE with your SQL instance. Mind that this command only works once, if you want to configure a second database, chose the option “Configure additional database” (see below).

   ---

   msiexec /qn /lvx* rbs_install_log.txt /i RBS_X64.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="WSS_Content_Blob_001" DBINSTANCE="DC" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1

   ---

6. After this process has completed (it may take a minute or two, the log reads “Verbose Logging stopped”), check the “rbs_install_log.txt” if it contains the following line of text (it should be approximately 21 lines before the end of the file:
   

   ---

   "Product: SQL Remote Blob Storage -- Configuration completed successfully"

   ---

   
   If that is not the case you have an issue. Check the following:
   - Are you in the right directory
   - Did you make a typo
   - Did you run the prompt with elevated privileges
7. If you have more than one WFE in your farm, you now have to change to the other servers and run the following command:
   For easier reference, just copy the text below
   

   ---

   msiexec /qn /lvx* rbs_install_log.txt /i RBS_X64.msi DBNAME="WSS_Content_Blob_001" DBINSTANCE="DC" ADDLOCAL="Client,Docs,Maintainer, ,FilestreamClient,FilestreamServer"
   

   ---

8. Check the “rbs_install_log.txt” if it contains the following line of text (it should be approximately 21 lines before the end of the file:
   

   ---

   "Product: SQL Remote Blob Storage -- Configuration completed successfully"
   

   ---

9. Execute all steps from step 7 on every additional WFE. This is mandatory, otherwise problems might occur.

The script has created a few tables in the database, check if they are existing:

1. Connect to SQL Server
   Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio
2. Execute the following query
   For easier reference, just copy the text below
   

   ---

   use WSS_Content_Blob_001
   select * from dbo.sysobjects
   where name like ‘rbs%’
   

   ---

The result should show the RBS tables. This may take a while.
As one last step you have to tell Sharepoint that the content database uses RBS. To do that you have to execute the following command:

1. Connect to WFE
   Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Management Shell
2. Execute the following commands in sequence:
   For easier reference, just copy the text below
   

   ---

   $cdb = Get-SPContentDatabase WSS_Content_Blob_001

   ---

   $rbss = $cdb.RemoteBlobStorageSettings

   ---

   $rbss.Installed()

   ---

   $rbss.Enable()

   ---

   $rbss.SetActiveProviderName($rbss.GetProviderNames()[0])
   

   ---

   $rbss

   ---

Since all has been prepared we can check the functionality. Just create a site collection and make sure the content database used is “WSS_Content_Blob_001”. (or whatever you chose during install).

1. Connect to WFE
   Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Central Administration
2. Application Management – Manage Content Databases
3. Choose the applicable Web Application
4. Configure the Content Database to put the next site collection to “WSS_Content_Blob_001”
   – If you have multiple databases, set “Maximum Number of Site Collections” to the current value
   – “WSS_Content_Blob_001” should not contain any site collections
5. Go back to the main site of  Central Administration
6. Application Management – Create Site Collection
   - Enter all the required data
   - OK
7. As soon as the site collection creation is finished, all newly uploaded documents should be created in the filesystem.

Notice:

Documents below 100 kB will not be put to the file system but will be stored in the database.

Configure additional content databases:

If you want to configure more than one content database for RBS, all the steps above have to be executed. The only difference is the command in step 5. This one dies not work, and no RBS tables are created. Therefore use the command below:

---

msiexec /qn /i rbs.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME=WSS_Content_Blob_002 FILESTREAMSTORENAME=FilestreamProvider_1 ADDLOCAL=EnableRBS,FilestreamRunScript DBINSTANCE=CD

 SharePoint 2010 Vs. SharePoint 2013 limitations

Limit Name	SharePoint 2010 Maximum Value	SharePoint 2013 Maximum Value
Web application limits
Web application	Not Published	20 per farm
Content database	300 per Web application	300 per Web application
Zone	5 per Web application	5 per Web application
Managed path	20 per Web application	20 per Web application
Solution cache size	300 MB per Web application	300 MB per Web application
Site collection	250,000 per Web application	250,000 per Web application
Web server and application server limits
Application pools	10 per Web server	10 per Web server
Content database limits
Number of content databases	300 per Web application	500 per farm
Content database size (general usage scenarios)	200 GB per content database	200 GB per content database
Content database size (all usage scenarios)	4 TB per content database	4 TB per content database
Content database size (document archive scenario)	No explicit content database limit	No explicit content database limit
Content database items	60 million items including documents and list items	60 million items including documents and list items
Site collections per content database	2,000 recommended 5,000 maximum	2,000 recommended 5,000 maximum
MySites per content database	Not Published	5,000 per content database
Remote BLOB Storage (RBS) storage subsystem on Network Attached Storage (NAS)	Time to first byte of any response from the NAS cannot exceed 20 milliseconds	Time to first byte of any response from the NAS cannot exceed 20 milliseconds
Site collection limits
Site collection	Not Published	2,000,000 per farm
Web site	250,000 per site collection	250,000 per site collection
MySites per farm	Not Published	500,000 per farm
Site collection size	Maximum size of the content database	Maximum size of the content database
Number of device channels per publishing site collection	Not Available in SharePoint 2010	10
List and library limits
List row size	8,000 bytes per row	8,000 bytes per row
File size	2 GB	2 GB
Documents	30,000,000 per library	30,000,000 per library
Major versions	400,000	400,000
Minor versions	Not Published	511
Items	30,000,000 per list	30,000,000 per list
Rows size limit	6 table rows internal to the database used for a list or library item	6 table rows internal to the database used for a list or library item
Bulk operations	100 items per bulk operation	100 items per bulk operation
List view lookup threshold	8 join operations per query	8 join operations per query
List view threshold	5,000	5,000
List view threshold for auditors and administrators	20,000	20,000
Subsite	2,000 per site view	2,000 per site view
Coauthoring in Word and PowerPoint for .docx, .pptx and .ppsx files	10 concurrent editors per document	10 concurrent editors per document
Security scope	1,000 per list	1,000 per list
Column limits
Single line of text	276	276
Multiple Lines of Text	192	192
Choice	276	276
Number	72	72
Currency	72	72
Date and Time	48	48
Lookup	96	96
Yes / No	96	96
Person or group	96	96
Hyperlink or picture	138	138
Calculated	48	48
GUID	6	6
Int	96	96
Managed metadata	94	94
Page limits
Web parts	25 per wiki or Web part page	25 per wiki or Web part page
Security limits
Number of SharePoint groups a user can belong to	5,000	5,000
Users in a site collection	2 million per site collection	2 million per site collection
Active Directory Principles/Users in a SharePoint group	5,000 per SharePoint group	5,000 per SharePoint group
SharePoint groups	10,000 per site collection	10,000 per site collection
Security principal: size of the Security Scope	5,000 per Access Control List (ACL)	5,000 per Access Control List (ACL)
Search limits
Search service applications	20 per farm	20 per farm
Crawl databases	10 crawl databases per search service application 25 million items per crawl database	5 crawl databases per search service application
Crawl components	16 per search service application	2 per search service application
Index components	Not Published	60 per Search service application
Index partitions	20 per search service application 128 total	20 per search service application
Index replicas	Not Available in SharePoint 2010	3 per index partition
Indexed items	100 million per search service application; 10 million per index partition	100 million per search service application; 10 million per index partition
Crawl log entries	100 million per search application	100 million per search application
Property databases	10 per search service application;128 total	10 per search service application;128 total
Link database	Not Available in SharePoint 2010	Two per Search service application
Query processing components	128 per search application 64/(total crawl components) per server	1 per server computer
Content processing components	Not Published	One per server computer
Scope rules	100 scope rules per scope; 600 total per search service application	100 scope rules per scope; 600 total per search service application
Scopes	200 site scopes and 200 shared scopes per search service application	200 site scopes and 200 shared scopes per search service application
Display groups	25 per site	25 per site
Alerts	1,000,000 per search application (seems like a mistake)	100,000 per search application
Content sources	50 per search service application	50 per search service application
Start addresses	100 per content source	100 per content source
Concurrent crawls	20 per search application	20 per search application
Crawled properties	500,000 per search application	500,000 per search application
Crawl impact rule	100	no limit
Crawl rules	100 per search service application	no limit
Managed properties	100,000 per search service application	50,000 per search service application
Values per managed property	Not Published	100
Indexed managed property size	Not Published	512 KB per searchable/queryable managed property
Managed property mappings	100 per managed property	100 per managed property
Retrievable managed property size	Not Published	16 KB per managed property
Sortable and refinable managed property size	Not Published	16 KB per managed property
URL removals	100 removals per operation	100 removals per operation
Authoritative pages	1 top level and minimal second and third level pages per search service application	1 top level and minimal second and third level pages per search service application
Keywords	200 per site collection	200 per site collection
Metadata properties recognized	10,000 per item crawled	10,000 per item crawled
Analytics processing components	Not Available in SharePoint 2010	6 per Search service application
Analytics reporting database	Not Available in SharePoint 2010	Four per Search service application
Maximum eDiscovery KeywordQuery text length	Not Available in SharePoint 2010	16 KB
Maximum KeywordQuery text length	Not Available in SharePoint 2010	4 KB
Maximum length of eDiscovery KeywordQuery text at Search service application level	Not Available in SharePoint 2010	20 KB
Maximum length of KeywordQuery text at Search service application level	Not Available in SharePoint 2010	20 KB
Maximum size of documents pulled down by crawler	Not Available in SharePoint 2010	64 MB (3 MB for Excel documents)
Navigable results from search	Not Available in SharePoint 2010	100,000 per query request per Search service application
Number of entries in a custom entity extraction dictionary	Not Available in SharePoint 2010	1 million
Number of entries in a custom search dictionary	Not Available in SharePoint 2010	5,000 terms per tenant
Number of entries in a thesaurus	Not Available in SharePoint 2010	1 million
Ranking models	Not Available in SharePoint 2010	1,000 per tenant
Results removal	Not Available in SharePoint 2010	No limit
Term size	Not Available in SharePoint 2010	300 characters
Unique terms in the index	Not Available in SharePoint 2010	2^31 (>2 billion terms)
Unique contexts used for ranking	Not Available in SharePoint 2010	15 unique contexts per rank model
User defined full text indexes	Not Available in SharePoint 2010	10
User Profile Service limits
User profiles	2,000,000 per service application	2,000,000 per service application
Social tags, notes and ratings	500,000,000 per social database	500,000,000 per social database
Maximum Number of Users Imported Via FIM	Not Published	1000000
Content deployment limits
Content deployment jobs running on different paths	20	20
Blog limits
Blog posts	5,000 per site	5,000 per site
Comments	1,000 per post	1,000 per post
Business Connectivity Services limits
ECT (in-memory)	5,000 per Web server (per tenant)	5,000 per Web server (per tenant)
External system connections	500 per Web server	500 per Web server
Database items returned per request	2,000 per database connector	2,000 per database connector
Response latency	Not Published	600 seconds
Service response size	Not Published	150,000,000 bytes
Filter Descriptor (in-store)	Not Published	200 per ECT method
ECT Identifier (in-store)	Not Published	20 per ECT
Database Item	Not Published	1,000,000 per request
Workflow limits
Workflow postpone threshold	15	15
Workflow timer batch size	100	100
Workflow associations	Not Published	100 per list
List items or documents that can be bulk created or uploaded to start workflow instances	Not Published	5,000 items
Published workflow definitions per site	Not Published	1,000 per site
Total workflow associations per site	Not Published	1,799 per site
Maximum workflow definition (xaml) size	Not Published	5,120 KB
Maximum depth of a workflow sub-step in xaml (workflow complexity)	Not Published	121 levels
Workflow instance activations per second per web server	Not Published	6 per second
Rest calls from SharePoint workflow per second per web server	Not Published	60 per second
Workflow variable value size	Not Published	256 KB
Maximum list size for workflow lookups to non-indexed fields	Not Published	5,000 items per list view
Maximum list size for auto-start workflow associations	Not Published	10 million items per list
Managed Metadata term store (database) limits
Maximum number of levels of nested terms in a term store	7	7
Maximum number of term sets in a term store	1,000	1,000
Maximum number of terms in a term set	30,000	30,000
Total number of items in a term store	1,000,000	1,000,000
Number of Variation Labels	Not Available in SharePoint 2010	209 per term store
Visio Services limits
File size of Visio Web drawings	50 MB	50 MB
Visio Web drawing recalculation time-out	120 seconds	120 seconds
Visio Services minimum cache age (data connected diagrams)	Minimum cache age: 0 to 24hrs	Minimum cache age: 0 to 24hrs
Visio Services maximum cache age (non-data connected diagrams)	Maximum cache age: 0 to 24hrs	Maximum cache age: 0 to 24hrs
SharePoint Web Analytics service limits
SharePoint entities	30,000 per farm when Web Analytics is enabled	Deprecated
PerformancePoint Services limits
Cells	1,000,000 per query on Excel Services data source	1,000,000 per query on Excel Services data source
Columns and rows	15 columns by 60,000 rows	15 columns by 60,000 rows
Query on a SharePoint list	15 columns by 5,000 rows	15 columns by 5,000 rows
Query on a SQL Server data source	15 columns by 20,000 rows	15 columns by 20,000 rows
Word Automation Services limits
Input file Size	512 MB	512 MB
Frequency with which to start conversions (minutes)	1 minute (recommended)  15 minutes (default) 59 minutes (boundary)	1 minute (recommended)  15 minutes (default) 59 minutes (boundary)
Number of conversions to start per conversion process	For PDF/XPS output formats: 30 x M For all other output formats: 72 x M Where M is the value of Frequency with which to start conversions (minutes)	For PDF/XPS output formats: 30 x M For all other output formats: 72 x M Where M is the value of Frequency with which to start conversions (minutes)
Conversion job size	100,000 conversion items	100,000 conversion items
Total active conversion processes	N-1, where N is the number of cores on each application server	N-1, where N is the number of cores on each application server
Word Automation Services database size	2 million conversion items	2 million conversion items
SharePoint Workspace limits (Renamed to Office Live Workspace)
Office Live Workspace list items	30,000 items per list	30,000 items per list
Office Live Workspace documents	1,800 documents limit in SharePoint Workspace	1,800 documents in Office Live Workspace
OneNote limits
Number of Sections and Section Groups in a OneNote Notebook (on SharePoint)	See limit for "Documents" in List and library limits	See limit for "Documents" in List and library limits
Maximum size of a section	See limit for "File size" in List and library limits	See limit for "File size" in List and library limits
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	See limit for "File size" in List and library limits
Maximum size of all images, embedded files, and XPS printouts in a single OneNote page.	Default limit is double the "File size" limit.	Default limit is double the "File size" limit.
Merge operations	One per CPU core per Web server	One per CPU core per Web server
Excel Services limits
Maximum workbook size	Not Published	10 MB
Machine Translation Service limits
Input file size for binary files	Not Available in SharePoint 2010	524,288 KB per file
Input file size for text files	Not Available in SharePoint 2010	15,360 KB per file
Maximum character count for Microsoft Word Documents	Not Available in SharePoint 2010	10,000,000 per document
Total concurrent translation processes	Not Available in SharePoint 2010	5
Delay between translations	Not Available in SharePoint 2010	59 minutes
Number of translations per translation process	Not Available in SharePoint 2010	1,000 per process
Maximum concurrent translation requests	Not Available in SharePoint 2010	300
Files per translation job	Not Available in SharePoint 2010	100,000 files
Machine Translation Service database size	Not Available in SharePoint 2010	1,000,000 files
Office Web Application Service limits
Cache size	100 GB	100 GB
Renders	One per document per second per CPU core per application server (maximum eight cores)	One per document per second per CPU core per application server (maximum eight cores)
OneNote concurrent merge operations	Not Available in SharePoint 2010	8 per document
Project Server limits
End of project time	Date: 12/31/2049	Date: 12/31/2049
Deliverables per project plan	1,500 deliverables	1,500 deliverables
Number of fields in a view	256	256
Number of clauses in a filter for a view	50	50
SharePoint Apps limits
Maximum Access app size on Office 365/SQL Azure	Not Available in SharePoint 2010	100 Mb
Apps displayed in Manage Licenses page	Not Available in SharePoint 2010	2,000
Number of app licenses per tenant	Not Available in SharePoint 2010	1,000,000
Number of apps displayed in the Add an App page	Not Available in SharePoint 2010	240
Number of managers per app license	Not Available in SharePoint 2010	30
Number of app licenses assigned to a user viewable by that user	Not Available in SharePoint 2010	2,000
Number of apps in the corporate catalog viewable by a single user	Not Available in SharePoint 2010	500
Miscellaneous limits
Number of User agent substrings per device channel	Not Available in SharePoint 2010	150
Number of SharePoint sources per EDiscovery case	Not Available in SharePoint 2010	100
Number of Exchange sources (mailboxes) per EDiscovery case	Not Available in SharePoint 2010	1500
Maximum size of EDiscovery Query	Not Available in SharePoint 2010	16K characters or 500 keywords
Number of nodes in managed navigation term set	Not Available in SharePoint 2010	2000