.NET||ADO.NET||Ado.Net Introduction by MohanReddy

today I am going to discuss about a do dotnet okay so what is a do dotnet so using a DeVoe dotted what we can do so what is the advantages of radio dotnet we will discuss okay so a Leawood dotnet stands for active X data object Eddie BOE dotnet stands for active x8 data object okay so ad or dotnet is a native driver a do dot neck is a native driver so mainly using a devout net we can connect to the database so ad whoa dotnet is used to provide communication from front end to back-end application so that is what before going to discuss about AD whoa dotnet you need to know the few terms okay that comes called first one is front end application front end application second one is back-end application back-end application third one front end tool fourth one back in the tool okay these are the few terms you have to know before about a tivo Dorner front-end application back-end application front end tool and back-end tool front end application means the application which will be interact with screens forms web pages reports these are all our front-end application back-end application means the application where we can store in the user information or client information that is called back-end application you know front-end application means our dotnet web pages or window forms like that back-end application means SQL Server database design the database in that okay and front end atoll and back and tool front end atoll means the toll our software which is used to develop front-end application is known as front and tool for example Visual Studio is a front-end atoll in.net if we take Java NetBeans is a front-end okay so eclipse is a front-end so many front-end tools are they back and the tool means the tool our software which is used to develop back-end application is known as backhand tool back and tool is nothing but sequel server management studio okay this is called back and tool because using the tool only we can able to design back-end application like that okay right so why I am discussing here front-end and back-end this using a de veau dotnet ad whoa dotnet is a native driver using a de veau dotnet we can communicate from front-end to back-end application okay in reality compulsory each and every website should maintain some database they should interact with the database compulsory so we should connect the data in database and we will get the information from the database we will transfer the information to the database these communication should be done in especially in dotnet applications using a de veau dotnet so without a de veau dotnet we cannot write database connectivity program okay we cannot write a database connectivity code this is the main important of area dotnet so ad word or net is used to connect to database or it is provide to communication or interact with the database is possible okay right so a debo dotnet is what native driver we can say okay right so here in ad whoa dotnet especially we need to discuss layered approach okay we need to discuss layered approach so there are three layers are very needy border plane so first layered approach second layered approach and third layered up in that what layered approach we have to follow then let's see that okay right for going to talk about first layered approach here first layered approach in this layered first layered approach front end and back end applications are present in same mission front end and back end applications are present in same mission this is mission one here it is front end application here it is backend application both are communicating with each other okay this is the layered approach first lead approach in this first layer front-end application applications are present in same mission what is the drawback in this layered approach no front end and back end applications are present in same mission so they communicate with each other no translatory mediums are required okay and the eighth approach cannot support centralized database that means what centrally-located database with the database many clients can be interact that is called centrally located database but here it is again application this is database purpose here with this back-end application no other clients can interact so only this client only can interact this front-end application only can interact so it will not support centralized database okay so and we cannot store large amount of data into this database only so this is the drawback of first layered approach to overcome this drawback we will go for second layered approach here I am giving second layered approach second layer approach in this second layered approach front end application and back and applications are present in two different missions friend and application and back and apply to different missions here it is mission one here it is mission two here front end application back-end application here native driver here also native driver so here native drivers are going to be interact with each other the front-end application means you know dotnet and Java sample and the front-end native driver e back and native driver is back-end application is SQL crackle so these are an application and back-end application here front-end need two driver and back any two driver in this layered approach front-end and back-end can be present in two different mission this is mission one and descent this is mission two okay so here front-end and back-end or present in two different missions so in this lead approach it supports centralized database that means database is separate mission with this database any clients can be interact with this and we can store large amount of data also here it is possible so this is the very useful layered approach here okay so here what is the role of native drivers here in this layered approach okay so in this layered approach front-end application and back-end application cannot interact directly with each other rather they interacted through native drivers here front and NATO driver is they that is a Devo dartnet back and native driver is there that is SQL native client if you use SQL Server database okay so front end whenever sending requested to back-end application that request directly will not go to back-end application rather it goes to where this request goes to front-end native driver this nature driver take that request and this request is converted into back and native driver understandable format and sends to back and nature driver so back and nature driver will send request to the backend application same vice versa response also will be happen like this only back-end application will send the response to front-end application but it will not go directly response to front-end application meanwhile it will go to where back and native driver this back and native driver will take that response and it will convert into front end and a two driver understandable format and front-end native driver will send response to front-end application okay so these both are going to be communicate the role of native drivers are to communicate with each of the front-end and back-end application will not communicate with each other directly they interacted with what through native driver so what is the drawback of this layered approach okay so I am telling here so using this layered approach it can be support centralized database once the database is present here in back-end application many clients can be interact with this database and whatever they want they can access here okay centralized database is possible and we can store large amount of information also in this database application okay it is possible then what is the drawback you know yes so what is the drawback means if front-end application is having this native driver particular native driver okay that native driver is only suitable for particular back-end application for example let us consider so this is a front-end application okay front-end application this front end up equation is contained native driver that is end a one end a one so native driver one this native driven one is used for interacting with what database for example SQL database so this native driver is reserved for SQL Server database Anya okay so this is only reserved for SQL Server database but here this front-end application this is having native driver one okay but it is having interaction with what SQL Server but if you use Oracle database then this is not going to be support here okay because this native driver one already reserved with SQL Server again front end should maintain what native driver - like this so differences in two driver should maintain front end same like backend application also okay for example back-end application is there for example back location is that is SQL server this SQL is maintaining one set of native drivers that is nd1 it is used to interact with what application dotnet application but this native driver is reserved for dotnet application for example here java application is there front-end again this back-end should maintain what separate native driver that is nd2 so this is the problem here okay so what is the problem whenever front-end application wants to interact different databases then front-end application compulsory should maintain different set of native drivers and whenever back-end application wants to interact with particular front-end application and back-end application also should maintain different native drivers okay for interacting with different front-end application so this is the problem with this too late approach okay so that is what to overcome this drawback we use third layered approach so how it later prove it will be we will discuss no front-end application no back-end application should maintain set of native drivers because drivers they are not interact with each other they are interact with through middleware here now let me talk about prelate approach here it is three layered approach here it is third layered approach third layer approach okay this is third layered approach now here front-end application as usual here front-end a native driver it is ad vitur net and here in the middle varies there here you can see this is middleware middle way and here back and application back in native driver here native driver here pattern application so what is happening here front-end and back-end cannot be interact with each other directly and native drivers also cannot be interact with each other directly middle weight solve it so what is the middleware here these are the data providers like SQL client is and were active client one data provider then JDBC Java database connectivity ODBC open database connectivity Willa DB object link embed database these are the data providers here if you use data providers we can able to communicate with anything here okay so if you in set of native drivers back-end application and front-end application need not to maintain set of native drivers when they want interact with different front-end applications or when they want to interact with different back-end application set of native drivers are not required for native driver is enough okay because native drivers are not going to interact with each other they interact through middleware like data providers okay this is the third layered approach okay right so this is the layered approach in a level dotnet now we will discuss so the mainly ad or dotnet is provide two types of architectures a devotee provide how many types of architectures two types of architectures ad or dotnet will provide what are the two types of architectures that our first one is connection oriented architecture first one is connection oriented architecture second one is disconnection oriented architecture connection oriented sure and disconnection oriented architecture a Devo dartnet will provide mainly two types of architectures connection oriented and disconnection oriented so connection oriented means whenever programmer wants to interact with the database compulsory connection should open whenever programmer has finished their task with database some operation has completed database you should only close the connection that means as a programmer you should open connection and you should close the connection okay that is called what architecture connection oriented architecture this collection oriented architecture means what whenever we send request to the server or database automatically connection is open whenever we get response from the database automatically connection is closed so this is called disconnection or inter architecture in this disconnection oriented architecture you need not to open connection you need not to close connection in connection oriented architecture compulsory should open connection and after finishing your task from the database you should compulsory close the connection this is okay right action oriented architecture and disconnection and connection oriented architecture is having two methods that is method one and Method two method one and Method two connection oriented architecture is having how many methods two methods ever we used any one of the method you should compulsory open connection and you should close compulsory close connection okay that should be done so this method one so actually this method one is used to this method one is used to do the operations into database and what used to do operations into database okay this is client and here it is server you can consider this is database in this method first step client will send a request to the server request means opening connection after sending request second step he will perform required operations he will perform required operations and after completion of performing required operation simply he will close the connection this is what the method one you know method one of connection oriented architecture what is the use of method 1 method 1 is used to perform required operations on to the database like if we want inside the data but if you want to delete the data or if you want to update the data then we can use what method method 1 so in a third I need to build send request to the server for required operation to do he will perform required operation whatever he wants to do like inserting updating deleting after completion of his task you should close the bot connection compulsory this is what method connection oriented architecture using method one only we can do the operations like inside delete update the data into database you strictly remember using method one we cannot read the data from database okay if you want to read the data from database you can use method two off connection oriented architecture so using method two we can read the data from database we cannot perform operations like insert delete update the data into database this is and scenario is different this is for transferring the data into database this is for gate the data from database okay so I'm going to explain this method to find okay here it is climbed and here it is server server client and server this is database here what I mean to say result set here result set or network buffer we can say in this method to client will send request to the server for required data to read I want to for required data to read purpose client is sending request client request is process here in second step client request is process after completion of process client requested data is dumped into result said or network buffer also we can call once the client requested data is present in result set is established to the client in tourists once link is establishing to the read the day say plug simply will close the connection because it is printed architecture again okay so this is connection oriented architecture method to method to is for what purpose to read the data from database method one is used for what purpose to transfer the data into database like if you want to do the operations we can use method one inside delete update or you want to get the data from database or you want to read the data from database you can use method two these two methods are going to work with what connection oriented so compulsory whenever you want interact with the database you should open connection whenever you get the data from database after completion of that you should close the connection whenever you finish task from the database so method two scenario is what client will send requests to the for required data to read client requests will be processed at server-side after completion of process client requested data is dumped into where result set it is a memory which is a lot for the client at server-side once the data is present in result set the link will be established the client once the link is established to the client client starts read the data from where result set after completion of reading client should close the connection so this is what connection oriented architecture method to it is just for reading the data from database it is just for doing operations into database like inside delete update whenever you use method one and Method 2 of connection oriented architecture compulsory you should open connection and compulsory should close the connection okay right now we talk about a disconnection oriented architecture this connection oriented architecture means what whenever you want interact with the database you need not to open connection that means when you request to the server automatically connection is going to be open whenever you get the response from the server automatically connection will be closed so that is what this connection oriented architecture you need not open connection and you need not to close connection let me loop the scenario of this connection oriented architecture for example you can see this is that client ok here it is client and here it is process area process area and client will send request to the server as usual client will send trick with server client rich will good and client requests will be process itself after completion of process client requests that data is dumped into process area and after that client will starts read from process area now what is the main but it is difference between connection oriented architecture and disconnection oriented architecture means here you should not open connection and close the connection whenever you send request to the server connection is open automatically whenever you get response from the server connection is closed automatically so client will send requests to the server for reading the data or writing the data whatever it is and client requests will be processed at server side once process is completed requested data is dumped into client omission only that is called process area here it is processing once the data is present in process area link is going to be disconnected okay there is no need to work with database so client will always read the data from where process area what is the advantage if you know this processor is present in client emission once the client requested data is present in process area anytime they can interact with process area you need not to go and every time to collect the data from server so here one-time request will happen every time one time only you are getting entered the data what you want and you can place your data in your mission only so if the data is present in our mission client omission then why we need to interact with always server it is a very advantage actually but disadvantages when whenever you immediate temptation is not required then later if you decided to update back the data to the database and you can use this connection oriented architecture method otherwise immediate temptation is compulsory required like if you are just reading and transferring the data back to the database then you can go for connection oriented architecture method to okay which one is better to you as per your requirement you can follow but here request here only one time client request this process and processor data is present in process area once the data is present in process area there is no prior connection to maintain to the database then client always interact with this process area whatever they want to do these operations and all they can do immediately one time it will be update back to the database this is called dis collection oriented architecture okay so this connection oriented architecture and disconnection oriented architecture so we will with the clear picture with programmatic representation database and all but it can strictly remember in AD or dotnet whenever you want to do these all operations or whenever you want to interact with the database compulsory then you have to use some objects ad or direct objects and classes but without that objects and classes we cannot do anything in database so that all ad or dotnet objects and classes are present in this namespace system dot data dot SQL client namespace yl client you know I am going to interact with SQL server so that's what compulsory this namespace is required system dot data dot SQL client but if you interact with Oracle then system dot data dot were ichael without this namespace a do not need classes and not present here okay so you want to connect it with the database so here I am giving some objects names object so whenever you want interact with the database so we have to use object name and class name objects and classes are present in system data dot X calc line so this namespace is compulsory system dot data dot SQL client why because whenever I am going to interact with SQL Server you can use SQL client or if you are interacting with vehicle database where I will require so here I am giving object name and class name here object name and class name object name is for example connection object okay let me give that object name is connection class name is SQL connection okay object name is command class name is SQL command object name is parameter last name is Esquivel parameter object name is data reader class name is SQL data reader object name is data adapter class name is SQL data adapter object name is data set class name also data set these are the main important objects using these objects and process we are going to connect with the database and we are going to do the operations into database without these objects and classes we cannot do anything all classes are present in where system data desk will climb if you are not including system dot data data sweet line namespace these classes are not going to become okay so these are all present in this namespace so connection me if you want to connect to database you can use connection object command means after connecting you want to do some operations like insert delete update we can use command R through parameters you want to work with you can use parameters data reader means it is reverse so you can read the data from database whenever you want to read the data from database already data is present in database then you can use reader and this connection command parameter data reader are work with what architecture connection oriented architecture but the data set both purpose we can use either we can store the data into database either you can read the data from database these are work with what architecture base connection oriented architecture okay these are so all these we will see practical implementation each and everything one by one how to connect with the database how to command how to do the parameter and how to read the data from database everything we'll discuss in later sessions you

Channel: Durga Software Solutions

Views: 31,532

Keywords: durga, durga sir, durgasoft, interview, questions, java, software, training, c# programming, c sharp programming, c sharp, asp net c#, programming c#, programming in c#, c# programming language, c# development, c# developer, c# for dummies, c# online

Id: n7hL9Aolm0I

Length: 30min 46sec (1846 seconds)

Published: Fri Aug 19 2016