You can solve your problem by following the activity
1. Shrinking the Database and Log file is the best option (But not frequent). You can schedule the shrink activity in Off-peak hours of the database access.
2. Defragment the Tables / Indexes timely maner by scheduling job in Off-Peak hours
3. Isolate the TempDB database from your Database physical location.
ie: If your Database and TempDB Database are there in D:\ Drive then, Try to move your Database to some other drive E:\ or F:\
4. Try to avoid using NVARCHAR, NCHAR like National Datatypes in Tables. so you can avoid unnecessary of memory usage.
5. If possible, Try to archive the outdated records into some other database in Different Server / Different location in the same server.
6. Try to implement Partition on Tables with multiple filegroups for frequently increasing transaction tables.
ie: Filegroups should be placed in different Physical location (C:\, D:\, E:\,...)
7. If you not implemented any Mirroring / Log Shipping / Replication / Transaction Backup on Server then, Try to maintain the Database's Recovery Model as "SIMPLE". Insteadof "FULL"
CheersArtisingh30, if this helps please login to Mark As Answer. | Alert Moderator