Hi,
We have asp application (ado connection) which connects to the sql server
2000 (sp3). There is one asp page which sequentially executes set of 6
stored procedures. When I execute same set of stored procedures in query
analyzer, I get response in less than 1 second.When application does that,
response gets back in 15-20 seconds (only when we have problem, otherwise in
2-3 seconds). In the trace, I noticed that each of these 6 stored procedures
(which btw use 1 connection object) gets a different SPID. Why is that?
Shouldn't they use the same SPID, if they use the same connection object
(executed sequentially!)?
Also, the trace shows that each of them gets executed almost instantly
(1ms), but between end of previous, and beginning of the next one, there is
delay of 2-3 seconds. During these 2-3 seconds, there is nothing going on on
the database server (very few events).
Does anybody have an idea?
ThanksPedja wrote:
> Hi,
> We have asp application (ado connection) which connects to the sql
> server 2000 (sp3). There is one asp page which sequentially executes
> set of 6 stored procedures. When I execute same set of stored
> procedures in query analyzer, I get response in less than 1
> second.When application does that, response gets back in 15-20
> seconds (only when we have problem, otherwise in 2-3 seconds). In the
> trace, I noticed that each of these 6 stored procedures (which btw
> use 1 connection object) gets a different SPID. Why is that?
> Shouldn't they use the same SPID, if they use the same connection
> object (executed sequentially!)? Also, the trace shows that each of them
> gets executed almost instantly
> (1ms), but between end of previous, and beginning of the next one,
> there is delay of 2-3 seconds. During these 2-3 seconds, there is
> nothing going on on the database server (very few events).
> Does anybody have an idea?
> Thanks
Are you sure you are not closing the connection and opening it up each time
your ASP code executed some SQL?
David Gugick
Quest Softwaresql
Showing posts with label server2000. Show all posts
Showing posts with label server2000. Show all posts
Monday, March 26, 2012
one ado connection object - multiple spids?
Labels:
ado,
application,
asp,
connection,
connects,
database,
executes,
microsoft,
multiple,
mysql,
object,
oracle,
page,
sequentially,
server,
server2000,
sp3,
spids,
sql
Tuesday, March 20, 2012
OLEDB Jet For Access
Hi all,
I am looking for a definitive guide to set up a linked server in SQL Server
2000.
I want to add a linked server to an Access (95) database
I have managed this on our production server (although I keep getting errors
occasionally & have to restart the server service), but on a vanilla test
server I cannot get it to work.
I would like to understand why the production server is OK, but the test is
not.
What do I have to install first to make this work?
Also, is there an idiot's guide anywhere ?Hi,
Use Component Checker to verify MDAC installation.
Install a latest Jet pack update or MDAC.
You can find it on http://www.microsoft.com/data
Use sp_addlinkedserver and sp_dropserver instead EM. (read BOL)
Tomasz B.
"CCA Dave" wrote:
> Hi all,
> I am looking for a definitive guide to set up a linked server in SQL Serve
r
> 2000.
> I want to add a linked server to an Access (95) database
> I have managed this on our production server (although I keep getting erro
rs
> occasionally & have to restart the server service), but on a vanilla test
> server I cannot get it to work.
> I would like to understand why the production server is OK, but the test i
s
> not.
> What do I have to install first to make this work?
> Also, is there an idiot's guide anywhere ?
>
>
I am looking for a definitive guide to set up a linked server in SQL Server
2000.
I want to add a linked server to an Access (95) database
I have managed this on our production server (although I keep getting errors
occasionally & have to restart the server service), but on a vanilla test
server I cannot get it to work.
I would like to understand why the production server is OK, but the test is
not.
What do I have to install first to make this work?
Also, is there an idiot's guide anywhere ?Hi,
Use Component Checker to verify MDAC installation.
Install a latest Jet pack update or MDAC.
You can find it on http://www.microsoft.com/data
Use sp_addlinkedserver and sp_dropserver instead EM. (read BOL)
Tomasz B.
"CCA Dave" wrote:
> Hi all,
> I am looking for a definitive guide to set up a linked server in SQL Serve
r
> 2000.
> I want to add a linked server to an Access (95) database
> I have managed this on our production server (although I keep getting erro
rs
> occasionally & have to restart the server service), but on a vanilla test
> server I cannot get it to work.
> I would like to understand why the production server is OK, but the test i
s
> not.
> What do I have to install first to make this work?
> Also, is there an idiot's guide anywhere ?
>
>
OLEDB Jet For Access
Hi all,
I am looking for a definitive guide to set up a linked server in SQL Server
2000.
I want to add a linked server to an Access (95) database
I have managed this on our production server (although I keep getting errors
occasionally & have to restart the server service), but on a vanilla test
server I cannot get it to work.
I would like to understand why the production server is OK, but the test is
not.
What do I have to install first to make this work?
Also, is there an idiot's guide anywhere ?
Hi,
Use Component Checker to verify MDAC installation.
Install a latest Jet pack update or MDAC.
You can find it on http://www.microsoft.com/data
Use sp_addlinkedserver and sp_dropserver instead EM. (read BOL)
Tomasz B.
"CCA Dave" wrote:
> Hi all,
> I am looking for a definitive guide to set up a linked server in SQL Server
> 2000.
> I want to add a linked server to an Access (95) database
> I have managed this on our production server (although I keep getting errors
> occasionally & have to restart the server service), but on a vanilla test
> server I cannot get it to work.
> I would like to understand why the production server is OK, but the test is
> not.
> What do I have to install first to make this work?
> Also, is there an idiot's guide anywhere ?
>
>
I am looking for a definitive guide to set up a linked server in SQL Server
2000.
I want to add a linked server to an Access (95) database
I have managed this on our production server (although I keep getting errors
occasionally & have to restart the server service), but on a vanilla test
server I cannot get it to work.
I would like to understand why the production server is OK, but the test is
not.
What do I have to install first to make this work?
Also, is there an idiot's guide anywhere ?
Hi,
Use Component Checker to verify MDAC installation.
Install a latest Jet pack update or MDAC.
You can find it on http://www.microsoft.com/data
Use sp_addlinkedserver and sp_dropserver instead EM. (read BOL)
Tomasz B.
"CCA Dave" wrote:
> Hi all,
> I am looking for a definitive guide to set up a linked server in SQL Server
> 2000.
> I want to add a linked server to an Access (95) database
> I have managed this on our production server (although I keep getting errors
> occasionally & have to restart the server service), but on a vanilla test
> server I cannot get it to work.
> I would like to understand why the production server is OK, but the test is
> not.
> What do I have to install first to make this work?
> Also, is there an idiot's guide anywhere ?
>
>
Subscribe to:
Posts (Atom)