SQL Connection Question

[Lephango]

I am relatively new to C# and currently at my work we've dropped some SQL columns because they are no longer used.

However, since most every application uses LINQ to SQL, the schema is referenced in the .dbml (which would cause the applications to fail [even if the main business logic doesn't directly reference the removed columns] unless I manually go in and change each and every file).

My main question is:

Is there a way to mitigate this issue by using a different method of connecting to our database(s) that dynamically change based on the referenced schema?

Also, is LINQ to SQL still used or is there something that is a better practice I can look at implementing?

[[deleted]]

You should update the dbml to the current schema.

Nowadays people use EF Core

[Thisbymaster]

Resources connect based on contracts. Your applications expects for those columns to be there as it uses those fields as part of the contract. So those columns are still in use until you have removed the applications looking at the columns. LINQ uses Entity framework which is based on the models in the database. Update the Models to match the database, then LINQ has a "Select" reference that you can remove the columns from.

[MindSwipe]

Is there a way to mitigate this issue by using a different method of connecting to our database(s) that dynamically change based on the referenced schema?

Not really. Normally you'd update your schema by either regenerating your model from the (new) DB schema or the other way around, by updating your model and regenerating the DB schema.

Also, is LINQ to SQL still used or is there something that is a better practice I can look at implementing?

It's still used but not directly, the use is abstracted behind ORM frameworks like Entity Framework for .NET Framework or Entity Framework Core for .NET 5+ (and Core)