Once I determined that it is the ADO.NET connection at the root of the problem, this thread led me to the answer. Basically connections through Sql Server Management Studio (SSMS) by default have SET ARITHABORT ON. ADO.NET connections do not. Setting ARITHABORT OFF and executing the query directly through SSMS gives me the same slow … Read more
No, they are the same thing. I disassembled SqlConnection.CreateCommand and found this: public SqlCommand CreateCommand() { return new SqlCommand(null, this); } which proves that they really are the same thing.
It is possible. In .NET 2.0+, SqlDataReader inherits from DbDataReader, which implements IEnumerable (non-generic one). This means that you can use LINQ: List<string> list = (from IDataRecord r in dataReader select (string)r[“FieldName”] ).ToList(); That said, the loop is still there, it’s just hidden in Enumerable.Select, rather than being explicit in your code.
I posted an answer on another question on another topic that might have some use here. That answer involved SMB connections, not SQL. However it was identical in that it involved a low-level transport error. What we found was that in a heavy load situation, it was fairly easy for the remote server to time … Read more
By following the naming conventions , you will find it’s called : ADO.NET Entity Framework , which means that Entity Framework sits on top of ADO.NET so it can’t be faster , It may perform both in equal time , but let’s look at EF provides : You will no more get stuck with writing … Read more
From the MSDN Forums: If you right-click the TableAdapter in the Dataset Designer and click ‘Configure’ the TableAdapter Configuration Wizard opens where you can reconfigure the main query that defines the schema of your table. This should leave the additional TableAdapter queries (the additional methods) that were added after initial configuration. Of course the additional … Read more
Try this method. It should work when field when you want to store image is of type byte. First it creates byte[] for image. Then it saves it to the DB using IDataParameter of type binary. using System.Drawing; using System.Drawing.Imaging; using System.Data; public static void PerisitImage(string path, IDbConnection connection) { using (var command = connection.CreateCommand … Read more
As stated in the documentation for that constructor: When you specify an Object in the value parameter, the SqlDbType is inferred from the Microsoft .NET Framework type of the Object. Use caution when you use this overload of the SqlParameter constructor to specify integer parameter values. Because this overload takes a value of type Object, … Read more
You won’t immediately gain anything by switching your existing code to use TransactionScope. You should use it for future development because of the flexibility it provides. It will make it easier in the future to include things other than ADO.NET calls into a transaction. BTW, in your posted example, the SqlCommand instances should be in … Read more
You can’t (unfortunately) do that. A Sql Parameter can only be a single value, so you’d have to do: WHERE buildingID IN (@buildingID1, @buildingID2, @buildingID3…) Which, of course, requires you to know how many building ids there are, or to dynamically construct the query. As a workaround*, I’ve done the following: WHERE buildingID IN (@buildingID) … Read more