November 28, 2016 at 5:45 am
Hi all,
Thanks for all your investigations and suggestions. 🙂
Since I've replaced XML conversions (necessary with former "SQL Server 2008" but useless and costly with 2014 release) with standard CAST, all things are better.
I've also simplified views (1 instead of 2).
Now, performances are quite similar berween UAT and PROD.
I didn't create any index yet.
From my understanding of your explainations, optimizer uses kind of internal indexes based on statistics
...but to be sure to get similar results in different environments, it should be better to explicitly create indexes, shouldn't it ?
Regards,
Steph.
November 29, 2016 at 1:23 am
polytropic2310 (11/28/2016)
From my understanding of your explainations, optimizer uses kind of internal indexes based on statistics
That's a misunderstanding. SQL Server doesn't have any internal indexes. If you do not create any indexes, then the information is stored completely unordered and unindexed; and that will always affect performance (and allmost always ina negative way).
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply