I think there is something hidden happening here such as some data inserts and deletes which causes the file size growth. A few things we need to know is:

1. What was the original size of the MDF file when you created the new database? By any chance, did you happen to create the database with a huge initial size? (which may be the reason for having empty/unused space in the db)
2. How did you configure the database file size growth? By any chance, have you configured the database to grow by a large size when the existing space is fully used?
3. What is the schema of the table which caused the unexpected file size. Do you have a number of large value type columns and by any chance have you (or a program/process) inserted a large number of rows into the table and later on deleted?

One of these may be causing the unexpected file growth.

Thanks Jacob,

as per point,

1) DB initial size is not huge, it is by default 13 MB .mdf and log file is 10% of mdf. 2) file size growth also same as created, there were no any large size of existing space. 3) yes, but only one table has large value type columns(Text datatype) which has inserted and deleted record log.

but as i said other client production server same applications are running but i did not face such kind issue.

executed by DBCC CLEANTABLE command spaces are available in Database that means its reclaim for memory where ever drop table and column, but no any alteration in any table.

The database file size will grow only when the current size is not enough to hold the data. So when the number of rows grows, SQL Server will allocate more space to the data file which will naturally increase the MDF file size.

In your case, you see a lot of empty space (unused space) in the MDF file which indicates that some inserts occurred which forced SQL Server to grow the file and later on the data was deleted. When you delete data from a table/database, the space already allocated to the MDF file does not shrink. SQL Server will keep the allocated space as - unallocated - until you explicitly shrink the file and reclaim the unused space.

So now what step should i implement on it?

Well, the first thing is to identify what is causing the file growth. Once we know that, we can discuss the possible options. May be you need to do a continuous monitoring of file growth which will give you a better idea of what is happening.

Thank you very much Jacob for giving your such important time to me..