Why can indexes in the database not be deleted / edited?

Question

SQL

Please, prompt:
There are 2 tables, in one 2 million records, in another 10 million, both terribly slow down at joins.
I decided to deal with indexes: I went into MSSMS to manage indexes in tables, I see that in addition to the expected clustered index on id, there are 2 more indexes, but they can’t be edited, deleted, and even just the properties can’t be viewed - the options are disabled. With what it can be connected?
For the experiment, I created a separate pivot table, 12 fields, 2 million records, I have not yet set indexes. Sampling (without any joins) takes about 2 minutes.
Please tell me:
Is this a normal execution time for such volumes or is there room for optimization?
If not normal, what time is considered acceptable?

Answer 1

Decided to figure it out

Look at the standard performance reports (or run Profiler), find the cause, look at the execution plan (by turning on IntelliSense), follow the recommendations to reduce the cost (if any - in blue).

Answer 2

No rights, most likely.
what does:
begin tran
drop index
rollback ?
But that's not even the point. There can't be a problem with joins that there are other indexes there. Now, if the insertion-deletion braked, yes.