• Your choices are pretty limited. You can remove data and then shrink the database. You can use storage compression if you're using Enterprise in SQL Server. You can look at a third party product like Red Gate SQL Storage Compress (disclosure, I work for Red Gate).

    In general, simply saying, make the database smaller, is somewhat difficult to answer. Why do they need this. What are you trying to achieve? Is it just a storage issue or something else going on?

    "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