ado.net 2.0 and sql server 7

[Juan M. Servera]

Hello, we are migrating our "old" .net 1.1 application to 2.0 and have
noticed that opening connections to a sql server 7 now is very very slow,
but this doesn't happen with sql server 2000.
Is there any workaround to speed up this a bit. Our application is now
unusable with sql 7.

 

[Ray Booysen]

Hello, we are migrating our "old" .net 1.1 application to 2.0 and have
noticed that opening connections to a sql server 7 now is very very slow,
but this doesn't happen with sql server 2000.
Is there any workaround to speed up this a bit. Our application is now
unusable with sql 7.

Jeepers, you are migrating from 1.1 to 2.0 before its fully released.

Did you move from SQL 2000 to SQL 7?

Just out of interest, why are you migrating?

Regards
Ray Booysen

 

[Sahil Malik [MVP]]

Let me confirm a few things -

a) You are not using distributed transactions.
b) can you paste your connection string?
c) You are using SqlClient.
d) You are able to replicate this behavior in a Console Application - all
the consoleapp does is "open a connection".

- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.malik/archive/2005/05/13/63199.aspx

 

[W.G. Ryan MVP]

Hello, we are migrating our "old" .net 1.1 application to 2.0 and have
noticed that opening connections to a sql server 7 now is very very slow,
but this doesn't happen with sql server 2000.

-- Juan, just to make sure I understand, does the simple process of calling
MyConnection.Open(); - that's what takes a long time? If it is (and I
guess even if it isn't), if you use the exact same code and run it under
1.1 - there's no problem?

From just this, it's hard to isolate b/c the box the 97 is running on could
be slower/less ram etc or there could be any of a number of differences
between the two.

Are you able to isolate anything else that could contribute to it?