Community discussion forum

Back to discussion

Using ADO.NET with SQL Server

Last post was 11 Jun 2009 at 06:00
Tags: .net, ado.net, asp.net, csharp, db United Kingdom
This is a comment thread discussing Using ADO.NET with SQL Server
  • 10 years ago

    This thread is for discussions of Using ADO.NET with SQL Server.

    Report abuse
  • 5 years ago

    is there anything you dont know?

    Report abuse
  • 5 years ago

    I enjoyed this article.  Clearly constructed, good basic examples, logical progression of complexity.  All fairly basic stuff, but a good grounding.


    Thank you!


    Report abuse
  • 5 years ago
    yeah. I haven't quite figured out how to get time to write more of these!
    Report abuse
  • 5 years ago

    Bravo!! James...... You wrote that article so fine....so lucid it is....Got a good insight into Ado.net.
    Would like to see you going into more details on it...Well Done!!

    Report abuse
  • 5 years ago

    Very clear and concise, well done! Keen to read your next article on this topic...

    Report abuse
  • 5 years ago

    I wanted to know if this article was written with inline code in mind or code-behind.


    It would appear to me to be written from an inline perspective but I am new to this and may be wrong.


    I am desperately looking for someone to write something that is geared more towards (what I thought was ) the Microsoft vision.  Where the developer is using the full functionality of the IDE in terms of the drag and drop features and connecting the controls via the code-behind page.  This would also allow for segregation between layers (presentation, business, database).


    Do you know where I can find such a tutorial?


    Thank you for your time.


    Sincerely,


    Tim

    Report abuse
  • 5 years ago
    This was still aimed with code-behind in mind. However, I've found a large number of people happily dragging and dropping components from the toolbox, or using the Microsoft wizards, with no real idea as to what each object actually *does*. Although the wizards are great time savers for many things, personally I still prefer writing my own logic for making calls to database stored procedures etc. But maybe I'm a control freak!

    In terms of layer segregation - there's no hint of layout code here. At the most, we're setting the DataSource for a datagrid - and then presumably the .aspx page would be dealing with the layout/appearance.

    Report abuse
  • 4 years ago

    I am very happy !


    I wanted to know how the asp.net database stuff exactly works.. and well here it is..
    step by step.


    Thnx
    /mamoman

    Report abuse
  • 4 years ago

    It was really useful in reading this article. great stuff... could have explained the update method little  bit in detail.
    Thanks for the good work though....
    Take care,
    Suresh.N

    Report abuse
  • 3 years ago
    Very nice article.  It helped me a lot in converting some VB6 code to VB .NET 2005.  The only thing I would add is a message at the top that this is for VS 2003.  In VS 2005 they have made some minor changes to the syntax and the above code would not work.  Ex.

    Dim sqlConn As New SqlConnection(connectionString)



    would now be:

    Dim sqlConn as New SqlClient.SqlConnection(connectionString)





    Report abuse
  • 3 years ago

            Great article, very helpfull. Although I'm writing because I have lingering doubts on the subject in general, I've been programming with visual basic, all the way from 6.0 to 2005 and several database managers, and I've generally avoided the use of datasets, datatables, etc etc, I work writing my updates, inserts and deletes (you have to set them up anyway using datasets), and fill my datagrids using arraylists of the objects I build, which gives me certain freedom populating them, since I can manipulate the data before showing it... on the other hand, I've also found confusing the interaction between tables and datatables with an auto-numeric value, could more likely be lack of experience, but it creates dificulties that I do not have working more directly with the database itself... So my question is, mainly, why use datasets, datatables and so on? what definites advantegaes do I get from using them instead of working with the queries myself? (which by the way I hear is faster (in runtime), and cleaner...) .. Any thoughts would be welcome of course, I'm just looking for opinions...

     Thanks!

    Alita

    Report abuse
  • 3 years ago

    dear sir,

    i 'm facing some problem in insert data from an application to database using dataset. pls. help me in parameterised insert data into a datasource.

     

    sukanta

    Report abuse
  • 2 years ago

    hello,

    hey very gud article. but i am facing  a problem that when i connect to SQLServer usisng C# it doesnt allowed me to connect by saying its a valid user. as i am using Windows authentication for connecting to the SQLServer

    Report abuse
  • 2 years ago

    hello,

    hey very gud article. but i am facing  a problem that when i connect to SQLServer usisng C# it doesnt allowed me to connect by saying its not a valid user. as i am using Windows authentication for connecting to the SQLServer

    Report abuse
  • 2 years ago
    Hi all,

    After spending about 6 months part-time experimenting with the 2005 pro vb.net interface using wizards, its my opinion that wizards should NOT be used to develop anything but fixed database prototypes.

    I had actually started using code in 2005 but it was crashing so much that I tried the wizards.
    The wizards didn't crash so much when building solutions.  I thought I had finally found a code generator that actually worked.  Come to find out only up to a point.

    Once I started using the wizard, I had so many work arounds and crashes from attempting to change a database field that I finally gave up.  Some of the crashes were so bad they actually corrupted files.

    The wizards are there just to "wow" unsuspecting parties into thinking its super easy to use.
    Its not.  Its super easy to use exactly how they demo in the limited way of the drag-n-drop features and thats all.

    Absolutly no support or demos regarding how to modify once built.
    I tried chasing down the code behind the wizards but like every other code generator its so complex its propriatary and very easy to break.

    Don't use the wizards as a coder.  Develop everything in code.

    I could suggest only to use the wizards on a fixed database and never try to modify the db or the code.
    Just re-wizards everything.

    Or use the wizards to dupe unsuspecting clients into thinking its easy to use.

    So please, please don't waste your time using the wizards.

    ---------------

    James Crowley wrote:
    This was still aimed with code-behind in mind. However, I've found a large number of people happily dragging and dropping components from the toolbox, or using the Microsoft wizards, with no real idea as to what each object actually *does*. Although the wizards are great time savers for many things, personally I still prefer writing my own logic for making calls to database stored procedures etc. But maybe I'm a control freak! In terms of layer segregation - there's no hint of layout code here. At the most, we're setting the DataSource for a datagrid - and then presumably the .aspx page would be dealing with the layout/appearance.


























    Report abuse
  • 2 years ago
    hey pls need help wit the connection string for using sql server wit ado.net. im not gettin the code lines for the connection .please help.its urgent
    Report abuse
  • 2 years ago

    Hi Folks,

    I keep getting this error when trying to connect to my sql dbase.

    An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

    I'm currently learning to use vb.net and sql server, so i am a novice. Any help would be gratefully appreciated.

    kindest regards.

    Report abuse
  • 2 years ago

    Hi, finally getting somewhere with my understanding of ADO but am still a bit lost with my predicament.

    I have an Empress (SQL) database on a Linux server that I want to link to an MS Access database on a Win2000 PC (they are both on the same closed network).

    Although I have read and understood the topic and have tried and failed to get my link to work I have somehow managed to get myself stuck in a neverending loop of confusion. I think I'm trying to do too many things with too many programming languages at the minute and am one stage away from placing my underpants on my head with a pencil up each nostril and need someone to guide me through to the next stage before I implode!

    Thanks

    Report abuse
  • 2 years ago

    Excellant article, very meaty and precise!

    Here is a little utility for helping get the precise sequence of objects correct for a particular combination of request/data type, at least for SqlClient

    http://www.nicecleanexample.com/Tools/SqlBuilder/SqlClient.aspx

    jk

     

    Report abuse
  • 7 months ago
    My version of your code gives an error when trying to DataBind it: "The data source does not support server-side data paging." what am I doing wrong? -pk string sql = "select * from casefolder"; SqlConnection sqlConn = new SqlConnection(connectionString); // Sets up the connection, it is closed here -pk01 sqlConn.Open(); SqlCommand sqlComm = new SqlCommand("select * from casefolder", sqlConn); SqlDataReader r = sqlComm.ExecuteReader(CommandBehavior.CloseConnection); gridCases.DataSource = r; // Call to DataBind needed in ASP.NET - Fails at this point: "The data source does not support server-side data paging." -pk01 gridCases.DataBind(); sqlConn.Close();
    Report abuse
  • 7 months ago
    Sorry about that! See if this works better. -pk My version of your code gives an error when trying to DataBind it: "The data source does not support server-side data paging." what am I doing wrong? -pk string sql = "select * from casefolder"; SqlConnection sqlConn = new SqlConnection(connectionString); // Sets up the connection, it is closed here -pk01 sqlConn.Open(); SqlCommand sqlComm = new SqlCommand("select * from casefolder", sqlConn); SqlDataReader r = sqlComm.ExecuteReader(CommandBehavior.CloseConnection); gridCases.DataSource = r; // Call to DataBind needed in ASP.NET - Fails at this point: "The data source does not support server-side data paging." -pk01 gridCases.DataBind(); sqlConn.Close();
    Report abuse
  • 7 months ago
    I can't seem to get the hang of sending code, I clicked on "code" but it still didn't work, so a few extra blank lines might make it clearer? My version of your code gives an error when trying to DataBind it: "The data source does not support server-side data paging." what am I doing wrong? -pk string sql = "select * from casefolder"; SqlConnection sqlConn = new SqlConnection(connectionString); // Sets up the connection, it is closed here -pk01 sqlConn.Open(); SqlCommand sqlComm = new SqlCommand("select * from casefolder", sqlConn); SqlDataReader r = sqlComm.ExecuteReader(CommandBehavior.CloseConnection); gridCases.DataSource = r; // Call to DataBind needed in ASP.NET - Fails at this point: "The data source does not support server-side data paging." -pk01 gridCases.DataBind(); sqlConn.Close();
    Report abuse
  • 5 months ago

    The new VSTS enables you to convert your imagination into the perfect material images on screen ! Let your mind do the thinking and VSTS will do the rest ..... http://bit.ly/izsu9

    Report abuse

Post a reply

Enter your message below

Sign in or Join us (it's free).

Ask a question

Related discussion

Quick links

Recent activity

Languages

Web Development

Frameworks & Architecture

Other major sections

Cancel
We'd love to hear what you think! Submit ideas or give us feedback