Timeout error - - after restored sql 2008 db to sql 2012

Question

0.00/5 (No votes)

See more:

Below is the error message:

HTML

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

Few days ago, I migrated our server, old server use IIS 7 + Sql Server 2008 R2

new Server: IIS 7 + Sql Server 2012

after that, When I connect to Sql Server 2012 , some reports or functions occurs TimeOut Error,

But I switch to Sql Server 2008.

And I set 1hour for timeout in system's config. It still the same error.

Is there any settings for the Sql Server 2012? Can anyone help me!!

Posted 6-Jan-14 17:34pm

chenghuichao

Add a Solution

2 solutions

Solution 1

Has your connection string changed ? How long does it take to time out ? What's the exact error ?

I'd increase the timeout via the connection string and see what happens then.

Posted 6-Jan-14 17:39pm

Christian Graus

Comments

chenghuichao 6-Jan-14 23:44pm

Yeah,I have changed the connection string, and add the 'Connect Timeout=0;'. In my system, only report and big data functions occurs this error. my database is about 12G, but there is no timeout error when I use Sql Server 2008.

Christian Graus 6-Jan-14 23:48pm

Is it the same machine ? How long did these functions take on SS2008 ?

Can you go back to SS2008 ? Why were you moving ?

chenghuichao 6-Jan-14 23:55pm

A new Cloud Server, Old server take 3 min, new server I run in SSMS it's about 6 min or more.

My vendor said they can not found SS2008, only have SS2012.

Christian Graus 7-Jan-14 0:03am

OK, so SQL Server is NOT the only thing changed. It's probably not the issue then. It's the whole server structure surrounding SS on your new platform that is the issue.

chenghuichao 7-Jan-14 0:10am

maybe, but how can I find out the issue? I have checked the IIS, SS2012 & Server resource few days, it sill the same, I have got headache.

Christian Graus 7-Jan-14 0:12am

Install SS2012 on your old server, you need to remove variables. Test so that the ONLY difference is SQL Server. If it's not slower, then that's not the issue.

chenghuichao 7-Jan-14 0:16am

Thanks so much, I'll try this.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

thatraja · Accepted Answer · 2014-01-06T20:25:00

Many reasons for this error. Check these

Dirty ways
Increase timeout for SQL connection[^]
Increase timeout for SQL command[^].

Good ways
Use SQL Server Profiler[^]
How to identify SQL Server performance issues, by analyzing Profiler output?[^]
SQL Server Best Practices[^]

Optimize the database
Top 10 steps to optimize data access in SQL Server: Part I (use indexing)[^]
Top 10 steps to optimize data access in SQL Server: Part II (Re-factor TSQL and apply best practices)[^]
Top 10 steps to optimize data access in SQL Server: Part III (Apply advanced indexing and denormalization)[^]
Top 10 steps to optimize data access in SQL Server: Part IV (Diagnose database performance problems)[^]
Top 10 steps to optimize data access in SQL Server: Part V (Optimize database files and apply partitioning)[^]