HI @nayan_wylde , @shanisolomonron 

I don't think it works in the way you've described. We can easily check this. Each time I execute following code I get new id:

%sql
CREATE OR REPLACE TABLE databricks_demo_ws.default.my_table (
  id int,
  name string
)

So, first time I've exectued above code I got id: f2a57c4-152b-46c4-9dd5-b1e945846d71

Then I execute above code second time. As you can see, no major schema changes occured but still I got completly new id: 641cacab-7175-4f44-98cc-fad9ba8aa66e

I think what they refer in docs as table identity is more related to catalog / metadata identity (not necessarily the same as the internal delta log id). Because all other things mentioned in documentation hold:

• The table history is retained, and I can revert the table to an earlier version with the RESTORE command.
• The operation is a single transaction, so there is never a time when the table doesn't exist.