Hello Ivan,

>It means that after
>making lot of changes into data and doing backup/restore,
>data in restored database will be stored more "dense",
>and optimizer will use different cardinality estimation.

Thanks, I didn't think about that. But it is stil very strange because
the primary index I talk about in the productional database has
selectivity: 0,0000074... and after restoring it "drops" to
0,0000006....

Instead of using it the optimize chooses to use a foreign key with
selectivity of only: 0,00003... which is very strange to me.

>Btw. are the indexes active in the restored database ? :-)

Yes they are active :))

--
Best regards,
Alexander mailto:saho@...