When should i open and close the database connection.and which are best data classes (for e.g dataset, datatable etc) should i use when connection is open or close.
I have an application with a few dbml files to connect to several sql servers in order to import data from one to another using Linq to SQL.
There are 2 connection strings with integrated security and in one I provide user ID and password.
It all works great in the development workstation. I've then wrapped the dll project and deployed the asp.net application to a test server. Then, when I tried to run the application to import the data, I got a connection exception:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I figured out after some debugging the problem is with the DataContext whose connection string is the one I provide user ID and password. Now, the funny part is that the same connection string works if I create a udl file and test it. And again the same connection string works with my development workstation.
I've a web form named contest, where users are to register for it. When the register is clicked on, details entered by the user will be saved into the database, but before it will check if the user has already participated in the contest (using AJAX). If the user has already participated, the button will be disabled. The problem is there is an error when I click on the register button.
The error:
ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.
I previously used a datasource and a connection string to connect to my database on sql server and all orked fine. The connection string was saved in my web.config file and is: ....
I'm using Visual Studio 2008, and my database is SQL Server 2000.
I want to add a connection to the Server Explorer in VS. The Data source is Microsoft SQL Server (SqlClient). After entering in all my information and I click Test Connection, it is successful.
But when I click OK, I get the error:
Unable to add data connection. ExecuteScalar requires an open and available connection. The connection's current state is closed.
I have developed Dynamic Data application for DB administration. I'd like to show thrown exception message (when connection to db is closed) in UI friendly manner. I cant figure out where to catch this exception.
Tried EntityDataSource events in List PageTemplate - no success.
In my DAL i have more than 100 methods/Function, each and every method am opening the sqlconnection and closing the connection, this is taking too much of time to establish the connection at every time. So what i expect is one common class will create the SqlConnection that will check if the connection is Broken or Closed then create the connection again else return the connection, how to do this(Also i would like to apply ConnectionPooling).
I have a page where I load a couple of dropdown lists from the database (DB). I do this by calling a general function that connects to the DB and gets the data to the dropdownlist. This means that I can have three queries to the DB while rendering one page.
should I close and dispose the sqlconnection, sqlcommand and sqldatareader at the end of this function?
Would it be faster if I left it open for the next call, if you get what I mean, or is it best to close and dispose it every time?
Our site was under Slow HTTP POST DOS attack recently. It's when your server receives a lot of incoming connections and keep them for long time because the sender sends information very slow and server cant serve real users' request - denial of service.
The problem is that I can't drop the HTTP connection in asp.net:
Response.End(), throw new Exception(), even Thread.CurrentThread.Abort()
don't close the connection. It waits while sender sends all the fake data, then answer to it with '500 server error' or something. The slow POST attack still will be successful in this case.
The reason this question came up, is because if I run my website application with a SQL Server data store, and I terminate the browser (terminating the session), I try to open up SSMS to edit the DB. But I can't access the database because I believe there is still an open connection, even after application termination.
Is it recommended to close the database connection upon session/application closing? Or am I way off on what I'm thinking could be the problem?
I made a site www.hediyelikdukkani.com and I added the site to goole from web masters tools. But google doesn't index my web site. When I test my site how the google see from Test like a Google bot from web masters tools it says that
I am using a adapted version ofhttp://www.mikesdotnetting.com/Article/45/Programmatically-accessing-data-from-DataSource-controlsDon't we need something like a closing-routine / close connection command after getting data from the database?If yes: What is the correct closing command?
Is this necessary to open and close connection when i am using SqlDataAdapter and DataSet to get data from from table from databse in sql server? Which one will be better to use in the following code. Code1 or Code2.
Code: 1 With open and colse connection
public DataSet GetFAcadSlidingImage() { SqlConnection con = GetConnection(); cmd = new SqlCommand("Pro_GetFAcadSlidingImage", con); cmd.CommandType = CommandType.StoredProcedure;
[Code].....
Code:2 Without open and colse connection
public DataSet GetFAcadSlidingImage() { SqlConnection con = GetConnection(); cmd = new SqlCommand("Pro_GetFAcadSlidingImage", con); cmd.CommandType = CommandType.StoredProcedure;
I'm getting "This SqlTransaction has completed; it is no longer usable" exception when try to commit my transaction after sqlreader is close.Here is the code sample
[Code]....
...so when I get to commit the transaction it raises the mentioned exception: "This SqlTransaction has completed; it is no longer usable". I have also noticet that Command.Transaction becomes NULL after reader.Close()My question is: Can I use SqlDataReader and SqlTransaction ? Maybe to use BeginExecuteReader and EndExecuteReader ?
I can check whether username exists or not successfully but not for email. any ideas why it isn't working? Error message was that i did not close my connection. using System;
does anyone have any working code that uses javascript to open and close a cpe when the CPE is in a masterpage? It seems like the javascript never is able to find the CPE when it is on a master page. I have an DropDownList on the page and when certain items are selected, i want to collapse or expand when others are selected. It seems to work fine on a regular page, but not when it is a page nested in a master page. It is adding a suffix to the CPE and javascript is unable to find it.