I use the command

DBCC DBREINDEX(MOV_MAG,' ')

in a scheduled job, using MSSQL management studio gui.

I run it with a weekly schedulation, but I start it "by hand" when the issue appear.

The thing which is giving me some perplexity is that before the upgrade to a new version of the software which is using this DB, there was a complete maintenance plan, running every week (also with reindex) and it was enough for the DB, and the DB has worked flawlessly for more than ten years.

Anyway I will read surely the stairway suggestions and the fragmentation explaination from the links above, and probably I will try to write a job which will be started if the fragmentation will be higher than a percent.

Other suggestions and observations will be appreciated.

Thanks guys!