Which Is Better Sql Or Ado Data Base To Use With Asp.net

[web_designer 7]

hi, i am now learning asp.net using visual studio 2008 professional edition. i want know which is better to use with asp.net SQL or ADO.net. or i should learn both of them.what are the advantages and disadvantages of each of them. i am more familiar with SQL more than ADO.net. but i think ADO.net is the a new dimension for the future. what do you think??

[k_nitin_r 8]

Hi!I think the two concepts, SQL and ADO.NET are distinct and are not replacements for each other.SQL is actually an ambiguous term because it can either refer to Structured Query Language, which is the language that is used to store and retrieve data from the database server, or it can refer to the database server from Microsoft, which is the MS SQL Server.ADO.NET is an interfacing mechanism with the database that enables you to retrieve data from and write to the database server irrespective of the database vendor. You can use the ADO.NET interface to work with Microsoft's SQL Server, the Oracle database server, MySQL, PostgreSQL, or pretty much any other database server that has either a driver/connector for the Microsoft .NET Framework, an ODBC database driver, or an OLE DB database driver.So, putting all of the concepts together, SQL statements can, optionally, be passed through ADO.NET and those can be run on MS SQL Server, and so SQL (both, in the case of the Structured Query Language statements, and the Microsoft SQL Server database) and ADO.NET are complementary to each other and are not substitutes for each other.

[web_designer 7]

thank you for your reply, when i posted this question i was just starting in data base in visual studio 2008, i found my self that i am understanding SQL more than ADO. so, i get lost. but now, i know that they are two things never depart.

[k_nitin_r 8]

Hi!@web_designerThe Microsoft .NET framework provides developers with all that they need from building web applications to enterprise applications and desktop applications. They've provided so many classes and libraries that you'll find yourself using some of them but not others because there's more than one way to get the application working the way you want it to. For example, if you are connecting to the Microsoft SQL Server database, you can either the SqlConnection class or you can use the OleDbConnection class. Similarly, for abstracting queries to the database, you can either use the Linq2Sql provider or the Linq-to-Entities framework to retrieve and manipulate objects from the database. In terms of building user interfaces, you can either use Windows Forms, or you can get more graphics-intensive applications using the Windows Presentation Foundation. However, if you really want to have control over the graphics rendering, you ought to create DirectX applications. Now, if the interface of your application has to cater to web users, you can either create a Windows Presentation Foundation web application that runs in the browser, or you can create a Web Forms application, then there's the ASP.NET MVC framework which builds upon the Web Forms architecture but has significant differences in the way you develop and build web applications, and you could use Silverlight which works pretty much like Windows Forms but runs within a web browser using the Silverlight plugin (think of it as an Adobe Flash equivalent).