computed column making the select query to run slow We are creating indexes, as per the requirements, on one server and copying all the indexes to the other servers. All servers have similar objects &amp; schema but different resource configuration values.

We have an issue where a query that joins 4 views is completing on one server but the same query is taking 4 minutes on the other server. If I take out the computed column from the select list it is completing in 4 seconds.

The two execution plans are quite different.

1)  Is this a good plan to copy the indexes blindly where SQL is choosing different execution plans?

2) I have also tried to create the index on the computed column on the base table, still no luck, any further suggestions? ( We can’t create an index on views for some reason.)
"Is this a good plan to copy the indexes." Indexes exist to improve the response time of read operations. Those operations arise from the workload. If the workload differs, the indexes should differ, too.

For example, it is not uncommon to have one server handle the OLTP activity and replicate the data to a second server where analytic queries are processed. The first server's work will be mostly single row lookups. The second's range scans and aggregates. In this case having different indexes on each server makes good sense. If all indexes were on both servers there would be additional, unnecessary work to do during writes and maintenance.