>OK, 50% is pretty high and 80% is very high.
>
>Now, if your data isn't terribly large, you might barely notice any query degradation (at least to the naked eye)
>
>But bottom line, when you reach fragmentation that high, SQL Server has to do more work than necessary to retrieve data.
>
>I have only ever seen this once, and it was 10 years ago - but I saw a site where fragmentation was so high (approaching 99%) that the SQL Server engine basically took the database offline (or something to that effect). It was a real cluster-****
The customer ran the reindex that Martina posted. Now the numbers are much lower. The database is not very large. The biggest table is less than 1000,000 (one million records). The other IT just tested that the speed is much better. But he said that the problem is intermittent and may come back. So we will see.
But I definitely take your input and will ask the IT to run these scripts to defragment on regular basis. If they do, that is another story (you know, "you can take the horse to the water ...." )
Thank you for much for your help.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
