I suspect there are some sites out there where a “set-it-and-forget-it” approach is taken for DB2 related performance. Many clients we go into don’t even realize the need for having a DBA. Depending on site size, that may work for a while.… Read the restContinue reading »
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 restContinue reading »
This is part of a series focusing on the details of each item that needs to be pruned in a Commerce database.
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 restContinue reading »
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 restContinue reading »
Ok, so there are several good reasons for Backing up your Commerce DB2 database
- After Commerce Instance Creation
- As required by your overall ongoing backup and recovery strategy
- Before a FixPack(DB2 or Commerce) or Feature Pack(Commerce)
- After a FixPack(DB2 or Commerce) or Feature Pack(Commerce)
- 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.
Schedule DB2 backups starting immediately after instance creation – the most common time that restores are needed is during the build process. Of course the most common cause for needing a restore is human error, but that’s something that is important to protect against during build.… Read the restContinue reading »
Just a quick tip. When building Commerce environments, select a different database name for each environment (Stage, Prod, etc), even if they are on different database servers. This will help you ensure that you(or developers or whoever else accesses the databases) never do something in the wrong environment.… Read the restContinue reading »
One of the most important things for performance of Commerce databases is the proper use of dbclean and data pruning.
It is a simple fact of life for OLTP databases that the same database with less data will perform better. This is especially true of Commerce databases, and even before a site has gone live, I try to have data pruning planned, scripted, and running on a regular basis.… Read the restContinue reading »
There is a flag that can be set on DB2 tables to mark them as “Volatile”. But not everyone knows what a volatile table is or what this does, so I thought I’d write a quick post on it.
A true volatile table is one that is used only for transient data – data that is put into tables and then quickly removed, meaning that a table marked as volatile could have zero rows one minute, 40,000 the next, and then back to zero.… Read the restContinue reading »