jwcolby
jwcolby at colbyconsulting.com
Sun Jan 9 21:09:30 CST 2011
No, I want nothing more than to have an access database linked to tables / views on SQL Server across the internet. I will be doing this over a VPN installed on each client machine, and the only exposure will be over that VPN. The client databases will be Access (for now) applications, probably bound forms, though likely only pulling a single record at the top form level. I have never done this before so I will have to see how the performance looks. It will run over a cable connection at my end, 1 mbit up, 20 mbit down. It will run over who knows what on each client end. Hopefully cable, perhaps DSL. Will the performance suck? I just can't tell till I try it. Someday (soon?) I want to go to C# and a service running on my server (initially). We will still have the connection limitations on my end. Eventually, once I get to C# and services, I will start to look at hosting on the internet where the connection limitation will ease up. But for now it will have a bunch of potential bottlenecks. A VM running on my server. SQL Server running on that VM. Hamachi software VPN on both ends. Access as the client. ADO linked tables across this mess. But it is the only solution I can cobble together in the short run. I could run Hamachi directly on my heavy duty SQL Server - 8 cores / 32 gigs, SSD to put the database on etc. I am just a little nervous about exposing that machine at all. I figure that a VM gives me a bit of isolation. It should be interesting if nothing else. John W. Colby www.ColbyConsulting.com On 1/9/2011 8:40 PM, Charlotte Foust wrote: > Maybe I misunderstood the phrase "expose the database". We built apps > that talked to a database across the internet, but we didn't in any > sense "expose" the database to users. The app retrieved data from > views or stored procs but the users could actually see the database. > I got the impression John was trying to actually work on the SQL > Server db across the internet. > > Charlotte Foust > > On Sun, Jan 9, 2011 at 1:13 PM, Stuart McLachlan<stuart at lexacorp.com.pg> wrote: >> To make the data in it accessible to users outside of your LAN. >> >> -- >> Stuart >> >> On 9 Jan 2011 at 10:26, Charlotte wrote: >> >>> Maybe I'm missing the point, but why would you *ever* expose the db on >>> the internet? >>> >>> Charlotte Foust >>> >>> Sent from my Samsung Captivate(tm) on AT&T >>> >> >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >>