Why Azure SQL clustered index is so extremely big?

Question

When I compare index sizes in our MS Azure DB, there is something weird.

I have two different DB tables (let's say tableA and tableB). Both has PRIMARY CLUSTERED INDEX on single BIGINT column.

tableA has around 350 000 records, and tableB has (slightly more) 380 000 records.

But index on tableA is 1100 Megabytes in size, and index on tableB is just around 100 Megabytes.

Can someone explain why is this happening ? Where could be the problem ?

PS: The index size was measured with script published here: http://blogs.msdn.com/b/sqlazure/archive/2010/08/19/10051969.aspx

Answer 1

Clustered index size show the actual size of the table. That's why in the blog, in query is condition:

WHERE type_desc = 'NONCLUSTERED'