question

You can use the DBCC SHRINKFILE to shrink particular database file. But if you are not concern with your disk space and you have plenty of it, then i recommend not to shrink because your Database can reuse this space and you can reduce the DB auto-growth(if enabled) and the performance impact of auto-growth. If you really want to do it then, shrink your file so that you have reserved enough free space for your future db growth. The following command shrink the myDBFileto 10 GB DBCC SHRINKFILE(myDBFile,10240)

I suppose that you are already aware about the disadvantage of shrink database but you have drop many cluster index in your database and you want to claim space from database then you can shrink the database, personally I found that for fast shrink that database you could put database in single user mode and then shrink database then it will be 30% faster than your normal shrink. Please take care of given below things if you want to shrink the database- (1) Do not run shrink database command on live database, please disconnect all connection then only run this command. (2) If possible then put database in single user mode for fast shrink. (3) Rebuild or Re-Organize indexes after shrink the database otherwise database performance will be decrease. (Use SORT_IN_TEMPDB=ON) for rebuild the indexes.

By removing all your non clustered indexes you'll get a lot of free space in your DB, but you'll loose a lot of that space when you add them again. Are you really sure you need to shrink the files? I guess you already know the disadvantages of shrinking the files. I wouldn't use shrink unless I have dropped a some large tables that's not used anymore, or when I've implemented DATA_COMPRESSION on the indexes.