Most of us by now are aware of the basics of Ghosting and Site Definitions
- We know ghosting refers to the process whereby a database reference to a single set of files (the site definition) is made when creating a site in SharePoint as opposed to a physical duplicate.
- We have learned that ghosting helps boost performance and reduce file storage needs.
- We have learned that the true benefit of site definitions and ghosting is seen when updating a large number of sites via a single set of files.
- We have learned that a page becomes “Unghosted” when we open and save it in FrontPage 2003.
- We have learned from Fitz that SharePoint 2007 has big plans to help relieve the pain of unghosted pages.
The reality is that many of us have unghosted pages now and unfortunately not everyone will be able to have SharePoint 2007 right away. In the absence of that there are some really great solutions out there which deal with unghosted pages.
I made a post a couple of months back about the new version of reGhost.NET by Matthew Cosier
I finally had a chance today to install and try out the latest reGhost.NET application. I have to say from a user-experience perspective I was very happy with everything from start to finish.
The application is just as fast an easy to install as it is to use. On top of that (to the best of my limited testing/knowledge) it really seems to work. If you have not yet had the pleasure of trying this application I would highly recommend it.
This has been tested with WSS SP2 + SPS SP2, please let me know if you have any other problems using other configurations.
This version will also tell you exactly which site the particular page came from before reghosting it, making a great choice for those large commercial sharepoint databases with hundreds, thousands, millions of ghosted pages (we hope not that many).