I'm in the middle of what's becoming a rather heated discussion with a client. The thiong is that I developed a Reporting Services report against three joined views/tables, and it worked great. Then they move their db to a new server, and also decided to make some of the local views remote. Now the report hardly works at all.
There are three tables, A, B, and C, with a left join between each. The join B -> C works great, while A -> B is very slow. I've told them several times that they need to add a foreign key index on table B that is obviously missing, and they absolutely refuse to do so, saying that this is a 3rd party system that they will not mess with, and at the same time they are not willing to talk to their 3rd party supplier about it. Instead, they want me to rewrite the report to use sub reports. I'm telling them that this will take at least two days, that I currentlly don't have the time to do so and that they should at least be willing to try to set the index and see if that works.
I'm running out of arguments here, but can any of you think of a good reason NOT to index a foreign key? I certainly can't
BTW, all databases are on the same SQL Server 2005 instance.
Start Free Trial
