'I like stability more than features,' said Helle. And no wonder: When Helle arrived at Westminster, Colo.-based NextAction in mid-2004, the company was plagued with near-weekly crashes of its core database, which aggregates and analyzes consumer purchasing data from more than 1,100 retailers such as Home Depot and Williams-Sonoma.

NextAction uses a custom-written extract, transform and load (ETL) tool to clean up and import the data. Unlike competing consumer databases that can aggregate only where and when a consumer goes shopping, NextAction can also tell what the consumer actually bought at each store, according to Helle.

In 2004, the company's 13TB data warehouse was spread across five Microsoft SQL Server 2000 databases. But within a year, the fast-growing firm's database had grown to 30TB spread across eight instances of SQL Server 2000. 'My guys were working 70 to 80 hours a week,' he said. 'We were dying on the vine.'

NextAction's data warehouse was growing too fast to easily manage on SQL Server, said Helle, and it would crash so often that the process of mining data for retailers grew from three and a half days to eight days -- a major problem, since the data mining took place weekly. 'That's what really impacted revenue, the fact that it failed quite often,' Helle said.

One of the first actions Helle, a 15-year veteran of database marketing, took was to convince his boss that NextAction would need to upgrade to new hardware and a new database to handle its intensive and fast-growing data needs.