I have a desktop app written on the premise that there will be many users, each with their own SQL database installation on their local machines.
If we want to migrate the entire project to the web, including user data, then, it would seem that the data tables would have to be modified to include a UserID column.
For example, if User A had records 1 and 2, and User B had records 3 and 4, we would not want User A accessing User B's records. Therefore, a column would be added to the tables to store UserID and all queries and updates would be modified to add the UserID.
This sounds like a real pain if this is necessary. I am unfamiliar with the Database schema in cloud services. Is a re-design of the database as described above really necessary, or is there some other way in which this problem has been dealt with to make a migration to the cloud more seamless?
Thanks.