like operate giving timeout while doing wild search for 'ABCZ%'

March 10, 2010, 12:34 am

Hello all

i am not sure what is going wrong here. i might be missing some basics, going bonkers. need some desperate help to find out the reason for strange behavior. It could be service pack issue, but incase its not...

environment:

VB6.0

sql server 2000 sp3

database is on d drive on 2003 server with more than 10GB free space

database has 1 table t1, around 18 column/fields all varchar with 1 bigint field which is primary key, more than 28 million records

7 indexes on 7 different fields - one each

[in context to example below] field3 varchar(10) - (not primary key, not foreign key, no default) - nonclustered index with fill factor = 90

Example:

connection timeout is set to 100 - using DAO

a) query used in the source - throws timeout / execution cancelled error - select field1, field2 from t1 where field3 like 'ABC 0HZ%'

b) query used in the source - works fine (without Z) - select field1, field2 from t1 where field3 like '0H%'

c) query used in the source - works fine (without %) - select field1, field2 from t1 where field3 like 'ABC XYZ 0HZ' or - select field1, field2 from t1 where field3 = 'ABC XYZ XYZ 0HZ'

Problem:

query a above throws timeout error while using like operator to do a wild search for input data ending with Z

queries b and c works fine

Solutions tried:

  - Sql server restarted
  - rebuild index - dropped and recreated
  - database detached and attached again
  - database shrinked after dropping indexes

Hope the point clear - Any help would be highly appreciated

Thanking you in advance

regards ash

↧

Transaction time-out after

March 11, 2010, 9:40 pm

≫ Next: SSRS 2008 Time out for lengthy queries

≪ Previous: like operate giving timeout while doing wild search for 'ABCZ%'

Hello Friends,

Just wanted to know the parameter in sql 2000 which is equivalent to "Transaction time-out after" (default 30 sec) in sql 2005 server.

Thanks & Regards, Sashikanta Mishra.

↧

SSRS 2008 Time out for lengthy queries

April 8, 2010, 4:02 am

≫ Next: sql server 2005

≪ Previous: Transaction time-out after

We have several reports on SSRS 2008 which we have accessing through a c# web page using reportviewer control. One report, takes around 10 minutes to run the query is getting timed out aftrer executing the query. I have tried out the time out settings of report data source, site settings of the report manager and the particular report, the time out of IIS in which the application is hosted and the connection time out of shared data source.

Even after that report failed. The query is working because it is generated using stored procedure and creates a named temporary table(tmp_123) for reporting. After running the query I am able to view the rows in the table.

Please advise what to do in detail.

↧

sql server 2005

October 24, 2010, 4:13 pm

≫ Next: Timeout during DBCC CHECKDB

≪ Previous: SSRS 2008 Time out for lengthy queries

**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.** hi team this is the error oi am getting while accessing in application, can any one help me

↧

Timeout during DBCC CHECKDB

May 9, 2011, 8:56 pm

≫ Next: Troubleshoot: "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding"

≪ Previous: sql server 2005

Hi, I have 2 jobs for DBCC CHECKDB on a SQL 2000 server. 1st job runs DBCC Checkdb for master 2nd job runs DBCC Checkdb for a user database the job for master database runs just a couple of mins before the other job. It completed successfully while the 2nd job FAILED due to "Timeout expired" error?? What can be the reason?

↧

Troubleshoot: "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding"

June 8, 2011, 11:32 pm

≫ Next: Urgent Help required The semaphore timeout period has expired. [SQLSTATE 08S01]

≪ Previous: Timeout during DBCC CHECKDB

We have this virtualised(VMWare) Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) build 7600, on Windows 2008 r2 Enterprise. We have this very nagging problem of "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding" error message using SSMS just to **login**. UPDATE: We're using mixed authentication. It only happens when connecting through SSMS remotely, but if I RDP inside and connect it doesn't happen. I've tried connecting via IP but it also gives the same error What I have done in hopes of resolving this issue: 1. Reduce the number of users under the sysadmin roles(http://support.microsoft.com/kb/934751) 2. Check, via the sysads, if firewall is blocking the port or dropping them. They said its not. 3. Installed sp_whoisactive just to make sure there's no long running query that might contribute to this. Found nothing. 4. Check if SQL Browser is running and is active, both are true. 4. 6. Disabled for the meantime CDC jobs, just to eliminate it from equation. I'm connecting via SSMS 2008 r2/ SSMS 2008 and sqlcmd all return the same message. I'm stumped and its intermittent , do you have any idea in troubleshooting this? *----

↧

Urgent Help required The semaphore timeout period has expired. [SQLSTATE 08S01]

June 10, 2011, 9:51 pm

≫ Next: time calculation in sql 2005

≪ Previous: Troubleshoot: "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding"

I am getting the following error for the sqlserver agent (SQL SERVER 2005 SP2). **[298] SQLServer Error: 121, TCP Provider: The semaphore timeout period has expired. [SQLSTATE 08S01] [298] SQLServer Error: 121, Communication link failure [SQLSTATE 08S01] [298] SQLServer Error: 16389, Communication link failure [SQLSTATE 08S01] [298] SQLServer Error: 258, Unable to complete login process due to delay in prelogin response [SQLSTATE 08001]** This set of error I am getting quite frequently.. This is a production Database..And I need provide the Root Cause of this problem as SQL Server Agent goes down with this error. Not sure wheather it's related to the NIC/SAn or some network related problem. Please help. Many thanks in advance. Regards Aniruddha

↧

time calculation in sql 2005

June 22, 2011, 4:33 am

≫ Next: Login timeout error in SQL Server 2008 R2

≪ Previous: Urgent Help required The semaphore timeout period has expired. [SQLSTATE 08S01]

I am very new SQL. In my office i need to calculate the following from the main Server and display it to the client PCs. 1. Display the No. of Block ( 1 to 96) Every hour is divided into 15min blocks, 96 blocks in a day. 2. Display the block time as say 03:00 to 03:15 at say 3:10 hrs 3. Calculate the time left(in mm:sec format ) from the current time Please help. Thanks in advance.

↧

Login timeout error in SQL Server 2008 R2

September 26, 2011, 9:22 pm

≫ Next: SQL job failure due to timeout

≪ Previous: time calculation in sql 2005

Hi, I am not able to connect to a SQL instance (SQL 2008 R2) remotely properly. I am able to connect to it locally. Actually, remotely we CAN connect but only when we keep the Connetion timeout settings to something like 1500 secs. The connection is too slow and I cannot run any queries using Management studio. There is NO network issue as I am able to connect to other servers in that network. When I try OSQL/SQLCMD I get the below error: D:\Documents and Settings\>osql /S ,1433 /E [SQL Native Client]TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [SQL Native Client]Login timeout expired [SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. I have tried without PORT number too, same result. SQL browser is working, I have added SSMS,SQLCMD/OSQL to firewall exceptions on the target server. Any idea, what could be the problem???

↧

SQL job failure due to timeout

December 19, 2011, 8:13 pm

≫ Next: Timeout expired for Windows Authentication Only

≪ Previous: Login timeout error in SQL Server 2008 R2

Hi All, I have some jobs (in the form of .EXE executions) which connect to 2 or sometimes 3 SQL servers (all SQL 2005) However, these jobs seem to fail occasionally (every alternate day) due to errors similar to the one below: **Error messages (at different times):** 1. An error occured at database level : System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 2. An error occured at database level : System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding The job runs some stored procedures. The server on which the databases and instance is located have the below memory allocation: Instance 1 - 750 Instance 2 - 700 Instance 3 - 128 Max RAM on server: 3.75GB The connection is made using connection strings. The job is executed from one server and connects to SQL instances residing on another physical server. Questions: 1. Can the timeout errors be related to low memory allocation ? 2. If not, what may the reason of the error?

↧

Timeout expired for Windows Authentication Only

February 9, 2012, 3:37 pm

≫ Next: Sqlserver 2008 Backup restoration failing

≪ Previous: SQL job failure due to timeout

After rebuilding a server, I am consistently getting "Timeout Expired" messages when trying to connect to SQL Server through SSMS with windows authentication from a machine other than the server itself. I can connect SSMS from another machine if I user SQL Server authentication with a username and password. I can also use SSMS with Windows Authentication on the Server itself either by connecting with RDP or sitting down directly at the server. I looked at [troubleshoot-timeout-expired-the-timeout-period-el][1] on this site, but that didn't quite seem to apply. I also looked at [Troubleshooting: Timeout Expired][2] but those suggestions did not resolve this issue. This does not seem to be a DNS issue since I can connect to the Server through RDP and the shared folders come up over the network (not to mention I can connect to SQL Server with SQL Server authentication). It does not seem to be a problem with my domain account since I can log in with Windows authentication from SSMS on the server. I double checked the firewall settings and even tried (*temporarily!*, on a server with no route to the internet) disabling the firewall. And naturally, I have verified that I have the proper server name. So, any ideas what could cause this? [1]: http://ask.sqlservercentral.com/questions/41373/troubleshoot-timeout-expired-the-timeout-period-el.html [2]: http://msdn.microsoft.com/en-us/library/ms190181.aspx

↧

Sqlserver 2008 Backup restoration failing

June 5, 2012, 1:43 am

≫ Next: connection timeouts in sql server 2000

≪ Previous: Timeout expired for Windows Authentication Only

I do Sqlserver 2008 database backup to the the C drive of my Central Server. On daily basis the system admin team do a full system backup of this server to Network Driver. I Then Copy the sqlserver database from the network drive to the C driver of Another Server and do the restoration. The Current Database size of the my Database is 118GB. When i trying to Restore, i browse to the location of database on the C Drive and Select the full backup file, it fails to read. i check the window task Manager it says DBXYZ is not responding. I but when i try to select the log it works. I suspect the problem has to do with the size of the database.(My sqslerver is an Enterprise edition. Please help.Tell me how you resolve yours.

↧

connection timeouts in sql server 2000

January 1, 2013, 9:09 am

≫ Next: Performance issue after restart

≪ Previous: Sqlserver 2008 Backup restoration failing

Hello all, Happy new year!!! we are having few sql2000 instances. Recently we are facing the connection timeouts and all the applications connecting to SQL Server are getting hanged. After the server restart, everything seems normal.. only thing i got from the cient team is ... [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00] [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00] [382] Logon to server '(local)' failed (JobManager) [298] SQLServer Error: 11, General network error. Check your network documentation. [SQLSTATE 08001] what might be the cause ?? may I please How to dig into this issue ?

↧

Performance issue after restart

January 7, 2013, 9:06 am

≫ Next: query timeout expired problem

≪ Previous: connection timeouts in sql server 2000

Hi, I have got a very confusing problem. I have a stored procedure which is internally calling a number of child sps. some among them are called in a loop too. The issue i am getting is that the sp takes more than 3 minutes to complete which is not allowable for the application, which gets time out error. I found that if i run the sp for query analyser, for the first time it gives 3 minutes, but if we run it again, the time take will get reduced to 10 seconds only. For my wonder i found that the sp takes 3 minutes for every restart of my server (or restart of sql service). I am totally clueless. Can anybody help me on what could be the root cause of the issue. Statistics or Indexes are not rebuild during restart as per my knowledge. I have found many times that performance is increasing after restart. But this is for the first time i come across such a condition. Please put some lights on this issue. Thanks in avance.. Paps

↧

query timeout expired problem

March 14, 2013, 1:16 pm

≫ Next: How to find out Stored procedures, function and triggers which are timing out?

≪ Previous: Performance issue after restart

TIA for your help. I am using an OleDbTransaction in `ASP.net`, Page Language="vb", the database is SQL Server 2008 R2 Express. I get a "query timeout expired", and the transaction is rolled back, then the webpage user has to try again, and usually it succeeds. Is it a race condition that is causing this? Inside the transaction there are Inserts on 12+ tables, Updates on 3+ tables, and 7+ Selects. The Selects are generally used to get the IDENTITY ID of the Insert that just happened. The query timeout always happens on one specific Insert in the middle of the transaction. The table is one of our busiest. The time taken up until that Insert is generally 1/100th of a second. Does an insert inside of an OleDbTransaction place a lock on the last page of the table? So that another user trying to insert will get the timeout? It is possible that two different users are getting the same PublicID (see below code) and trying to use it. There is a UNIQUE index on tblContracts.PublicID. Is it something to do with my insert being too slow because of my indexes being wrong for that table? More detail. The series of events looks something like Sub ConvertAppCall(ByRef udtErrorReport As ErrorReport) Dim conDB As OleDbConnection Dim traDB As OleDbTransaction Dim cmdDB As OleDbCommand Dim prmDB As OleDbParameter Dim drdDB As OleDbDataReader conDB = New OleDbConnection(ConfigurationSettings.AppSettings("MDB")) conDB.Open() traDB = conDB.BeginTransaction() Try ...inserts/selects... then the statements with a ** are inside a utilities file, having passed the OleDbConnection and OleDbTransaction **SELECT TOP 1 PublicId FROM tblContracts ORDER BY PublicId DESC **then use OleDbDataReader to read the PublicID and add 1 to it, then **UPDATE [tblLasts] SET LastPublicId = " & lngPublicId then back on the main page, immediately do this INSERT INTO [tblContracts] (using the lngPublicID) cmdDB = New OleDbCommand(strSQL, conDB) prmDB = New OleDbParameter prmDB.ParameterName = "ContractNotes" prmDB.Value = IIf(txtContractNotes.Text.Length > 0, txtContractNotes.Text, System.DBNull.Value) prmDB.DbType = System.Data.DbType.[String] cmdDB.Parameters.Add(prmDB) cmdDB.Transaction = traDB cmdDB.ExecuteNonQuery and if any query timeout happens, it happens here

↧