WebSphere Commerce – Oracle or DB2

So I’m obviously biased on this. I’ve been a DB2 DBA for 10 years and believe in DB2 very strongly. Some of my biases against Oracle may be completely unfounded. I’m actually learning Oracle so I can support clients who…

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…

When to Backup your DB2 database

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…

Build Tip – DB2 Backups

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…

Build Tip – Database Naming

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…

DBClean – Junk OrderItems

So I’m starting out my series on DBClean and data pruning items with the one that I have seen cause the most immediate severe performance impact. I’ve seen this one take a site to its knees within two months of…

dbclean and data pruning intro

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.…

What to do when DB2 won’t work

This probably falls more in the DB2 newbie category, but I suspect I may have some readers who are DB2 newbies or at least not veterans. Several years ago (ok, probably more than 5), DB2 seemed to be considering a “Problem…

Never do runstats on volatile tables

Ok, so everyone will tell you that it doesn’t matter if you do runstats on volatile tables. The volatile flag is supposed to tell DB2 that the statistics are absolutely not correct, and heavily bias db2 to use indexes over…