and, if you move the creation of the indexes to after the population, do you still get this error? If not, that's possibly a good workaround. It also means you're not getting the overhead of updating indexes while the table's been populated.