Tagged articles - ADO

Although JSON is widely used as a format for sharing the data, there are still existing solutions or modules that still rely on ADO and DataTables. Even today it very common to see some piece of code which deals with DataTable or DataReader for the performance reasons. In the end if any of the ADO objects needs to be exposed as a JSON string you have to write your own serialization code. ...read more

So far (based on my experience) the fastest way to insert big number of records from application to database is to use SqlBulkCopy. The downsize of this is that SqlBulkCopy uses DataTable instace as an input parameter which is not so convenient when dealing with models which are strongly typed and a lot more easy to use than iterating through the DataTable. Since SqlBulkCopy accepts DataTable for insert you can not use models directly to insert your data...read more

This article is base don the article I wrote in September last year. Basically I wrote this piece of code because I needed something really lite for one way binding. There are a bunch of light ORMs and ORM-Like solution, but both of them provide two way binding, but for me insert/delete/update commands were already handled by stored procedures as it was an existing solution which needed some new features, so I needed something to make reading a lot easier...read more

Entity framework is an awesome tool for working with database in .net, but sometime you have to get back to old fashion ADO for the performances. The bad thing is that as soon as you get back to ADO, you have to deal with SqlDataReader, DataTable and DataSet classes. This is not so convenient for using in upper levels of applications, especially in MVC environment where using strongly typed objects is an essential thing. ...read more

Passing complex data to and from stored procedures has always been a tricky one. The most elegant way to pass values to a stored procedure is to use predefined data types in SQL Server...read more