Feb 18, 2011
visibility 10109
star star star star star
(0 votes)

The EPiServer Pages and Properties From the Database Point Of View.

The database diagram describing relations between EPiServer pages and their properties is given below.image

As you can see the tables tblPage and tblWorkPage are connected with “one – to - many ” relation. The main record about the page is stored in tblPage and the page  versions records are saved in the tblWorkPage. The query getting all the versions for the page with id = 49 looks this way:

select * from tblPage p
join tblPageType pt on p.fkPageTypeID = pt.pkID
join tblWorkPage wp on wp.fkPageID = p.pkID
where p.pkID = 49

When you create new page new record is added to the tblPage table. Everytime you publish  new version of the page the correspondent record is inserted into the tblWorkPage. Information about the page current version is stored in tblPageLanguage.PublishedVersion field which can  contain one of the tblWorkPage.pkID values.

Evidently, if you need to get the properties values for the given page version ( f.e.130)  you should execute

select * from tblWorkProperty where fkWorkPageID = 130,

where fkWorkPageID is a foreign key to tblWorkPage. So in much the same way the tblWorkProperty table keeps the history of properties values and tblProperty contains just a single record about given property – the value when created.

Feb 18, 2011

Comments

senthil Kumar
senthil Kumar Dec 20, 2011 05:48 PM

Hi Yugeen, Thanks a lot, very useful information for a beginner like me.

Oct 21, 2014 09:54 AM

Hi,
If I want to change a parent of a particular page from node1 to node2, which tables shall I look at?
Right now I have used the query below
update tblpage
set fkparentid = [new parent id]
where pkid = [id of the page]
This does change the node, but when I use the GetParents, it still points to the old node


Thanks.

Sofia 'Sonya'
Sofia 'Sonya' Feb 26, 2020 07:54 PM

Thank you, Yugeen! This has been very helpul.

I noticed that in Episerver version 10.10,  tblPage, as well as other tables you mentioned, are actually a Views in a database.

Thanks

Sonya 

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026

Opal Workflow Agents And The Graph Webhook Trap

What we did? We built a compliance review workflow agent in Opal. The job was simple: when an editor submits a page for review in Optimizely CMS 13...

Ritu Madan | Oct 14, 2026

cms13-scan: A Deterministic CMS 13 Readiness Scanner

Every CMS 12 to CMS 13 upgrade I have looked at starts the same way. Someone opens the solution and starts hunting. A text search for the APIs

Adnan Zameer | Oct 12, 2026 |