Data independence states that applications are independent of data storage structures and access strategies. This allows us to change the schema definition at one level without changing the schema definition at the next higher level. This ensures that changing the schema definition at one level does not affect the schema definition at the next higher level.   There are different kinds of data independence. Let’s see them:  Physical Data Independence – Physical data is the data that is stored in the database in bit-format. This data independence means changes at the physical level should not affect the logical level. For example, when working with the data on a table, do not change the format of the table.  Logical Data Independence – Logical data within the data is about the database. It basically defines the structure of the data, similar to a table stored in a database. This independence means changes in logical level should not affect the view level. For example, if we need to change the format of a table, this change should not affect the data stored in the table.