Which one is better when performance is taken into consideration-Ghosted(Compiled) of Un-Ghosted(Interpreted)?

It really depends on the complexity of your page.  On a very small and simplistic page, the difference would be neglible.  On larger and more complex pages, ghosted pages have a definite advantage.

 

You can easily determine what best suits your needs by running your own tests...

 

according to the above, this cannot be done.

 

however,

 

1) cant i do this by resetting the CONTENT column to NULL in the DOCS table?

 

If yes,

2) how do i find the page i am looking for in the DOCS table?

 

thx

my previous post should say unghosted to ghosted

Use the GhostHunter web part (as mentioned above)... it is the best option available.

The other concern to that needs noting is when updates applied to SharePoint passing through to the unghosted pages.

Hello, quick question. Does anybody know of a way to access and parse through a .properties file residing on the server from the SharePoint default.aspx page? Thank you in advance.

To change the default.aspx page from being unghosted to ghosted, can i just set the Content to null and set the setuppath to an appropriate value? I know this question was asked before, but did not see any answers to it. How excatly does the the GhostHunter webpart achieve this? :)

 

Hi....

I would really appreciate some help.... Ghosting and unghosting has always been a sort of dilema for me. I just want to clarify..... is a page only unghosted when using frontpage... How about if I edit the default.aspx (Homepage) in Notedpad does this unghost the page as well?

Also, when I add new columns to a list does it become unghosted? When I modify a page only through the browser and add like 10 new webparts does it become unghosted?

Would greatly appreciate your help.....

Thanks .....

Ryan-
A page is unghosted any time you edit the actual page, whether in FrontPage, NotePad, DreamWeaver, or anything else capable of opening and saving a text file. Unghosted simply means that the page has changed from the default.aspx template which is stored in the file system. Dragging and dropping WebParts on the page does not change the underlying .aspx page. When the page is rendered, SharePoint in the background queries the database and pulls from the database the WebParts that have been assigned to each WebPart Zone on the page. The WebPart Zones are what is actually the content of the default.aspx page, and the content for each zone is loaded when the page is rendered.
As for Lists, a list is not ghosted or unghosted. There is no physical "List" like there is a physical "default.aspx". A list is simply stored in the content database.

When you add columns to a document library, pages will not become unghosted.  However, if you update a column value for a particular web part page, your page will become unghosted.

 

The following post should shed some light...

Performance was mentioned in the comment dated Jan. 4, 2005.  Unghosted will be a tad slower due to the nature of a system, but it mostly depends on the complexity of your page.

 

-Maurice

Is it possible to reghost a page by setting the Content column to null? What exactly does GhostHunter do when it reghosts a page?

Excellent article !  Good content and easy to read, thanks.

I never found answer to this question :

 Can we convert an unghosted page to ghosted by making its content NULL and giving setuppath a default value??

 

Please answer this...........Thanks in advance..

If you are using v3, use the API to reset your page to its original ghosted form. 

Please do NOT attempt to reset pages on your own via direct database actions.  This is not supported, nor does the GHWP offer or imply such supportability.  More importantly, the GHWP is for v2 ONLY.  Chances are you have long stopped using v2.