471,334 Members | 1,398 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,334 software developers and data experts.

Local & remote db server - the differences... please help!

Hi everyone,
Hope you can help me with this one. We are doing a batch process on
both a local server and remote. By local I mean the db server is on
the same box and by remote I mean the db server is on another computer
(but in the same room, so not too far away). The db is: Microsoft SQL
Server 2005 - 9.00.3042.00
We have noticed that the remote server takes a lot longer that the
local. A lot longer. We are trying to think of the different ways that
could account for this. Essentially identify the difference between
local and remote connections in ASP.NET 3.0.
Yes, I know what your thinking - its the network. No, the network is
fine - its massive.

I would greatly appreciate any suggestions/comments/ideas/
possibilities code-diagnostics that you may be able to offer. i'm
really stuck. Cant't figure out why its taking so long...
Could it be a paremeter or somethign in the connection pool or is the
connection pool the same for local and remote. These are the things i
don't know about...

Thanks,
Al.
Jun 27 '08 #1
3 1671
On May 6, 9:27 am, "almu...@altavista.com" <almu...@altavista.com>
wrote:
Hi everyone,

Hope you can help me with this one. We are doing a batch process on
both a local server and remote. By local I mean the db server is on
the same box and by remote I mean the db server is on another computer
(but in the same room, so not too far away). The db is: Microsoft SQL
Server 2005 - 9.00.3042.00

We have noticed that the remote server takes a lot longer that the
local. A lot longer. We are trying to think of the different ways that
could account for this. Essentially identify the difference between
local and remote connections in ASP.NET 3.0.
Yes, I know what your thinking - its the network. No, the network is
fine - its massive.

I would greatly appreciate any suggestions/comments/ideas/
possibilities code-diagnostics that you may be able to offer. i'm
really stuck. Cant't figure out why its taking so long...
Could it be a paremeter or somethign in the connection pool or is the
connection pool the same for local and remote. These are the things i
don't know about...

Thanks,
Al.
I would start off by ruling out the network.
does your batch process involved a lot of data?
what does the batch process do? is it .net app or a sql job?
you can try to run the batch prcess locally on the remote machine. it
it works fine then it means that "remote" thingy has got something to
do with it.

what about the two dbs? are they same? do they have the same data? are
the indices up to date? on both?
Jun 27 '08 #2
al*****@altavista.com wrote:
Hope you can help me with this one. We are doing a batch process on
both a local server and remote. By local I mean the db server is on
the same box and by remote I mean the db server is on another computer
(but in the same room, so not too far away). The db is: Microsoft SQL
Server 2005 - 9.00.3042.00

We have noticed that the remote server takes a lot longer that the
local. A lot longer. We are trying to think of the different ways that
could account for this. Essentially identify the difference between
local and remote connections in ASP.NET 3.0.
Yes, I know what your thinking - its the network. No, the network is
fine - its massive.

I would greatly appreciate any suggestions/comments/ideas/
possibilities code-diagnostics that you may be able to offer. i'm
really stuck. Cant't figure out why its taking so long...
Could it be a paremeter or somethign in the connection pool or is the
connection pool the same for local and remote. These are the things i
don't know about...
Even though the network is fine, then going out on the wire would be
expected to be slower than something that is all happening in memory
(I don't know to what extent Windows TCP/IP optimizes local connections
but I am sure that it is faster).

Arne
Jun 27 '08 #3
If you could explain what are you doing and what is the environment in which
the application/set of code runs, that would enable us on helping you.

<al*****@altavista.comwrote in message
news:fb**********************************@l42g2000 hsc.googlegroups.com...
Hi everyone,
Hope you can help me with this one. We are doing a batch process on
both a local server and remote. By local I mean the db server is on
the same box and by remote I mean the db server is on another computer
(but in the same room, so not too far away). The db is: Microsoft SQL
Server 2005 - 9.00.3042.00
We have noticed that the remote server takes a lot longer that the
local. A lot longer. We are trying to think of the different ways that
could account for this. Essentially identify the difference between
local and remote connections in ASP.NET 3.0.
Yes, I know what your thinking - its the network. No, the network is
fine - its massive.

I would greatly appreciate any suggestions/comments/ideas/
possibilities code-diagnostics that you may be able to offer. i'm
really stuck. Cant't figure out why its taking so long...
Could it be a paremeter or somethign in the connection pool or is the
connection pool the same for local and remote. These are the things i
don't know about...

Thanks,
Al.

Jun 27 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Leonid | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.