PC Review


Reply
Thread Tools Rate Thread

ado.net 2.0 and sql server 7

 
 
Juan M. Servera
Guest
Posts: n/a
 
      29th Jul 2005
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.


 
Reply With Quote
 
 
 
 
Ray Booysen
Guest
Posts: n/a
 
      29th Jul 2005
Juan M. Servera wrote:
> 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
 
Reply With Quote
 
Sahil Malik [MVP]
Guest
Posts: n/a
 
      29th Jul 2005
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.ma.../13/63199.aspx
----------------------------------------------------------------------------


"Juan M. Servera" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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.
>



 
Reply With Quote
 
W.G. Ryan MVP
Guest
Posts: n/a
 
      30th Jul 2005

"Juan M. Servera" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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?



> Is there any workaround to speed up this a bit. Our application is now
> unusable with sql 7.
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
An error has occurred while establishing a connection to the server.When connecting to SQL Server 2005, this failure may be caused by the factthat under the default settings SQL Server does not allow remote connections. mina Microsoft VB .NET 0 8th Oct 2008 07:12 AM
An error has occurred while establishing a connection to the server.When connecting to SQL Server 2005, this failure may be caused by the factthat under the default settings SQL Server does not allow remote connections. mina Microsoft Dot NET 0 8th Oct 2008 07:11 AM
Help. Getting a An error has occurred while establishing a connectionto the server. When connecting to SQL Server 2005, this failure may be causedby the fact that under the default settings SQL Server does not allow remote aboutjav.com@gmail.com Microsoft ASP .NET 0 3rd May 2008 01:43 PM
Mirroring a Windows 2000 Server so that the backup server takes over when the main server fails Karl Strausser Microsoft Windows 2000 Setup 1 28th Sep 2005 01:43 AM
How do i change this connect string to support a SQL Server 2000 running on port 8832 User ID=car;Password=rat;Server=abc.def.hij;Initial Catalog=foobar i tried Server=abc.def.hij:8823 and Server=abc.def.hij;port=8823 neither of these work Daniel Microsoft Dot NET Framework 1 16th Dec 2004 09:55 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 05:29 AM.