Why is there a strong fragmentation of the table _Acc15 BP 3.0 in MSSQL?

Question

1C

Good afternoon.
In 1C BP 3.0, I found that all indexes on the _Acc15 table and a couple of other tables are highly fragmented.
There is a daily reorganization and weekly rebuilding of the indexes.
The weekend passed, the magazine says that everything went well. But the indexes of the _Acc15 table are highly fragmented.
Maybe 1C does not allow MSSQL to rebuild the indexes of any tables? The skul itself didn't say any errors, but in the fragmentation report the numbers show 50-75% fragmentation. And some forms and interface elements without a thorough VERY slow down.
- - - -
Accounting itself flies, except for one single form. Sales/purchase book. It is when any user opens these forms that 1c starts to just insanely wildly stupid. At the same time, there is no activity on the server in this regard. And there is no activity on the client side either. I tried to raise the client on different computers, up to the mssql server itself. One fig - stupid fucking book of sales and purchases at the opening. (not the formation itself). She's just dumb.
I sin on this table, which does not want to be defragmented.

Answer 1

1. For a start MSSQL version?
2. During work, do profiling ----> take it apart, what works out in the end.
3. How many records are in a fragmented table?