Wow

I am testing the logic only with a smaller client which same table but its only 30GB of size (whole database is about 90 GB) . The CREATE INDEX statement with DROP_EXISTING and ONLINE enable has taken 1hr so far and still not done. It is consuming 138GB of Tlog (we are on SIMPLE recovery model) and Tlog file still growing.

I'm afraid that for my 6 billion rows table this is not the way to go.

-- UPDATE --

The CI conversion only, took 1 hr 1/2 to complete and required 160GB of extra space for the Tlog.