free_mascot (1/31/2011)
When you are transfering large data to new table; I suggest you create just basic structure of the table i.e. without indexes, rules etc.Once transfer is done you can create the required indexes depending on your queries.
This will be much faster.
HTH
Maybe, maybe not. Inserts into tables with a well-constructed clustered index are faster than inserts into a heap table. It's all the additional non-clustered indexes and foreign key constraints that can slow down inserts. But even these may benefit inserts depending on how the inserts are being done. You really have to address each situation individually and not use a blanket approach.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning