Crawling has to do with making the contents of pages/uploaded documents available in SharePoint's search. the administrator can decide the content to be included in the search. Along with it, it also provides way to decide the order of results in search. Like according to the number of hits, the search order changes automatically.
SharePoint Console allows you to crawl and index items from a Microsoft Office SharePoint Server (MOSS) or Windows SharePoint Services (WSS) site or site collection. It also allows you to crawl a list of MOSS or WSS sites specified by an RSS feed. Crawling SharePoint items into your portal requires the configuration of a content source, a crawler, and a job. Depending on your needs, more than one content source and/or crawlers may need to be created.
A SharePoint content source is configured with authentication information and default click through behavior. The authentication information is the Windows credentials necessary to access the desired SharePoint site or site collection. If multiple sites are accessible with the same authentication credentials, only one SharePoint content source is required. If sites require different authenticating credentials, create a SharePoint content source for each set of credentials.
Each SharePoint content source can have one or more SharePoint crawlers associated with it. A SharePoint crawler describes which SharePoint site or site collection is to be crawled, what to crawl on that SharePoint site, and where the crawled items should be put. Note that the crawler does not import the SharePoint items themselves, but rather indexes them within the portal.
but in case a and b both are different datatype then also a.Equals(b) can be used to compare
but incase of == we cant event compaile the code if a and b are different data type
Example :
int a=0;
string b="o";
if(a.Equals(b))
{
//do some thing
}
//above code will compile successfully and internally the int b will convert to object type and compare
if(a==b)
{
//do some thing
}
//above code will give you the compilation error
2. by using == we cant compare two object
but Equals method will able to compare both the object internally
Note: We are not customizing the existing (default) delegate control but we are creating our own control loading onto the SharePoint site.
A content source is a set of options that you can use to specify what type of content is crawled, what URLs to crawl, and how deep and when to crawl. You must create at least one content source before a crawl can occur.
A search scope defines a subset of information in the search index. Users can select a search scope when performing a search.
Federated locations provide information that exists outside of your internal network to your end-users.
Enhances the end-user search experience by mapping crawled properties to managed properties. Managed properties show up in search results and help users perform more successful queries.
Collects information about user search queries and search results that users select on their computers to improve the relevancy of search results and to improve query suggestions.
The crawl component requires access to content using NTLM authentication.
Service applications in SharePoint 2010 are a set of services that can possibly be shared across Web applications. Some of these services may or may not be shared across the SharePoint 2010 farm. The reason these applications are shared is the overall reduction of resources required to supply the functionality these services cultivate.
Any of the below are acceptable answers:
Just provides a logical grouping of services that are scoped to a particular Web Application.
They are provisioned as a single Internet Information Services (IIS) Web site.
A virtual entity is used that is referred to as a proxy, due to label in PowerShell.
The three most popular designs are single farms with either a single service application group or multiple service application groups, or Enterprise services farms.
Depending on the environment requirements, a specialized farm can also be used in order to deploy specific services tailored to the organizational requirements which can aid in scaling out and conservation of resources.
Allows configuring and managing User profile properties, Audiences, Profile synchronization settings, organization browsing and management settings, and My Site settings.
Aggregates properties from diverse identity content sources together to create unified and consistent profiles across an organization, used throughout the SharePoint environment.
Allows sharing, securing, managing, and using Excel 2010 workbooks in a SharePoint Server Web site or document library. Excel Services consists of the Excel Calculation Services (ECS), Microsoft Excel Web Access (EWA), and Excel Web Services (EWS) components.
Allows users to monitor and analyze a business by building dashboards, scorecards, and key performance indicators (KPIs).
Allows users to share and view Microsoft Visio Web drawings. The service also enables data-connected Microsoft Visio 2010 Web drawings to be refreshed and updated from various data sources.
Allows users to edit, update, and create linked Microsoft Access 2010 databases that can be viewed and manipulated by using an internet browser, the Access client, or a linked HTML page.
A secure database for storing credentials that are associated with application IDs
Content deployment enables you to copy content from a source site collection to a destination site collection.
Multiple front-end web servers (WFE's) can be deployed and correlated through Windows NLB or anything approach. Application servers can be deployed into the farm for a variety of purposes, depending on organizational requirements. Databases can be clustered or mirrored, again depending on requirements and environment.
Clustering provides a failover scenario whereby one or more nodes can be swapped as active depending on whether a node goes down. In mirroring, transactions are sent directly from a principal database and server to a mirror database to establish essentially a replica of the database.
Governance is the set of policies, roles, responsibilities, and processes that guide, direct, and control how an organization's business divisions and IT teams cooperate to achieve business goals.
Any of the below are acceptable answers. There are some others but these are the major ones that I generally look for from a candidate:
Diagnostic logging captures data about the state of the system, whereas health and usage data collection uses specific timer jobs to perform monitoring tasks, collecting information about:
- Performance Counter Fata
- Event Log Data
- Timer Service Data
- Metrics For Site Collections and Sites
- Search Usage Data
Workflows created by using Microsoft SharePoint Designer 2010, the default setting enables deployment of declarative workflows. Yes, however you do not give non-authorized users access to the site. The e-mail message and attachments sent from notifications might contain sensitive information
The browser sends a DAV packet to IIS asking to perform a document check in. PKMDASL.DLL, an ISAPI DLL, parses the packet and sees that it has the proprietary INVOKE command. Because of the existence of this command, the packet is passed off to msdmserv.exe, who in turn processes the packet and uses EXOLEDB to access the WSS, perform the operation and send the results back to the user in the form of XML.
You can either try to force execute timer jobs using execadmsvcjobs command or can cancel the deployment using stsadm command
"stsadm –o cancaldeployment –id {GUID} command."
The Id here would be GUID of the timer or deployment job. You can get the Id from stsadm enumdeployment command. This will display all the deployments which are inprocess or are stuck with Error.
Differences are
1) Master pages contain controls that are shared across multiple page layouts,
such as navigation,search, or language-preference for multilingual sites.
Page layouts contain field controls and Web Parts.
2) Page layouts can be used by all page instances that are based on that
page layout.Master pages can be used by all page instances in a site.
2. Site definition supports feature stapling, but for site template additional features must be activated in gallery.
3. Site definitions are stored in hard disk, but site templates are stored in content DB.
4. Site definition can provision multiple webs, but site templates for single web only.
5. Creating site definition is relatively complex then site template creation.
Features: It helps sites to reuse functionality from one site to other sites without requiring to copy and paste XML. It is also an instance of Feature Definition.
Solutions: It helps to package Features in a cabinet (.cab) file along with meta data.
Feature Definition: It hides feature manifest contained in a feature directory and are installed at farm level.
Operating system: microsoft windows server 2008 or microsoft windows server 2008 r2, but for development purpose you can install sharepoint 2010 on windows 7 and microsoft windows vista sp1/sp2. All operating system should be 64 bit.
Database: sharepoint 2010 requires database of Microsoft sql server 2005 sp3 or Microsoft sql server 2008 or r2. Also all should be 64bit.
Application server: sharepoint 2010 requires iis7 +.
.net framework: sharepoint 2010 requires Microsoft .net framework 3.5 and sp1 is preferable
Sites: ribbon ui, sharepoint workspace, sharepoint mobile etc.
Communities: tagging, tag cloud, rating, social networking feature, my sites, blogs and wikis, my profile etc.
Content: enterprise content type, metadata and navigation, document sets, remote blog storage, audio and video content types, list enhancements etc.
Search: fast search integration, social relevance.
Insights: excel services, visio services, web analytics, sql server integration etc.
Scopes include
- Farm
- WebApplication
- Site (site collection)
- Web (site)
- installing
- uninstalling
- activated
- deactivated
- menu commands
- link commands
- page templates
- page instances
- list definitions
- list instances
- event handlers
- workflows
- feature.xml
- manifest file(elements.xml)
Common stsadm commands associated with feature are
- stsadm -o installfeature
- stsadm -o uninstallfeature
- stsadm -o activatefeature
- stsadm -o deactivatefeature.
This is designed to administer and monitor a sharepoint server farm. Here you can configure servers and servers' roles, define farm topology, and create new web applications and site collections. This basically a sharepoint site. The main features included here are: application management, monitoring, security, general application settings, system settings, backup and restore, upgrade and migration and configuration wizard.
A site collection is a logical container that holds a set of websites, hosted in a web application. If you want to publish internet or intranet web site then you need at least a web application and one site collection.
To create a new site collection we need a parent web application.
There are 5 different site templates available in sharepoint 2010, from which you can create sites. And they are:
Collaboration: it has templates for team site, blank site, document workspace, blog, group work site etc.
Meetings: it has templates for basic meeting workspace, blank meeting workspace, decision meeting workspace, social meeting workspace, and multipage meeting workspace.
enterprise: it has templates for document center, records center,powerpoint broadcast site, business intelligence center, enterprise search center, my site host, basic search center, and fast search center.
Publishing: it has templates for publishing portal and enterprise wiki custom: here you can define your own custom templates.
Everything is stored in SharePoint in form of list. They are similar to database. Lists have item, fields and views. Items are like a row in a table. Fields are like columns in a database table. Views display information from list.
Form library forms store data in XML files in a SharePoint form library. This means they are more flexible and you can do more with them. For example, they can be configured to save drafts and submit to different locations. However, they are more complex to work with and require more decisions to be made during configuration.
library is used to store the document and lists are the container of similar items in form of rows and columns. In library you can create core document like word, excel, powerpoint. But in list you can not create document, instead of that you can attach document in a particular list.
Some of the additions in workflow model are :
1. Sharepoint 2010 workflows are build upon the the workflow engine provide .net framework 3.5.
2. In addition to the sharepoint lists we can now create workflows for sharepoint sites as well.
3. Sharepoint designer 2010 also has a new graphical workflow designer for designing workflows and deploying them directly to sharepoint.
4. Another improvement in sharepoint designer 2010 is that it now allows you to edit the out-of-the-box workflows that come with sharepoint.
* policy
* usercode
* webclients
* webservices
A SharePoint solution file is essentially a .cabinet file with all a developers custom componets suffixed with a .wsp extension that aids in deployment. The big difference with SharePoint solution files is is that a solution:
allows deployment to all WFE's in a farm
is highly manageable from the interface allowing deployment, retraction, and versioning
Can package all types of assets like site definitions, feature definitions (and associated components), Webparts, etc.
Can provide Code Access Security provisioning to avoid GAC deployments
And much more..
A method activity is one that performs an action, such as creating or updating a task. An event activity is one that runs in response to an action occurring.
1. Visual Webparts - Allows you to Drag and Drop the controls from the Toolbox to WebPart Design surface. You can of course write your custom code in the code file. You can also package and deploy your webparts directly to Sharepoint from VS by pressing Clt+F5. Visual studio 2010 also provides you with three different views for developing webparts. The views are split view, design view and Source view(as we have in SharePoint Designer 2007).
2. ASP.Net WebParts - Where a developer can build up User Interface and logic in a class file. You do not have designer for drag and drop of controls. This webpart inherits from standard ASP.Net webpart. For Deployment we can again use ctrl+f5 to deploy this webpart.
1.Visual Web Part project template.
2. List defination template.
3. Content Type template.
4. Empty Project template.
5. Event Receiver template.
6. some workflow template.
7. the Site Definition template etc.
1. WebParts.
2. Event Receivers.
3. List Definations.
4. Workflows.
A .ddf file is a data directive file and is used when building the SharePoint solution bundle specifying the source files and their destination locations. The important thing for someone to understand is that the .ddf file will be passed as a parameter to the MAKECAB utility to orchestrate construction of the SharePoint solution file.
1. Restrict Delete
2. Cascade Delete
These options define a relationship between the Look-up list and the list containing the look-up Column.
The top-level elements in the Ribbon are tabs. Each tab organizes a set of groups (like Edit.Browse) and contains a set of controls. The controls inside the groups include buttons, drop-down menus, check boxes, combo boxes, split buttons, and galleries. In short, the users now can see the options like checkOut,Check In, Edit Page,Publish Page, delete page under edit tab, on the top of the Page itself.
A content type is a flexible and reusable wss type definition (or we can a template) that defines the columns and behavior for an item in a list or a document in a document library. For example, you can create a content type for a leave approval document with a unique set of columns, an event handler, and its own document template and attach it with document library/libraries.
You can create four different types of input forms including
1. An association form
2. An initiation form
3. A modification form
4. A task edits form.
The webpartmanager sealed class is responsible for managing everything occurring on a webpart page, such as the webparts (controls), events, and misc. Functionality that will occur in webpartzones. For example, the webpartmanager is responsible for the functionality that is provided when you are working with moving a webpart from webpartzone to webpartzone. It is known as the "the central class of the web part control set."
If your code modifies windows sharepoint services data in some way, you may need to allow unsafe updates on the web site, without requiring a security validation. You can do by setting the allowunsafeupdates property.
What does runwithelevatedprivileges do?
There are certain object model calls models that require site-administration privileges. To bypass access-denied error, we use runwithelevatedprivileges property when request is initiated by a nonprivileged user. We can successfully make calls into the object model by calling the runwithelevatedprivileges method provided by the spsecurity class
Checks whether the specified login name belongs to a valid user of the web site, and if the login name does not already exist, adds it to the web site.
E.g spuser usr = myweb.ensureuser("hitenders");
The spsite object represents a collection of sites (site collection [a top level site and all its subsites]). The spweb object represents an instance sharepoint web, and spweb object contains things like the actual content. A spsite object contains the various subsites and the information regarding them.
The spwebapplication objects represents a sharepoint web application, which essentially is an iis virtual server. Using the class you can instigate high level operations, such as getting all the features of an entire web application instance, or doing high level creation operations like creating new web applications through code.
Would you use spwebapplication to get information like the smtp address of the sharepoint site?
Yes, since this is a web application level setting. You would iterate through each spwebapplication in the spwebapplication collection, and then use the appropriate property calls (outboundmailserviceinstance) in order to return settings regarding the mail service such as the smtp address.
In order to retrieve list items from a sharepoint list through web services, you should use the lists.asmx web service by establishing a web reference in visual studio. The lists.asmx exposes the getlistitems method, which will allow the return of the full content of the list in an xml node. It will take parameters like the guid of the name of the list you are querying against, the guid of the view you are going to query, etc.
What is caml, and why would you use it?
Caml stands for collaborative application markup language. Caml is an xml based language which provides data constructs that build up the sharepoint fields, view, and is used for table definition during site provisioning. Caml is responsible for rending data and the resulting html that is output to the user in sharepoint. Caml can be used for a variety of circumstances, overall is used to query, build and customize sharepoint based sites. A general use would be building a caml query in a sharepoint webpart in order to retrieve values from a sharepoint list.
What are event receivers?
Event receivers are classes that inherit from the spitemeventreciever or splisteventreciever base class (both of which derive out of the abstract base class speventrecieverbase), and provide the option of responding to events as they occur within sharepoint, such as adding an item or deleting an item
Since event receivers respond to events, you could use a receiver for something as simple as canceling an action, such as deleting a document library by using the cancel property. This would essentially prevent users from deleting any documents if you wanted to maintain retention of stored data.
Sharepoint solution files can add in order to handle code access security deployment issues. This is done in the element in the sharepoint solution manifest.xml, which makes it easier to get assemblies the appropriate permissions in order to operate in the bin directory of the web application.
If I wanted to not allow people to delete documents from a document library, how would I go about it?
You would on the ItemDeleting event set: properties.Cancel= true.
An asynchronous event occurs after an action has taken place, and a synchronous event occurs before an action has take place. For example, an asynchronous event is ItemAdded, and its sister synchronous event is ItemAdding
Microsoft Office SharePoint Server 2007 for Internet sites and Microsoft Office SharePoint Server 2007 have identical feature functionality. While the feature functionality is similar, the usage rights are different. If you are creating an Internet, or Extranet, facing website, it is recommended that you use Microsoft Office SharePoint Server 2007 for Internet sites which does not require the purchase client access licenses. Websites hosted using an "Internet sites" edition can only be used for Internet facing websites and all content, information, and applications must be accessible to non-employees. Websites hosted using an "Internet sites" edition cannot be accessed by employees creating, sharing, or collaborating on content which is solely for internal use only, such as an Intranet Portal scenario. See the previous section on licensing for more information on the usage scenarios.
SharePoint Portal Services (SPS) has MUCH better document management. It has check-in, check-out, versioning, approval, publishing, subscriptions, categories, etc. STS does not have these features, or they are very scaled back. SharePoint Portal Services (SPS) has a better search engine, and can crawl multiple content sources. STS cannot. STS is easier to manage and much better for a team environment where there is not much Document Management going on. SPS is better for an organization, or where Document Management is crucial.
Web Parts can be connected by Modifying the Shared Part and providing the connection with the correct fields to share.
The file extension that applies to site templates.
Via Web Parts available at the Microsoft Web Component Directory. Oh yeah and Active X Controls.
The file extension that applies to SharePoint sites that have been backed up.
Personal views are specific to a user while Shared View is common across all users.
Yes. Microsoft recommends using the following browsers for viewing and editing Windows SharePoint Services sites: Microsoft Internet Explorer 5.01 with Service Pack 2, Microsoft Internet Explorer 5.5 with Service Pack 2, Internet Explorer 6, Netscape Navigator 6.2 or later.
"In Word 2003, you can compare documents side by side. Open two documents. Then, from the Window menu of one of them, select the Compare Side By Side command. If you have only two documents open, the command will automatically choose to compare them. If you have three or more documents open, you'll have to select which document to compare with the current file. A floating toolbar with two buttons will open. If the button on the left is selected, Word will scroll both documents at the same time. Press the button on the right side of the toolbar to return to where the cursor was located when you started comparing."
Moss stands for Microsoft office share point server. Moss is a portal based platform for complete management of documents & web services. It is a platform for creation of customized web based applications & portals like blogs, wiki etc. Moss provides security features and can be configured to return separate content based on the fact that the user has logged on using internet, intranet or extranet.
Moss provides extra features as compared with wss
consolidation of all the team sites within the organization
enterprise search : search through different sources within the organization with one
interface (portals, mail, erp, crm ...)
Central personnel data base with extended search capabilities, linked (or not) to
internal personnel management.
Business data catalog (bdc): default link to external systems (e.g. Crm/erp)
report center : central management of all reports and data connections.
Excel services : provides excel features in the web browser.
Creation of web-based e-forms, full web-browser access.
stsadm command is used to perform all administrative work. For e.g. Backup, restore, installing feature, adding web part to site etc.
Ans backup command:
stsadm -o backup -url http://moss:4002/ -filename c:\bkupsite.bak
to restore :
stsadm -o restore -url http://moss:4004/ -filename c:\bkupsite.bak
What is a farm?
Site is a collection of web pages which is used to store information in organised way.
Site stores list of documents, discussion, events, task and many other types of information.
Site provides controlled access to share information among user. I.e. only authorize users are allowed to access shared information.
What are web parts in sharepoint?
Webparts are smallest component in sharepoint. Web parts are used to give more functionality to the page.
various web parts available in sharepoint web part gallery are:
data view web part, content editor web part, form web part, excel web access web part, image web part etc.
What is bdc?
In bdc you can not modify data from your sharepoint list. It will be available to your site in read only.
In sharepoint 2010 it is named as bcs (business connectivity services). Bcs is two way, i.e. Data can be edit from sharepoint list as well from the back end data base.
What is a meeting workspace?
Document workspaces consist of information surrounding a single or multiple documents
An intranet (or internal network), though hosted on the web, can only be accessed by people who are members of the network. They need to have a login and password that was assigned to them when they were added to the site by the site administrator
A user can be assigned one of the following roles
readers - has read-only access to the web site.
Contributor - can add content to existing document libraries and lists.
Web designer - can create lists and document libraries and customize pages in the web site.
Administrator - has full control of the web site.
Claims
windows
forms-based authentication
Claims create a small token based on the sign-in, that contains the user's identity.
Classic authentication supports nt authentication types like kerberos, ntlm, basic, digest, and anonymous. Claims based authentication uses claims identities against a against a trusted identity provider.
Linq is a feature of the programming languages c# 3.0 and visual basic .net
linq adds, to each of the languages, a sql-like syntax and vocabulary for querying data sources.
Linq to sharepoint allows developers to use sql-like syntax to query lists and libraries in sharepoint.
Linq to sharepoint internally converts the linq query to a caml query to fetch records
advantage:
Disadvantage :
Explain types of SharePoint sites
Types of SharePoint sites:
wiki: this is usually where everyone is allowed to add/change content for a common knowledgebase.
Blog: this type of site is for posting specialized articles or information for everyone to read.
Publishing site: this site is used to approving particular content before it's published to everyone.
Document library: a site mainly used for document management purposes.
Download site: this type of site helps in monitoring the count of downloads and track them.
List or forum: the idea is to have specific people post a topic and then allow others to comment on the posts.
Survey: usually a site that's accessed by everyone for conducting a survey.
Dashboard: the idea of a dashboard is for business executives to gain information and perform reporting tasks.
2. default.master - this is used to support the 2007 user interface
3. minimal.master
4. simple.master- it is used for accessdenied.aspx, confirmation.aspx, error.aspx, login.aspx, reqacc.aspx, signout.aspx & webdeleted.aspx pages.
how can debugging share point application and timer jobs ? with steps?
steps 2:On the Debug menu, select Attach to Process
steps 3:select the Show processes from all users check box.
steps 4:select W3W.exe and OSWTIMER.exe can attach
steps 5:refresh sharepoint site point break point
A good example of an Application Page is the default Site Settings page: every site has one, and it's not customizable on a per site basis (although the contents can be different for sites).
With application pages, you can also add inline code
1. .net Managed applications – These are used when we have to create console applications or window applications, web applications which are not running inside SharePoint Contex.
2. For Silverlight applications
3. ECMAScript – It is a client object model extension for using with JavaScript or JScript. This is used for creating applications which are hosted inside SharePoint. For example, web part deployed in SharePoint site can use this JavaScript API for accessing SharePoint from browser using JavaScript.
What is Authentication and Authorization.
Once the system knows who the user is through authentication, authorization is how the system decides what the user can do.
SharePoint WebPart Base class or the ASP.NET 2.0 WebPart base class.
When inheriting from the SharePoint WebPart Base class your derived WebPart class will inherit from Microsoft.SharePoint.WebPartPages.WebPart. When inheriting from the ASP.NET 2.0 WebPart base class your derived WebPart class will inherit from System.Web.UI.WebControls.WebParts.WebPart. It is considered good practice to use the ASP.NET WebPart base class since the old base class is meant for backwards compatibility with previous version of SharePoint, however there are four exception when it is better to leverage functionality from the SharePoint WebPart base class:
Cross page connections
Connections between Web Parts that are outside of a Web Part zone
Client-side connections (Web Part Page Services Component)
Data caching infrastructure
Microsoft Office SharePoint Server 2007 | SharePoint Server 2010 |
Office client required to view and edit documents uploaded to document libraries (Download and open) | Office Web Application enables Word, PowerPoint, Excel and Visio documents, using Silverlight or HTML with JavaScript (Depending on Browser Support) |
No Co-Authoring Capability | Co-Authoring Capabilities available for Word, PowerPoint (with client software) and Excel (Available over the web) |
Lot of post backs | Fewer post backs for default actions – more Ajax usage |
No inherent support of Ajax or Silverlight | Fully supported |
Static themes. You just pick a theme and its applied across the site, no preview | You can select a theme , customize it and preview before applying it on the site |
No bookmarking, tagging or rating capability | Its all there |
Content Types scoped to site collections | New concept of having a Content Type hub which can be shared across web applications |
Media files would have to be downloaded before playing | Progress download feature available (not streaming) |
BDC used to store info in SharePoint | BCS reads data real-time (with some caching for performance) |
5 million item limit in document library | 10 million |
Views are CAML driven | Views XSLT based |
To query a list we had to use CAML | Queries via LINQ, JavaScript and Silverlight API's |
No restriction for installation | Ability to prevent people from installing SharePoint (Managed at the AD level) |
Shared Services scoped to Farm | Shared Services architecture changed to make it more flexible and ability to share across farm |
Profile synch could be done by anyone | Additional permission check for account to carry out profile synch |
Basic web Analytics | Web analytics capability enhanced |
Search results are static | Clicking on a search result affects the search results for the other searches for the same keyword |
To limit issues with rogue code that could bring down the server, CAS had to be defined /maintained for different applications. This was not easy to do and Admins used to say – no code allowed | Sandbox available that restricts the scope of code. Deployment is also easy, the code just needs to be uploaded by the site admin, no need for intervention from the SharePoint farm admin to run scripts on the server |
People with contribute access could upload .aspx pages in a document library. It was possible to restrict, however it would restrict everyone from uploading .aspx pages | People with contribute access cannot load .aspx pages |
Contributors could edit tool pane parameters | Not editable by contributors |
Explorer view on browser | Opens up Windows explorer with web dav access |
Simplistic Mobile Page OOTB | Able to create richer mobile pages using OOTB features |
Usage of outlook for offline access | SharePoint Workspace used for offline access – more capability eg. ability to synch up lists (even external content from BCS) |
Not possible to have a common document ID that is associated with a document regardless of which document library it moves into | Document ID can be defined and associated to the document regardless of where it is located(within the site collection) |
To upload a document or page, one needs to go to that appropriate site/subsite and library and upload | Content organizer moves document to appropriate libraries based on metadata rules which can be defined |
When a file with a same name is uploaded, it creates a new version | Option to have another version or append a unique ID to the document being uploaded |
Fixed layout with defined web part zones where web parts can be placed | More "Fluid" UI; ability to place web parts without having web part zones |
Retention policy allows only delete or invoke workflow by default | Multiple other options – eg send to another library etc |
EBS – to store docs out side SharePoint, possible but not easy to configure | RBS - managed by SQL |
Requires Server OS to install(32 or 64) | Can be installed on Win 7 (64 bit) and Win 2008 (64 bit) |
No field validations | Field validations available |
Workflows created in SPD or VS.Net – not possible to move a workflow developed in SPD to VS.Net | Workflows can be defined in Visio, Imported to SPD with rules added and then moved to VS.Net |
Table based layouts | Div Based layouts (better for accessability) |
1. Secure store database - the secure store service application database stores and maps credentials, such as account names and passwords. Prefixed with "secure_store_service_db_".
2. State database - the state service application database stores temporary state information for infopath forms services, the chart web part, and visio services. Prefixed with "stateservice".
3. Web analytics staging database - the staging database temporarily stores un-aggregated fact data, asset metadata, and queued batch data for the web analytics service application. Prefixed with "webanalyticsserviceapplication_stagingdb_"
5. Search service application administration database - the administration database hosts the search service application configuration and access control list (acl), and best bets for the crawl component. This database is accessed for every user and administrative action. Prefixed with "search_service_application_db_".
6. Search service application crawl database - the crawl database stores the state of the crawled data and the crawl history. Prefixed with "search_service_application_crawlstoredb_'.
7. Search service application property database - the property database stores information that is associated with the crawled data, including properties, history, and crawl queues. Prefixed with "search_service_application_propertystoredb_"
8. User profile service application profile database - the profile database stores and manages users and associated information. It also stores information about a user's social network in addition to memberships in distribution lists and sites. Prefixed with "user profile service application_profiledb_".
9. User profile service application synchronization database -the synchronization database stores configuration and staging data for use when profile data is being synchronized with directory services such as active directory.prefixed with "user profile service application_syncdb_".
10. User profile service application social tagging database - the social tagging database stores social tags and notes created by users, along with their respective urls.prefixed with "user profile service application_socialdb_".
11. Managed metadata database - the managed metadata service application database stores managed metadata and syndicated content types. Prefixed with "
managed metadata service_".
In addition to all the databases created with standard edition, enterprise addition install adds two more databases:
1. Performancepoint service application database - the performancepoint service application database stores temporary objects, persisted filter values, and user comments. Name prefix "performancepointserviceapplication_.."
2. Word automation services database - the word automation services database stores information about pending and completed document conversions.name prefix "wordautomationservices_..."