When we work with Episerver and Episerver commerce, all the data we work with is stored within two back-end databases. When we build projects, you should never write any form of code that talks to the database directly. Everything should always go via the Episerver API. If you don't, you can corrupt your installation and completely kill your website.
There are certain times when you come across one of those annoying bugs that don't seem to make any sense that taking a peak in the database to check that the data you expect to see is there in the correct format. In today's tutorial, I'm going to cover some of the most useful tables that I've needed to use over the years. The point of this article is to grow and expand over time, so if you want any knowledge about the Episerver database, please leave a comment or email me.
Software Architect, Programmer and Technologist Jon Jones is founder and CEO of London-based tech firm Digital Prompt. He has been working in the field for nearly a decade, specializing in new technologies and technical solution research in the web business. A passionate blogger by heart , speaker & consultant from England.. always on the hunt for the next challenge