is it ok to use identity function to the large table?

Question

is it ok to use identity function to the large table?

Viewing 4 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Haryadi Santoso Old Hand Points: 364 More actions · Answer 1

fyi, i have shrunk and truncated the log file for tempdb database...but the problem still can't be solved...and the server harddisk still has 45 GB free capacity...

Jo Pattyn SSC-Dedicated Points: 32571 More actions · Answer 2

Looks your tempdb is running full or it can't grow fast enough.

Can you split your command in batches of 100 000? With a counter or something to remember the highest number?

Haryadi Santoso Old Hand Points: 364 More actions · Answer 3

Dear Jo,

Why tempdb is faster to become full when i run such query in the table which has an identity column (Car_Service_Ordered)?

Why it doesn't happen in the same table (Car_Service)? whereas this table doesn't have an identity column.

Thx in advance for the explanation

Jo Pattyn SSC-Dedicated Points: 32571 More actions · Answer 4

In such situations it is always helpfull to compare the execution plans of the queries, you can do this via the query analyzer: (Query) show estimated execution plan.

Possible reasons: the identity field is an extra 4 bytes. You also sort different vin,service date vs record id.

You could change your select into statement into a seperate create table + insert statement because select into can lock some systemtables. A good idea is to use column names instead of * to avoid trouble if the order of the columns would ever change.