10 Commerce Tables you should be familiar with

UPDATE: An updated version of this post is available – Updated: 10 WebSphere Commerce Tables You Should Be Familiar With

 

So there are 800+ tables in the typical Commerce database – you’re never going to know them all. And getting a start on understanding the data model – even in the more limited way needed when you’re playing primarily the system dba role can be daunting.… Read the rest

Continue reading »

DBClean – Guest Users

This is part of a series focusing on the details of each item that needs to be pruned in a Commerce database.

Guest Users

What is it?

Guest Users are created by Commerce in the database. Technically they are only needed for when you allow a customer to add items to their cart before logging in or registering, or for a few other actions.… Read the rest

Continue reading »

HADR

What is HADR?

HADR is DB2’s implementation of log shipping. Which means it’s a shared-nothing kind of product. But it is log shipping at the Log Buffer level instead of the Log File level, so it can be extremely up to date.… Read the rest

Continue reading »

Stagingprop – the basics

I realized today that I haven’t done a post on the basics of stagingprop. All the pieces are there somewhere in the info center, and I love the info center once you’ve got the basics down, but I remember how confusing stagingprop was when I first started out, even though I had a major expert on the topic to ask questions of.… Read the rest

Continue reading »

DBClean – staglog

This is part of a series focusing on the details of each item that needs to be pruned in a Commerce database.

STAGLOG

What is it?

Staglog is a table in the staging database that records changes in data. Staging triggers on all stagingprop tables write to it when there is a change to any of those tables.… Read the rest

Continue reading »

DB2 for Commerce IDs

So the easy thing to do on Commerce build is to use your DB2 instance owner for everything related to the database. But that’s not really the best choice. It’s almost always the choice I see when a DBA was not involved with the architecture or build of a Commerce system.… Read the rest

Continue reading »

When to Backup your DB2 database

Ok, so there are several good reasons for Backing up your Commerce DB2 database

  1. After Commerce Instance Creation
  2. As required by your overall ongoing backup and recovery strategy
  3. Before a FixPack(DB2 or Commerce) or Feature Pack(Commerce)
  4. After a FixPack(DB2 or Commerce) or Feature Pack(Commerce)
  5. Before any task that requires change of a lot of data – such as first time pruning, explicit executions of delete statements or update/insert statements that will affect more than one table.
Read the rest Continue reading »