Re: Efficient way to alter a large table with limited space on the server

I just noticed the 3rd column in your index is RowNum and it's also defined as numeric(10).

Are you at risk of running out of values for RowNum, too?

Can RowNum values be re-used once you hit the max of 9.999 billion?