B Nagaraju

Transcription

1

2 Agenda

3 What to expect in this session Complete ADO.NET Support available in.net Clear Conceptual View Supported by Demos Understand 3 generations of DataAccess.NET Around 9 minutes of videos Free Stuff

4 Let s Start with a small video about Microsoft Today from Top Fortune companies

5

6 Free Stuff for workshop attendees! Get Free Material of ADO.NET with Conceptual Explanation and Practical Examples ( Registrants ) for all versions

7 Data Access Architecture ADO ADO.NET OLE DB ODBC OLE DB Managed Provider SQL Client Oracle Client 7

8 ADO.NET and the.net Framework Microsoft.NET Framework Web Services User Interface Data and XML ADO.NET XML Base Classes Common Language Runtime 8

9 ADO vs. ADO.NET 1/2 ADO Designed for connected access Tied to the physical data model The RecordSet is the central data container RecordSet is one (1) table that contains all the data Retrieving data from > 1 table or source requires a database JOIN Data is flattened : lose relationships; navigation is sequential Data types are bound to COM/COM+ data types Data sharing via COM marshalling Problems marshalling through firewalls (DCOM, binary) 9

10 ADO vs. ADO.NET 2/2 ADO.NET Designed for disconnected access Can model data logically! The DataSet replaces the RecordSet DataSet can contain multiple tables Retrieving data from > 1 table or source does not require a JOIN Relationships are preserved: navigation is relational Data types are only bound to XML schema No data type conversions required XML, like HTML, is plaintext: Firewall friendly 10

11 Connected Layer The term connected layer implies that a connection to a data source is open while data is being analyzed or manipulated. ADO.NET does not support connected data operations. (few Read-Only actions are connected) Persistent connections must be made using the COM Interop modules with the older ADO, and OLE DB Libraries to work in connected manner. 11

12 Disconnected Layer By its very nature, ADO.NET is disconnected, which means a connection to the data source is not maintained. A disconnected layer allows our data source to free up resources and respond to the next user. 12

13 ADO.NET Architecture ADO.NET Architecture is the latest extension of the Universal Data Access technology from Microsoft that uses textual formatting instead of binary formatting. In ADO.NET Architecture data is accessed and manipulated in a connectionless manner by using data providers. The Command, Connection, DataReader, DataAdapter & DataSet are the core objects in ADO.NET. They form the basis for all operations regarding data in.net. 13

14 WPF Forms Presentation Tier Windows Forms MyApp.Exe Typical Implementation of Classical ADO.NET in Projects DataSet Web Forms IE DataSet Internet Intranet XML Business Tier Data Object (Class) DataSet Data Adapter Data Adapter Data Tier Business to Business (BizTalk, for example) 14

15 ADO ADO.NET RecordSet DataReader DataAdapter DataSet Command Connection Command Connection 15

16 Data Access Namespaces in.net System.Data System.Data.OleDb System.Data.SQLClient ADO.NET System.Data System.Data.OracleClient System.Data.XML.SqlTypes.SqlClient.Common.OleDb 16

17 DataBase Classes/Objects in ADO.NET OleDbConnection /SQLConnection/Oracle.. OleDbCommand/SQLCommand/Ora.. OleDbDataAdapter/SQLDataAdapter/Ora.. OleDbParameter/SQLParameter/Ora.. DataSet DataTable DataView DataRow DataColumn 17

18 Programming with ADO.NET Connection Represents A Connection To The Data Source On A Connection, You Can Customize the connection to the database Create a Command object associated with the connection Begin, commit, and abort transactions Equivalent To The ADODB.Connection Object 18

19 Command Object Responsible for Invoking Stored Procedures from Database Also used for running SQL Commands like Insert,Update,Delete Statements 19

20 Command Object Represents a Command To Be Executed Not necessarily SQL With An ADO.NET Command You Can: Define a statement to be executed on the server Set parameter information for that command Retrieve return values from command execution Corresponds To ADODB.Command Object May Contain Parameters Values to be used when executing a statement 20

21 Command Object ExecuteNonQuery ExecuteReader ExecuteScalar ExecuteXmlReader (for SqlCommand object only) BeginExecuteNonQuery BeginExecuteReader BeginExecuteScalar BeginExecuteXmlReader (for SqlCommand object only) 21

22 DataReader Object DataReader provides forward-only and readonly streams of data Represents results of an executed query or command Equivalent to a FO/RO RecordSet Doesn't support scrolling or updating Supports Databinding 22

23 DataSet Object a client-side database. 23

24 DataSet Object Equivalent of ADO RecordSet but Richer Relational views of data Contains tables, columns, rows, constrnts, views, relations Disconnected model Has no knowledge of data source Array-like indexing, Strong typing Supports Databinding Supports batch updates Connects to data source via DataAdapter 24

25 DataAdapter Manages Data Exchange Between DataSet and Data Source Fill() Update() Provides Mappings Between Tables & Columns User Can Override Insert/Update/Delete Commands (Autogen component available) Allows Single DataSet To Be Populated From Multiple Different Datasources 25

26 DataSet & DataAdapter DataAdapter SelectCommand Database InsertCommand UpdateCommand DeleteCommand DataSet TableMappings 26

27 DataSet Tables Table Columns Constraints Column Rows Constraint Relations Row Relation 27

28 D a t a S e t Connected Operations Original DataStore Table1 Resolves changes with Managed Provider DataSet Table2 Extracts tables With Managed Provider Disconnected Operations Makes changes to data Table1 Table2 Table1 DataSet DataSet Sets up relationships Table2

29 Demo

30 Benefits of ADO.NET 2.0 Interoperability through use of XML Open standard for data that describes itself Human readable and decipherable text Used internally but accessible externally (Can use XML to read and write and move data) Scalability through the disconnected DataSet Connections are not maintained for long periods Database locking does not occur Locking support with ServiceComponents - Optimistic locking otherwise Works the way the Web works: Hit and Run! Maintainability Separation of data logic and user interface 30

31 C# 3.0 VB 9.0 Others.NET Language Integrated Query LINQ to Objects LINQ to DataSets LINQ to SQL LINQ to Entities LINQ to XML <book> <title/> <author/> <year/> <price/> </book> Objects Relational XML

32 The Good Easy to use Very powerful for read operations Absolutely recommended for 2-tier app Good for most ASP.NET architectures Where Data Access Layer and Presentation Layer are in the same process Released

33 The Bad The Challenging Change tracking in stateless environment (ASP.NET) Understand when query are executed and how Lazy vs. Eager Loading The Ugly Doesn't have multi tier change tracking support ADO.NET Entity Framework is an alternative Works only with SQL Server

34 Use the SQL Profiler all the time!! Use the SQL Profiler all the time!! Use the SQL Profiler all the time!! Use the SQL Profiler all the time!! Use the SQL Profiler all the time!! Use the SQL Profiler all the time!! Use the SQL Profiler all the time!! Use the SQL Profiler all the time!! Use the SQL Profiler all the time!! Use the SQL Profiler all the time!!

35

36 OLD ADO.NET 2.0 Linq To Sql Entity Framework

37 EntityFramework Versions Entity Framework 7 Entity Framework Entity Framework 6 -> Entity Framework 5 Entity Framework 4.1 -> 4.3 Entity Framework 4 Entity Framework 3.5 SP1 Runtime out-of-band (NuGet) Tooling out-of-band (Microsoft Download Center) Latest version chained in to new Visual Studio releases Core runtime in.net Framework Newer runtime pieces out-of-band (NuGet) Tooling in Visual Studio Runtime in.net Framework Tooling in Visual Studio

38

39 3-Layer / Typed DataSet Presentation Business Logic (Orchestration) Data Access BusinessLogic::[X]BM DataManagers::[A]DM QueryManagers::[M]QM QueryManagers::QmBase Presentation::Screen Presentation::Service BusinessLogic::[Y]BM +Get() +GetByID() +Commit() +DoSomeInterestingBusinessProcessing() Contains business rules and logic at the process or use-case level. DataManagers::[B]DM +Get() +GetByID() +Commit() One DM per DataSet. Contains logic for ordering operations and controlling all DataTables in the DataSet. QueryManagers::[N]QM +Fill() +FillByID() +Insert() +Update() +Delete() #FillDataTableByDynamicSql() #FillDataByStoredProcedure() #PerformInsert() #PerformUpdate() #PerformDelete() One QM per DataTable. Contains logic for basic database operations for each table or query Contains business rules at the entity level. BusinessObjects::[B]DS Business Objects / Data Transport Database Database::Stored Procedure BusinessObjects::DataTable[N] System::System.Data.DataSet BusinessObjects::DataTable[M] Database

40 3-Layer / Entity Framework Presentation Business Logic (Orchestration) Data Access (Entity Framework) Presentation::Screen BusinessLogic::[X]BM BusinessLogic::[Y]BM This layer is implemented through configuration using: * Conceptual Model * Storage Model * Mapping Spec Presentation::Service +Get() +GetByID() +Commit() +DoSomeInterestingBusinessProcessing() Contains business rules and logic at the process or use-case level. Contains business rules at the entity level. BusinessObjects::[EntityA] Business Objects / Data Transport Database Database::Stored Procedure Database

41 Demo

42

43 Links Team blog of Microsoft blogs.msdn.com/adonet Documentation EF6 Project EntityFramework.codeplex.com EF7 Project github.com/aspnet/entityframework Facebook facebook.com/nbende

44 Don t Miss..Coming Workshops DevOps - Agile Thank You.! Cloud Computing Angular 2.0/React JS and more...net 2015 in your apps Universal Apps/Mobile Apps

45 Questions?