no it doesn't support multiple inhertiance through classes. However, a single class can implement multiple interfaces.

It's an acronym for Language Integrated Query. Language Integrated Query (LINQ) is a Microsoft project that adds a native querying syntax reminiscent of SQL to .NET Framework programming languages, initially to the C# and Visual Basic .NET languages.

SQL cache dependency is the ability to invalidate a database cache if data in a table is changed.

This is a tricky Question, I would evaluate where I am giving an interview at. If the workplace is one which is known for following rigid Process guidelines, then I would say I would speak to me supervisor to make him/her aware of the significant risks involved in this situation and request to delegate/distribute the work. Alternate Answer: If the workplace is one which requires to be flexible (like the Support Engineering tasks) answere that you will manage your time in such a way that you cover most of the work, while communicating frequently with the supervisor with updated status.

It depends what the logic is. If you need to do complex manipulation of data already in the database, it is probably better than trying to run sql queries and fetch the data into the middle tie and perform the manipulation in the middle tie, then send the large amount of data back to the database using sql insert or update. On the other hand, you can do to something simple using sql, but you have to write quite a lot of code in stored procedure, why do that.

For stored procedure vs. dynamic sql queries, assuming you are not talking about case where you can call stored procedure within a sql query or you can use dynamic sql inside a stored procedure, dynamic query has a downside (at least in Oracle db), that it has to be compiled if the exact sql string is not used recently (seconds I think) by any session, which could takes some time, and use some system resource. On the other hand, logic in stored procedure is not necessary automatically better.

I think you have to compare approaches based on how easy it is to write the code to do what you want, how easy it is for others to understand and maintain the code, and what is the performance cost in a target database, etc.