sqlconnection

I have a Log class which put logs in Windows journal and in a SQL table. In order to optimize my code, I would like use only one SqlConnection . In MSDN, it says: Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe. My question is : private static readonly SqlConnection conn = new SqlConnection(ConfigParameters.Instance.UIDConnection); Is it thread-safe ? If yes, when use Open() and Close() ? If no, how use properly SqlConnection ? Here is my full class code : private static readonly SqlConnection conn = new

Please help! Background info I have a WPF application which accesses a SQL Server 2005 database. The database is running locally on the machine the application is running on. Everywhere I use the Linq DataContext I use a using { } statement, and pass in a result of a function which returns a SqlConnection object which has been opened and had an SqlCommand executed using it before returning to the DataContext constructor.. I.e. // In the application code using (DataContext db = new DataContext(GetConnection())) { ... Code } where getConnection looks like this (I've stripped out the 'fluff' from

I've never used the "appSettings" before. How do you configure this in C# to use with a SqlConnection, this is what I use for the "ConnectionStrings" SqlConnection con = new SqlConnection(); con.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionString"].ConnectionString; And this is what I have for the "appSettings" SqlConnection con = new SqlConnection(); con = ConfigurationManager.AppSettings("ConnectionString"); but it is not working. Anton Vidishchev ConfigurationManager.AppSettings is actually a property, so you need to use square brackets. Overall, here's what you need

hi I'm getting an error Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding . I'm alredy changed the connect timeout = 60000 and in database my procedure is executes in 43sec. so plz give me some perfect solution thank you You should note that Timeout property for SqlConnection object and Timeout property for SqlCommand object are different properties. By default command timeout is set to 30 seconds. Set it to 60, and your issue will be solved: commandObject.Timeout = 60; But most likely that you should change your SQL procedure or