Re: SQL Express slow when connecting from client on network.

Does LINQ use the SQL Server Native Client?
One possibility: Perhaps your SQL Server Native Client on the XP computer is attempting to connect via named pipes. Named pipes is not enabled on the client. After 85 seconds the connection attempt times out. Then it tries the next protocol such as TCP. It connects right away and returns results.
Or the other way around trying TCP first and then named pipes?
Use SQL Server Configuration Manager on the server to see which protocols are enabled.
Use SQL Server Configuration Manager on the client to determine the order of protocol connection attempts.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"William Vaughn (MVP)" <billva@xxxxxxxxxxxxxxx> wrote in message news:27BB7C09-99ED-4877-80A2-540C4280C6E7@xxxxxxxxxxxxxxxx
Ah, not being a LINQ fan, I can't say that I've heard of anyone use the terms "performance" and "LINQ" in the same sentence. I would turn on the SQL Profiler to see what's getting sent to the server by your application. It could be LAN latency or routing issues that are not seen when connecting with the Shared Memory provider but I expect that it's just extra overhead added by LINQ.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
____________________________________________________________________________________________



"jdc" <jdc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B2CCE2C9-8D0F-435A-AF86-A758A0EDBA60@xxxxxxxxxxxxxxxx
Hi,

I am not even sure if this is the right place to post, and I will admit
upfront I am fairly new at SQL programming.

I have written an application for a non-profit and deployed at their office
using SQL Server 2008 Express edition.

When I do an upate of data from my application on the machine that SQL
server is installed, the update takes around 5 seconds.

When I do an update of the same data from my application on an XP machine,
the same update takes around 90 seconds.

Same software, same data, only difference is machines.

Server machine is Server 2008.
Client machine is Win XP.

The application is written in C# and I am using LINQ to SQL to read/write
data.

Any help in explaining the speed difference (and how to eliminate it), would
be greatly appreciated.

Thanks


.

Relevant Pages

  • Trying to install SQL 2005 Standard onto Windows Server SQL 2008
    ... Component: SQL Server Native Client ... An attempt was made to install SQL Server Native Client on ... Client from an MSI file that is not named sqlncli.msi. ... When I start the installation, I get the warning from the SQL 2005 ...
    (microsoft.public.sqlserver.setup)
  • Re: Using SQL Server Native Client (ODBC) - SQLDriverConnect No respon
    ... Ah, I was under the impression that the SNAC provider is a COM-based (OLE DB) provider, not an ODBC data provider. ... I am working on a native C application, which should connect to a SQL Server ... by using the SQL Server Native Client. ...
    (microsoft.public.sqlserver.connect)
  • Re: Performance reduction of SQL 2005 server when connected from V
    ... SQL Server on it, ... will tell you what process ID is your current connection. ... How can I check out if the SQL Server Native Client version is the same ... found no reduction in the speed of the SQL 2005 server remote ...
    (microsoft.public.sqlserver.connect)
  • Re: Performance reduction of SQL 2005 server when connected from V
    ... One of my computers says 9.0.9091.2 but that computer has a future build of SQL Server on it, ... will tell you what process ID is your current connection. ... How can I check out if the SQL Server Native Client version is the same ... > found no reduction in the speed of the SQL 2005 server remote> connection. ...
    (microsoft.public.sqlserver.connect)
  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()
    ... the ODBC source using named pipe, but I don't know how to enable named pipes ... If it is not working I am going to use ado to connect to sql server. ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.connect)
Loading