[AccessD] SQL Server over Hamachi: First test not hopeful

Jim Lawrence accessd at shaw.ca
Sun Jan 16 11:04:38 CST 2011


To add to the comments: I think the only way a person is going to be able to
build application that runs decently in such locations is go and build a web
(html) front end...that is your only option.

Jim

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Sunday, January 16, 2011 8:33 AM
To: 'Access Developers discussion and problem solving'; 'VBA';
'Sqlserver-Dba'
Subject: Re: [AccessD] SQL Server over Hamachi: First test not hopeful


  The wi-fi in a public place is going to vary wildly in terms of quality.
You may have had your tested speed for all of two seconds. And outside of
raw speed, latency is a big factor.

  The other thing is with a Access FE and SQL Server BE over a VPN, your not
going to get away with simply using linked tables.

  You need to be using pass through queries, stored procedures, and
triggers.  As much as possible needs to happen server side for that to work
at all.  And app development is entirely different; no forms simply bound to
a table or query, but ones that deliver one record at a time.

  If you don't want to put that amount of effort into that or you want to
work over a VPN well, then you need to use terminal services and possibly
Citrix on top of that.

  By doing so, only KVM (Keyboard, Video, and Mouse) goes over the wire and
the app runs local.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Saturday, January 15, 2011 06:37 PM
To: Access Developers discussion and problem solving; VBA; Sqlserver-Dba
Subject: [AccessD] SQL Server over Hamachi: First test not hopeful

I developed a SQL Server database, with perhaps 10-15 tables, populated a
few with just a handful of 
records, created an Access database and built a few forms.  My strategy is
to do Access because I 
can do it quickly, but link it to SQL Server, the run the FE on a remote
computer over Hamachi.

Tonight I went to a local Arby's to test the speed of the system.  The local
Arby's has an open 
wifi, which using Speedtest.net tested 5 mbit down, 1 mbit up - typical low
end cable in my area.

So I tried to use the system and... well... it took an extremely long time
to connect, if it 
connected at all.  Access mostly timed out trying to log on.  SQL Server
Management System would log 
on sometimes.  Sometimes not.  Trying to hit it at the actual Hamachi IP
address worked but took 
awhile.  15 - 30 seconds to connect (I did not time it).

To be honest I am puzzled.  Google finds plenty of folks trying this, some
succeeding, most pretty 
slow.  Remote desktop is plenty fast.

 From inside of my office, out across the internet via Hamachi I have done
things like file 
transfers etc (in the past).  Remote desktop has always been very speedy,
but there isn't much 
needed for RD.

I had really expected faster connections / operation.  I really expected
SSMS to just work, pretty 
much at speed.  It didn't.

Sigh, back to the drawing boards.
-- 
John W. Colby
www.ColbyConsulting.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list