A SP with join's between tables of 2 SQL 2000 linked server used to work
relatively quick.
Since a few weeks the same SP that runs on +/- the same amount of data takes
much more time (43 sec).
When i copied the DB so that the SP should run on the same server it takes
only 13 seconds.
Probably the customer installed on the server but obviously they deny that
:)Hi
Run sp_updatestats (on both servers) and see what is going on
"Chedva" <chedvag@.matrix-it.co.il> wrote in message
news:eoueGxomGHA.1912@.TK2MSFTNGP02.phx.gbl...
>A SP with join's between tables of 2 SQL 2000 linked server used to work
> relatively quick.
> Since a few weeks the same SP that runs on +/- the same amount of data
> takes
> much more time (43 sec).
> When i copied the DB so that the SP should run on the same server it takes
> only 13 seconds.
> Probably the customer installed on the server but obviously they deny that
> :)
>sql
Showing posts with label performantce. Show all posts
Showing posts with label performantce. Show all posts
Monday, March 26, 2012
LINK SERVER BAD PERFORMANTCE
LINK SERVER BAD PERFORMANTCE
A SP with join's between tables of 2 SQL 2000 linked server used to work
relatively quick.
Since a few w
s the same SP that runs on +/- the same amount of data takes
much more time (43 sec).
When i copied the DB so that the SP should run on the same server it takes
only 13 seconds.
Probably the customer installed on the server but obviously they deny that
:)Hi
Run sp_updatestats (on both servers) and see what is going on
"Chedva" <chedvag@.matrix-it.co.il> wrote in message
news:eoueGxomGHA.1912@.TK2MSFTNGP02.phx.gbl...
>A SP with join's between tables of 2 SQL 2000 linked server used to work
> relatively quick.
> Since a few w
s the same SP that runs on +/- the same amount of data
> takes
> much more time (43 sec).
> When i copied the DB so that the SP should run on the same server it takes
> only 13 seconds.
> Probably the customer installed on the server but obviously they deny that
> :)
>
relatively quick.
Since a few w
much more time (43 sec).
When i copied the DB so that the SP should run on the same server it takes
only 13 seconds.
Probably the customer installed on the server but obviously they deny that
:)Hi
Run sp_updatestats (on both servers) and see what is going on
"Chedva" <chedvag@.matrix-it.co.il> wrote in message
news:eoueGxomGHA.1912@.TK2MSFTNGP02.phx.gbl...
>A SP with join's between tables of 2 SQL 2000 linked server used to work
> relatively quick.
> Since a few w
> takes
> much more time (43 sec).
> When i copied the DB so that the SP should run on the same server it takes
> only 13 seconds.
> Probably the customer installed on the server but obviously they deny that
> :)
>
LINK SERVER BAD PERFORMANTCE
Hi
Run sp_updatestats (on both servers) and see what is going on
"Chedva" <chedvag@.matrix-it.co.il> wrote in message
news:eoueGxomGHA.1912@.TK2MSFTNGP02.phx.gbl...
>A SP with join's between tables of 2 SQL 2000 linked server used to work
> relatively quick.
> Since a few weeks the same SP that runs on +/- the same amount of data
> takes
> much more time (43 sec).
> When i copied the DB so that the SP should run on the same server it takes
> only 13 seconds.
> Probably the customer installed on the server but obviously they deny that
>
>A SP with join's between tables of 2 SQL 2000 linked server used to work
relatively quick.
Since a few weeks the same SP that runs on +/- the same amount of data takes
much more time (43 sec).
When i copied the DB so that the SP should run on the same server it takes
only 13 seconds.
Probably the customer installed on the server but obviously they deny that
|||Hi
Run sp_updatestats (on both servers) and see what is going on
"Chedva" <chedvag@.matrix-it.co.il> wrote in message
news:eoueGxomGHA.1912@.TK2MSFTNGP02.phx.gbl...
>A SP with join's between tables of 2 SQL 2000 linked server used to work
> relatively quick.
> Since a few weeks the same SP that runs on +/- the same amount of data
> takes
> much more time (43 sec).
> When i copied the DB so that the SP should run on the same server it takes
> only 13 seconds.
> Probably the customer installed on the server but obviously they deny that
>
>
Run sp_updatestats (on both servers) and see what is going on
"Chedva" <chedvag@.matrix-it.co.il> wrote in message
news:eoueGxomGHA.1912@.TK2MSFTNGP02.phx.gbl...
>A SP with join's between tables of 2 SQL 2000 linked server used to work
> relatively quick.
> Since a few weeks the same SP that runs on +/- the same amount of data
> takes
> much more time (43 sec).
> When i copied the DB so that the SP should run on the same server it takes
> only 13 seconds.
> Probably the customer installed on the server but obviously they deny that
>
>A SP with join's between tables of 2 SQL 2000 linked server used to work
relatively quick.
Since a few weeks the same SP that runs on +/- the same amount of data takes
much more time (43 sec).
When i copied the DB so that the SP should run on the same server it takes
only 13 seconds.
Probably the customer installed on the server but obviously they deny that
Run sp_updatestats (on both servers) and see what is going on
"Chedva" <chedvag@.matrix-it.co.il> wrote in message
news:eoueGxomGHA.1912@.TK2MSFTNGP02.phx.gbl...
>A SP with join's between tables of 2 SQL 2000 linked server used to work
> relatively quick.
> Since a few weeks the same SP that runs on +/- the same amount of data
> takes
> much more time (43 sec).
> When i copied the DB so that the SP should run on the same server it takes
> only 13 seconds.
> Probably the customer installed on the server but obviously they deny that
>
>
Labels:
chedva,
database,
hirun,
ilgt,
link,
ltchedvagmatrix-it,
microsoft,
mysql,
oracle,
performantce,
server,
servers,
sp_updatestats,
sql
Subscribe to:
Posts (Atom)