I have checked the table definition of the field using sp_help in the query analyzer and this is what I have discovered.
The field definition in the source table for varchar and char are set to TrimTrailingBlanks = Yes.
While my new table in the destination the setting of TrimTrailingBlanks = No.

I think this is the cause why my database size increase more than 40 GB.

When creating table and set ansi_padding is off , the TrimTrailingBlanks is set to Yes.

I don't know what is the impact of set padding on/off before creating table.




>>that is the transaction logfile
>>try to set lging of when importing
>>dirk
>
>Thank you for your quick response.
>But I have already shrink the database and logs.
>I check the .MDF file size and it is bigger.
>The log is already shrink to small size.
>
>I don't know why the size of the .MDF becomes bigger.