Speed connecting to SQL using 2.0 framework

[Darin]

This is going to be pretty vague.

Our software was using the 1.1 version of the .NET framework and things
were fine. In March we upgraded to using the 2.0 framework, and the
visual studio 2005. Now, on the same hardware and program, everything is
slower, especially when connecting to SQL.

Has anyone seen anythign like this?

Darin

 

[Stephany Young]

Quantify 'everything is slower'.

 

[RobinS]

Stephany, You're back! Long time no see; hope you're doing ok.
Robin S.
-----------------------

 

[Darin]

Connecting to the SQL database and running SQL statements.

I haven't changed any of the code, so the connection string, and the way
the reading is done is the same.

Connection string:

Data Source={server name};
Initial Catalog=(database name};
User Id={user name};Password={password};
Min Pool Size=1;
Max Pool Size=7500;
Packet Size=32767;


SQL commands is run using:

strCommand = New SqlCommand(in_sql, xconn)
strCommand.CommandTimeout = 3600 '60 minutes
intOut = strCommand.ExecuteNonQuery()

OR

strSQL = "SELECT field FROM table
strCommand = New SqlCommand(strSQL, xconn)
strCommand.CommandTimeout = 600 '10 minutes
xobj = strCommand.ExecuteScalar


Darin

 

[Stephany Young]

Quantify means 'the numbers'.

How many minutes and/or seconds and/or milliseconds (measured) did it take
to connect to SQL Server 'before'.

How many minutes and/or seconds and/or milliseconds (measured) does it take
to connect to SQL Server 'after'.

How many minutes and/or seconds and/or milliseconds (measured) did it take
to 'run' a specfic query 'before'.

How many minutes and/or seconds and/or milliseconds (measured) does it take
to 'run' the exact same query 'after'.

 

[Darin]

This is coming from a customer, so I can't say. Just the general
perception the software is slower.

Basically, my question has to do w/ my connection strings and how I am
getting the data - is that the best way for .NET 2.0 and SQL (some
customers have 2000 and some have 2005).

Darin