Hi, for some time now we've experienced an issue with a particular customer where they have intermittent performance problems. The application appears to hang for about 20 seconds and then comes back to life.We have traced the issue to where the application is receiving a'timeout expired' error which happens after 20 seconds.The point in the code where the 'timeout expired' error appears is on the 'connection open' command i.e.Set mcnx = New ADODB.Connectionmcnx.ConnectionString = txtConnectionString.Text mcnx.OpenOur connection string looks something like 'Provider=SQLOLEDB;Data Source=INSTANCE;Database=DATABASE;Timeout=0;User Id=USERID;Password=PASSWORD' - we're not using integrated security i.e. We use a named SQL account.The application can handle timeouts fine and obviously we could set the connection timeout to a few seconds to combat this but I'd really like to get to the bottom of the underlying problem.We get the same issues if we run the application on the server. Also we get the same issues across multiple PC's at exactly the same time.We also intermittently get the same error via Server Management Studio when running any type basic query. I'm particularly intrigued about this one because it's just SQL Server on it's own doing this.The queries we are running typically take less than a second so we know it's not a database performance issue.The server has 70Gb of memory and 16 cores - 4 allocated to the O/S and the other 12 allocated to SQL Server.Any help or suggestions would be gratefully received.
Tapi sering kali karena posisi kamu berada pada jarak jauh mengakibatkan koneksi Wifi internet menjadi lemah dan disini kami akan membagikan memperkuat sinyal Wifi dengan CMD yang tentunya sangat mudah untuk dilakukan dan jika koneksi Wifi lemah maka kamu bisas gunakan cara berikut ini untuk laptop atau PC kamu. If My.Computer.Network.Ping('198.01.01.01') Then MsgBox('Server pinged successfully.' ) Else MsgBox('Ping request timed out.'
I see two possible problems. It could be a network problem unrelated to SQL Server. Are there any other network issues when this happens? Any interesting information in the Windows event logs?But assuming it's a SQL Server issue, my first guess is that something is happening on the SQL Server computer that uses a lot of resources. This could be something in SQL Server like a SQL Server backup, or it could be something happening in Windows,like a Windows backup.Is there any predictability to this? A scheduled job of some sort?Start a trace with SQL Server Profiler and if you can capture the event, you might find some particular query or workload is consuming resources.Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty.
![Coding Vb6 Untuk Cek Koneksi Internet Coding Vb6 Untuk Cek Koneksi Internet](/uploads/1/2/5/6/125629720/405483280.jpg)
![Coding vb6 untuk cek koneksi internet gratis Coding vb6 untuk cek koneksi internet gratis](/uploads/1/2/5/6/125629720/304550870.png)
Hi thanks for your feedback. We know that there are no network problems - this has been check by internal IT who manage the infrastructure and also by an external network engineer who we have brought in to diagnose the problem.The issue occurs mostly when there is user activity but I've seen the issue occur when there has been just a couple of users on the system.We have a test application which sends a very simple query to the server every few seconds and this suffers from the same issue. It appears that there is a problem when we try to make a connection to the server (this is before submitting the SQL command).This test application has the same issues regardless of whether it is run on a remote client or on the SQL server box itself.The other aspect to point out is that this issue affects all users at the same time regardless of which database they are connecting to.
It could be the production database or training database - the effect is the same.I've run server side traces (SQL profiler) and the only thing I can remotely match up with the issue is excessive 'audit logout' events which can take upto 12 seconds to run. Normally the duration against the audit logout is marginally (few milliseconds)longer than the query time. This could point towards the issue but unsure how to take this forward. I did look at whether any locks or blocking is occurring on the database and if this could be the cause. There are some deadlocks whichare being trapped but again nothing that ties in with when the issues occur.Other avenues we are looking into are AV (McAfee) issues, Firewall etc.
Backups don't appear to be having an effect because they're not running at the time that issues are experienced.Hopefully this provides more clues as to the problem.Thankyou. I'm assuming then that if we used an ip address that this would negate the dns issue?Yes, either a hard-coded IP or a local host file will address a name resolution issue. I suggest you use that only as a temporary fix until the underlying issue is addressed, though.I'll definitely be trying to ping the server when the issue occurs.
Would telneting to the ip and port number (1433) help identify if we connect to sql?The telnet to the SQL Server IP and port is an good way to verify SQL Server network connectivity. However, it will verify that SQL Server itself is responseive.Dan Guzman, SQL Server MVP, http://weblogs.sqlteam.com/dang/.
Have tried using the IP address solution but this has no effect.The ping and telnet commands run fine at the time of the issue.We have now noticed some lock timeouts on tempdb - in fact lots of them. From a profiler trace they point to object id 0 which I think means it is at database level.Could these be contributing or causing the problem?
I realised we were using tempdb a fair amount for some temporary table queries and cursors etc. But on this particular server we are getting the lock timeouts.The other thing to mention about this particular setup is that there are 16 cores with 4 of these allocated to the OS. The MAXDOP is set to 0. All of our other installations are dual core or 4 core so wondered whether this could be having animpact?Thanks.