Re: ODBC Connection with SQL Managed Provider

From: bruce barker (nospam_brubar_at_safeco.com)
Date: 04/09/04 

Date: Thu, 8 Apr 2004 21:09:32 -0700

its more lilely the startup time of the .net runtime and il code instead of
sql. the odbc manager is no quicker than the odbc.

when .net runs from a network share, it runs in a different mode than if run
more a local drive. the the .net vm must startup and the il has to be jit'd.
this means 1.2 mg of il code needs to be transfered across the network, when
you run the app.

you should break the app into smaller dll's and dynamicly load them you
could get the splash screen up quicker, and only load dll's when needed.

-- bruce (sqlwork.com)

"Ron Fluegge" <rmflugge@swbell.net> wrote in message
news:OfjZa9aHEHA.1528@TK2MSFTNGP09.phx.gbl...
> 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
>
>

Relevant Pages

  • Re: ODBC Connection with SQL Managed Provider
    ... One thing to remember is when running application from a network share, ... > So it was our intent to put a lot of the "forms" into the main app. ... the odbc manager is no quicker than the odbc. ... >>> authorizing the user against a table in the SQL server database. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: ODBC Connection with SQL Managed Provider
    ... The application is a data entry system that is "typically" loaded once (per ... So it was our intent to put a lot of the "forms" into the main app. ... the odbc manager is no quicker than the odbc. ... > this means 1.2 mg of il code needs to be transfered across the network, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: No way to catch this error in VFP?
    ... Yes it is from ODBC and I can re-create at will ...simply pull my network ... I use ODBC to connect to SQL, Oracle and Unix and never have seen any config ... some message box, maybe try another connection. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: I Need code to import data from third party program
    ... as i wrote i got the connection but when i try to open the table i got the ... ODBC data source. ... network drive and you are not connected to the network. ... creating a database on the network computer but i got there the same error. ...
    (microsoft.public.access.externaldata)
  • Communication link failure
    ... The problem is that from time to time, the ODBC connection fails and we ... Check your network documentation. ... it seems that the driver enters a "failure state" - which is reset ...
    (microsoft.public.sqlserver.odbc)
Loading