New answers tagged performance-tuning
The reason why you don't see much of benefit is because of the LIKE clause on column CODE. The optimizer would, in general, will not prefer such columns. The optimizer cannot directly resolve such types of queries/clauses. I would suggest you to have an index on column CompanyId alone and see if that helps. Good luck!
It's very unlikely that running master and slave on the same machine would be beneficial, because the two instances would not actually be sharing resources in any positive or helpful way. Running two instances with the same data means you have to divide up the available resources in some combination of implicit (cpu, disk, memory including OS cache) and ...
This is in the documentation: Clustered indexes must be created, rebuilt, or dropped offline when the underlying table contains the following large object (LOB) data types: image, ntext, and text. Nonunique nonclustered indexes can be created online when the table contains LOB data types but none of these columns are used in the index definition ...
Top 50 recent answers are included