Copying one SharePoint 2007 web application with all site collections to another farm.
Here are the steps described under “Migrating using SQL Server Tools”
to move databases across farms.

Steps to move Site Collection from one farm to another farm:

• Create a SQL backup of the content database of the web application you want to copy/migrate
• On the destination server, restore the backup in a new database.
• Create a new web application on the destination server (use the
  default database name proposed by SharePoint)
• Detach the database
  • Go to Application Management – Content databases
  • Select the correct web application
  • Set the database status to offline
  • Backuprestore1
  • Click Add a content database
  • Enter the correct details about your restored database and click OK to finish

stsadm -o addcontentdb -url [http://Youroldserver] -databasename
[WSS_Content] -databaseserver [SQL Server Instance]

You will get   “Operation completed successfully” message when migration is done

While WSS and MOSS are both pieces of software built by the Microsoft Office team.

Windows SharePoint Services 3.0

• WSS is included as a part of the Windows Server 2003 operating system
• WSS as the underlying platform
• WSS does not have its own licensing model. Instead, the use of WSS is controlled through Windows Server 2003 licenses.
• It has the core document management and collaboration platform features With WSS, the average information user can build web-based business applications without numerous technical resources.

MS Office SharePoint Server 2007

• MOSS is a separate product with its own SKU
• MOSS is a value-added set of components and services that has been built on top of this WSS.
• MOSS has its own licensing model that includes server-side licenses and client access licenses (CALs). The MOSS licensing model is further broken out into a Standard Edition and an Enterprise Edition.
• MOSS 2007, is the nexus of the Microsoft Office system It delivers the robust, enterprise-targeted features of SharePoint Products and Technologies, which accelerate business processes across the intranet, extranet, and Internet.

Ghosting means process of requesting  an uncustomized page instance by using a page template loaded into memory from the file system of the front-end Web server. These Ghosted pages are pulled from the cache at runtime and therefore it will increase the scalability from the system.

All uncustomized pages are reused across all the sites and there is no unnecessary data storage or retrieval.

Ghosting eliminates the need to transfer the contents of a page definition file from the SQL Server computer with the content database to the front-end Web server computer

For example, the default home page is a ghosted page. Any web part pages created via New Web Part Page user interface also ghosted.

Unghosting means that the site has been customized. When you customize a site in SharePoint Designer, or you add custom fields to a Document Library, or create sites using that template; then the changes that you made are stored in the database as a difference and that is referred to as Unghosted.

A request for a Customized (Un-Ghosted) page returns a response which is a combination of data from both the file system and the database.

All Unghosted sites are based on a Site Definition.