Should I split a SQL Server table?

Question

I have a table where most columns are very, very often read (SELECTed) and almost never updated.

Now I need to add a set of columns to the same table (they are properties of the same object), only they will be less readable, and they will also be updated very often

If I add new columns to the same table, will UPDATE interfere with SELECT?

Should I instead create a new table with a 1 to 1 ratio with the previous table?

If this is important, I am using Azure SQL Server.

Answer 1

-, . . UPDATE SELECT, SELECT , ( , , , , select SELECT *). , SELECT :

SELECT distinct * FROM my.Table where [NewColumn] is not NULL

, UPDATE, , , null , UPDATE , SELECT , 1 , 2 .

, , , , , .