Answer the question
In order to leave comments, you need to log in
What to learn about junior .NET Backend databases?
I know how to write simple queries so far. But, I'm very confused, because I don't understand what I'm writing queries for - T-SQL or MS SQL? What is their difference? And what do you need to learn?
In the MVC framework, I used code first in Entity Framework 6. If you learn this O / RM, then what exactly do you need to know?
Answer the question
In order to leave comments, you need to log in
There is an ANSI SQL language, as it was, it does not exist anywhere in its pure form, each DBMS adheres to it, but introduces its own features that make it not fully compatible with other DBMS. SQL with "chips" in a particular DBMS is called a SQL dialect . MS SQL Server has its own dialect - Transact-SQL . You can also embed .NET assemblies in SQL Server.
EF generates T-SQL code from objects and expressions , sends it to SQL Server and parses the response again into C # objects, taking into account their relationships, which is why it is called ORM framework .
As they rightly say, EF and other ORMs do not free you from the need to know SQL and how relationships are organized there. For at interviews they will still force you to write SQL on a piece of paper, but in practice, in the name of the god of productivity, you will still write stored procedures in T-SQL. So you need to be able to work with ADO.NET, even though it looks quite antique in our hipster age.
T-SQL or MS SQL? What is their difference?T-SQL is a built-in language of (now one of) MS SQL.
Until you swing, tie with frameworks. They will easily destroy your ability to build architecture.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question