ODBC Connection with SQL Managed Provider
From: Ron Fluegge (rmflugge_at_swbell.net)
Date: 04/08/04
- Next message: Wardeaux: "Re: Help! What's with the open connection?"
- Previous message: Bin Song, MCP: "Re: Using one instance of SqlConnection in an ASP.NET page"
- Next in thread: bruce barker: "Re: ODBC Connection with SQL Managed Provider"
- Reply: bruce barker: "Re: ODBC Connection with SQL Managed Provider"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Apr 2004 16:20:55 -0500
I have a Win forms application using version 1.1 that a client has installed
on a "network drive". The application connects with a SQL Server 2000
database using the Microsoft .NET Framework 1.1 Data Provider for SQL
Server.
The client's users map to the network drive and run the application from a
desktop icon that references the application on the mapped drive
(Y:\AppFolder\App.exe). In some cases, they are referencing the application
without mapping to the drive such as
\\ServerName\ShareName\AppFolder\App.exe.
The Framework 1.1, as well as all supporting files, are installed on each
user's desktop and the application "executes" just fine.
The client's problem is the "speed" of having the application start.
Apparently, it takes 1 minute for the "splash" screen to display and then
the main window follows 2 minutes later. The application EXE is 1.2 MB and
during this time it is simply getting the user's Windows identity and
authorizing the user against a table in the SQL server database. Really,
not a big chunk of code and, of course, it's blazing fast when the
application is run on the user's machine even when it goes to the database
server on the network to do the authorization -- so it appears that the SQL
Server portion (ADO.NET) is not the problem ... correct?
According to my main contact (a user and not an IT person), the client's IT
dept wants to do something with "ODBC connections" to make it "faster".
I'll be the first to admit that this is not my expertise, but is there
something that they can do with the network related to ODBC connections to
make the app download faster? I would have thought that ODBC would have no
bearing when using the Managed Providers. It's apparently something that
they can write in under an hour and make everything work ... I have to admit
that I have no idea what it is that they're planning to do.
I don't fully understand why on a corporate network it should take so long
for the app to display the "splash" screen (which is the first thing it does
so that the user authorization can proceed under the covers so to speak).
The question is: Is there anything related to Win forms/ADO.NET apps that I
can do to speed up the downloading of the application from the mapped drive
to the user's machine to run the app? The client's IT depart is supposed to
be .NET "savvy", but I'm not sure why a SQL Server Managed Provider ADO.NET
app's speed would be affected by ODBC connections...
I've Google'd everything I could thing of and have come up empty. Any
advice, references, suggestions, etc. would be greatly appreciated.
Thanks...
Ron
- Next message: Wardeaux: "Re: Help! What's with the open connection?"
- Previous message: Bin Song, MCP: "Re: Using one instance of SqlConnection in an ASP.NET page"
- Next in thread: bruce barker: "Re: ODBC Connection with SQL Managed Provider"
- Reply: bruce barker: "Re: ODBC Connection with SQL Managed Provider"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
