i have a web application that use a MySql DataBase. In a page, i have used the sqlDatasource control. The problem is that the conection with the database doesn't closed and i have a lot of open conections until show me the error that says me that the conection pool is full.
[code]....
I'm getting the following error after uploading my site on live server:Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.i'm using the following code:
public static IQueryable<Property> Properties(string name, string city, string state, int pageIndex, int pageSize, ref int total)
{
ServerDataContext server = new ServerDataContext();
total = server.Properties.Count(x => x.Name.StartsWith(name) && x.City.StartsWith(city) && x.State.Contains(state));
return server.Properties.Where(x => x.Name.StartsWith(name) && x.City.StartsWith(city) && x.State.Contains(state)).Skip(pageIndex * pageSize - pageSize).Take(pageSize);
}
I need to set the SQLDataSource connection string on the fly. Right now, this is what I have:
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
OnSelecting="SqlDataSource1_Selecting"
SelectCommand= (working select stmt here)</asp:SqlDataSource>
Then, I have this:
[code]....
I am using a AccessDatasource for getting values from a accessdatabase for a Dropdown list. After i load the page and close it, a .ldb file is created. After wards i am not able to open the database manually. How to close the connection. I have given Network service Modify access [URL] to share permission, still no go.
View 3 Replies how to convert this AccessDataSource to a SqlDataSource connection?Thanks.CodePrivate Function GetNotes(ByVal id As String) As Object
Dim ds As New AccessDataSource()
ds.DataFile = AccessDataSource1.DataFile[code].....
I have a website with high traffic.
Maybe I will increase minimum connections pool, to 100.
This is too high? Website have 10000 pageviews/day
I'm having some problems with connections to an SQL database not closing after being opened, which is maxxing out the pool and causing the site not to load any of the dynamic content (until eventually unused idle connections get close, as the problem seems to go away after a while).
I've been through my code several times and can't figure out where things are not being closed properly.
Is there a surefire way to make sure these connections are properly closed? Or to pinpoint where the problem lies?
Most places in the site I am using ObjectDataSource. You don't need to close a connection when using that, do you?
Where ObjectDataSource isn't used, a developer wrote this method and put it in a class file called "common.cs":
[Code]....
I searched the entire solution for every instance of "common.openDatabase()", and where it occurs I make sure there is a "cmd.Connection.Close();" that follows.
Am I missing something or doing it wrong?
Here's an example of where a db connection gets opened and then (purportedly) closed:
[Code]....
I should be closing my readers and connections in a more robust way? Some of my questions are:
- If a try-catch block is used, should the closures be done in the Finally section? Or in the main Try section?
- Should all closures assess whether or not the control is already open before closing (to prevent error)? (see closure of conn below)
- Are there any other preferable ways of handling this? Trying to improve my code!
[Code]....
I am trying to tie a sqlDatasource to a Stored Procedure. The stored procedure looks like...
[Code]........
I've been playing about for ages in an attempt to get a simple bit of code that can detect whether or not SQL Server is listening remotely or just locally.. My pretty lame attempt so far is as follows:
[Code]....
I'm sure there must be a better way to do this! Aside from the fact that this code fails to work properly.
sp.IPAddresses contains:
- 127.0.0.1
- 0.0.0.0
- 10.0.0.10
When I used Surface Area Manager > Surface Area Configuration for Services and Connections and set Remote Connections to "Local connections only" sp.IPAddresses still contains the same addresses.
My lecturer insists that a web site should NOT have a static SQL connection as its not good practice (didn't explain why) but then I thought that if one makes instances of an SQL connection everytime I want to save, delete or edit then surely thats a bottleneck as I would need to everytime establish a connection and then do the save process. From what I have read online, the process of establishing a connection to the server is the longest (about 5 to 10ms)...
How would one manage their SQL connection. At the moment I do something like:
[Code]....
the SQL connection option ARITHABORT is OFF for OLEDB connections, which I assume Linq To SQL is using. owever I need it to be ON. The reason is that my DB contains some indexed views, and any insert/update/delete operations against tables that are part of an indexed view fail if the connection does not have ARITHABORT ON. Even selects against the indexed view itself fail if the WITH(NOEXPAND) hint is used (which you have to use in SQL Standard Edition to get the performance benefit of the indexed view).Is there somewhere in the data context I can specify I want this option ON? Or somewhere in code I can do it??I have managed a clumsy workaround, but I don't like it .... I have to create a stored procedure for every select/insert/update/delete operation, and in this proc first run SET ARITHABORT ON, then exec another proc which contains the actual select/insert/update/delete. In other words the first proc is just a wrapper for the second. It doesn't work to just put SET ARITHABORT ON above the select/insert/update/delete code.
View 4 RepliesI just want to know, What parameters or attributes should be taken in connection string so as to handle high traffic enterprise applications? Like in general we use server, initial catalog, userid, passwd. Some times we add timeout , and in some scenario pool etc. But i don't know what attributes should i take in as my common practice apart from above.
View 3 RepliesI've been getting this error recently, after several reloads of the same page:
System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached So I am thinking there must be some queries or calls in the app I used incorrectly that causes them not to release the connection. Is there any tools out there that allows me to somehow peek into the pool to see who is hanging on to what?
web service show me this errorFailureA 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) App_Code.d-vwopz6my sql version in 8.00.2039 how to configure SQL 8.00.2039 to allow remote connections
View 2 RepliesWe have developed web application using Asp.net, C# and SQL Server. However, When viewing the Process Info Tool for MS SQL Server, we see lots of processes (150-1000+) with Status = 'sleeping' and Command = 'AWAITING COMMAND' (Application = '.Net SqlClient Data Provider')The DataReaders and Connections are all being closed, but still the sleeping connections are accumulating. The problem becomes so severe that we finally get a "General Network Error" or a "Internal system error" and if we restart IIS. We have tested a lot but no success.
View 5 RepliesI have created web application and wrote single connection string in a class file hosted at live server.
I'm getting error sometime "Connection pool size exceeded".
My other applications are hosted on same server [server1] and all application hit same server [server2] having database. Is it mean, my every application using same connnection pool because of same IIS or same memory and encountered error said "Connection pool size exceeded".
How can I get rid of this problem ? (I have already tried manipulation of pool size)
I am working on a web application now a days, when i have uploaded it on server it creates exception message ,"connection Pool max size", but i have opened and closed connection properly.
View 1 RepliesI'm trying to make sure a block of code behind properly closes a connection to SQL after it's finished. But when I add the line "cmd.Connection.Close();" Visual Studio underlines "cmd" in green and says "unreachable code detected" What does that mean and how do I correct it?
[Code]....
I think I have a problem that I never noticed before. I was just recently (as in tonight) shown the SQL Server Profiler. I noticed that on a video that I watched there profiler did not move unless there was a query to the database, thus making it easy to see what exactly was going on. When I opened mine for the first time and ran it I am getting 9 logs every say 5 seconds. They consist of;
Audit Logout
RPC:Completed
Audit Login
RPC:Completed
RPC:Completed
SQL: BatchStarting
SQL: BatchCompleted
SQL: BatchStarting
SQL: BatchCompleted
Does anyone know if this is normal or my database just working way to hard?
I just restarted the server and checked databases for active connections now that I know nothing is running, and found the one database that is causing the problem... ReportServer has 4 connections after my restart. Should I leave this alone? Is it normal to have this reporting constantly going on?
I am new to using ADOMD for accessing SSAS cubes. I am having an issue with concurrency. I am using ADOMD to connect to SSAS 2005 in an ASP.Net 2008 application. When a user executes an MDX query and the ASP.net page opens an ADOMD connection, a second user that tries to execute an MDX query gets "a connection is already open" error. I don't understand how ADOMD works. Does it open only one connection for all users because ASP.Net is using a single account for all connections from the web server? I do not have this problem when using ADO.net in the same manner.
View 2 RepliesI am trying to make a small utility program to update a table in a database.
I made it as a asp.net 2008 project and connected to the development SQL server(which is located locally).It is working fine.
Then I try to move this to production, I realized that the sql server is located in another state and I can not connect it this way.( connection string from webconfig and open the connection).I can not change any configuration of the prod sqlserver.
I get error like sql server does not accept remote connection.( Verify that SQL Server is configured to allow remote connections).
I am trying to make a small utility program to update a table in a database.
I made it as a asp.net 2008 project and connected to the development SQL server(which is located locally).It is working fine.
Then I try to move this to production, I realized that the sql server is located in another state and I can not connect it this way.( connection string from webconfig and open the connection).I can not change any configuration of the prod sqlserver.
I get error like sql server does not accept remote connection.( Verify that SQL Server is configured to allow remote connections).
we are facing a big problem while running our website on the production server. We decided to start using the connection pool. we added these statments to AppSettings section at the configuration file to provide the connection information to the DataAccess Layer class to access our Oracle Database.
<appSettings>
<add key="ConnectionString" value="Data Source=server;User ID=*******; Password=********; Validate Connection=true; Max Pool Size=200; Min Pool Size=10;Connection Lifetime=120; Connection Timeout=60; Incr
[code]...
Does the same connection string used on two different physical servers hosting different web applications that talk to the same database draw connections from the same connection pool? Or are pooled connections confined to at the application level?
I ask because I inherited a 7 year old .NET 1.1 web application which is riddled with in-line SQL, unclosed and undisposed sql connection and datareader objects. Recently, I was tasked to write a small web app that is hosted on another server and talks to the same database and therefore used the same database connection string. I created a LINQ object to read and write the one table required by the app. Now the original .NET 1.1 app is throwing exceptions like
"Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached."
Maybe these are unreleated, but wanted to get your opinions to make sure I cover all my bases.