Like PatP, I have also favored GUIDs for all their unique capabilities.

However I am facing a GIS/List Management project that is multi-year and multi-nation and includes hierarchical organization ownership and overlapping territory boundaries.

I was impressed by the disk impact calculations in this article: that was referenced in this forum on another thread.

So my current strategy is to move to INTs for fundamental data relationships within the transactional records but to maintain a separate hierarchy based on GUIDS for a separate hierarchy to track ownership. Or maybe not even then.

In any case, I anticipate a period of uncertainty where I may have to switch various areas of the overall schema between ints and GUIDs until i get the right balance.

So what I think I'm going to need is a group of scripts based on the example provided by GVee that are tailored with the standard column names I'm using throughout the design.

Thanks,

Kimball