New DB Server throws connction time out problem

Question

2.00/5 (1 vote)

See more:

we are planed to change our live site from one server to new server .
our old server had sql server 2008 and iis7 service pack 1
now we are moving our live files to a new server and db to another new server
our new db server contains Sql Server 2012 and our new live site server has iis8.
while i try to connect my database server from my live site it throws connections time out error.
but we are using already working live server files and db in our new servers,but the different is in our previous configuration we have single server for db and iis, but now we have separate servers.

i ve connected new db server with my local development environment files but it returns the same time out error, so i can understand the problem is beacause of new db server but, i don't ve any idea where i am struck with up

i have some doubts on that
1.We are using linq for our data processing.we dragg and drop the table from server explorer which are all created from sql server 2008, so this dbml not supporting the new sql server 2012 table and databases
2.or else i need to do any other configuration changes in my new servers
3.Is there any permission problem

its eating my time, please any on help me.

Posted 1-Sep-13 23:31pm

arunraju

Add a Solution

Comments

Bala Selvanayagam 2-Sep-13 5:36am

It could be a firewall blocking the client calls on the server ? also there is an option in SQL server to grant access to remote call, may be this is not ticked

Try doing a simple ODBC connection (from the control panel) of your workstation and see that works first to eliminate where the issue is ?

arunraju 2-Sep-13 5:53am

Hi Bala,
Thanks for your support ,i can retrieve some basic data from that new server but during the bulk records retrieving process only am getting this error..
do u ve any suggestion on this...?

Bala Selvanayagam 2-Sep-13 6:11am

Hi Arunraju

You have to narrow where the issue is ? (SQL SERVER/WEB SERVER)

Since you are able to recreate the issue in your development environment, could you have a break point on the SQL server execution where it throws the error

1. Get the SQL statement, directly execute on the database server and see how long it takes to execute

2.Run it through the IIS web server, you know how long it took in the SQL server already and now you can calculate how long it takes in the web server.

If the SQL server is taking longer, then it could be an indexing issue (have you migrated all your indexes into the new server ?) and also you are saying that the database before was a single one and now multiples...How does it work

If the delay is in the IIS server, check the server configuration

Bala

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)