Aleksi’s answer to your question is correct.
My question is why you have a table with over 200 columns?
Every table should correspond with one “object”, such as, a person, an order, a product, etc.
Every column should correspond with a “property” of that “object”. For example, a person might have properties of first name, last name, age, address, etc.
It is possible, but very rare, to have a single “object” with over 200 properties.
Often when there are that many properties, one of two things is happening.
The table is actually combining information for two or more objects. You can check this by examining each property and asking what object that property is describing. For example, if you have inadvertently combined the person and the order in one table, you will notice that some properties are related to the person and others are related to the order. In that case, you need to create separate tables for person and order.
The table has a field that occurs multiple times. For example, if you have fields with names like “Image1”, “Image2”, “Image3” or “Order1”, “Order2”, “Order3” then it is very likely that you need to move the occurring items to a child table.
My intention is to help, not criticize. When I see tables with so many columns, I wonder if the data modelling is correct.