SharePoint 2010 vs. MOSS 2007

SP 2010	MOSS 2007
Look and feel
In SP 2010 look and feel perspective there will be a ribbon where we can have a look and feel like Office 2010	In MOSS 2007 there is no ribbon
Deployment of Web parts
In SharePoint 2010 deploying custom web part is pretty simple i.e. just right click on the solution and click Deploy	In MOSS 2007 you need to drag the dll either to bin or GAC
Silverlight Application
In SP 2010 we can create a Silverlight application directly from Visual Studio 2010	In MOSS 2007 we have to create a web part to host Silverlight application
Shared Database & Service Application
In SP 2010 there is no SSP but there is a concept of Service Application like BCS as one service application, Excel Services as another service application, User Profile as separate service application General idea is that you have an application for each service, rather than one application with lots of service crammed into it Own database rather than shared database in SP 2010	In MOSS 2007 we have SSP where we can work around with BI,Search Settings, User Profile Import, Excel Services, Info path In Database also we use to have separate area for SSP stuff
Easy exports/imports between the forms
In SP 2010 we can update existing information	In MOSS 2007 through we can just read the information and we can't update the existing services
Improvement in Deployment
In SP 2010 we can Deploy through Farm based and solution based solution in SP 2010	In MOSS 2007 there is no such option
Alerts
In SP 2010 it has been improved in validation and unique values. While creating column itself we have an option "Allow Duplicate values" to Yes or No	In MOSS 2007 alerts were sent only through emails but in SP 2010 users can also send alerts to mobile device as SMS message. A New property delivery channel is introduced to indicate, whether the alerts is delivered as Email or an SMS message
Improvements of events
New events for list creation and web creation	No List and web events in MOSS 2007
Getting Items from the list
In SP 2010 through object model we can fetch multiple list data by LINQ query and object model	In MOSS 2007 we can fetch only through object model
Rating
In SP 2010 we can have rating column by default	In MOSS 2007 we should install the feature that is available in codeplex to have rating
Key Word Suggestions
In SP 2010 we can have keyword suggestions	In MOSS 2007 we don’t have any keyword suggestions
Taxonomy
In SP 2010 we can create Taxonomy by using Managed Metadata service	In MOSS 2007 we don’t have taxonomy
Other Features
In SP 2010 we have Power Shell Scripting, JavaScript object model, Chart Web Parts	In MOSS 2007 we don’t have Power Shell Scripting, JavaScript object model, Chart Web Parts
Running stsadm command
In SP 2010 we have to go 14 hive path to run stsadm command	In MOSS 2007 we have to go 12 hive path to run stsadm command

Classic Authentication and Claim based authentication

What are the differences between Classic Mode Authentication and Claims based Authentication?

Classic Mode Authentication: This refers to the integrated windows authentication. We cannot configure the forms based authentication if your web application is using Classic Mode Authentication. We can convert a web application from Classic Mode Authentication to Claims Based Authentication.

However, this can only be done using PowerShell commands and it is an irreversible process.

Claims Based Authentication: SharePoint 2010 is built on Windows Identity Foundation. It enables authentication from windows as well as non-windows based systems. This also provides the capability to have multiple authentication in a single URL.

SharePoint 2007 - Master Merge

The concept of  Master merge and how indexing happens behind the scene in SharePoint

• Index server when crawls the content it creates a shallow index, shallow index is a smaller part of our index file. The reason for creating Shallow index, we can write efficiently on a smaller file rather on a bigger file and also we can propagate the index file faster on the network to all query servers.
• Reading all smaller index file will be time consuming, example when we server search query : "SharePoint" it would be a larger overhead to open all these smaller index file and perform search we need more file I/O. To prevent this overhead we perform merging of all these smaller files to a one single file called "Master Index" so that we can open a single file and perform search on the single index file. This process is called Master merge, merging all your shallow index to master index.
• By default we don't have any time period to schedule Master merge, it happens when we have shallow index more than 10% size of master index
• Master merge happens at query servers / index servers
• We can force master merge or change the size limit below is the link written by Bill Baer (very interesting) http://blogs.technet.com/wbaer/archive/2007/12/03/managing-master-merge-in-microsoft-office-sharepoint-server-2007.aspx