Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
shinz
Starting Member
1 Post |
 Posted - 2008-07-20 : 08:25:43
|
| Hi!I've got a little problem, I hope there's someone who can help me...At home I have a Windows 2003 Server Standard Edition with an SQL Server 2005 installed on a computer that's connected to the Router. I am planning to write a database application with Access 2007 that has to connect to the SQL-Server via Internet, because it has to run in different locations.To have the Server available through the internet I set up a dyndns-account and made my router update the IP-address at dyndns. The router forwards the necessary port (TCP and UPD) to the IP-address of the local SQL-Server (I changed it from 1433 to a different port) via NAT/Virtual Server.When I create an Access 2007 adp and connect over my local Ethernet to the SQL-Server everything runs fine. Then I tried the dyndns-connection over the Internet. Connection is no problem at all. But: It is unbelievably slow. It's so slow it's impossible to work with. A form bound to a table is unusable. You can't even type fluently in a text field. You press a key and it takes a few seconds until the letter appears on the screen.Then I tried to make an ODBC-Connection to the Server and everything runs fine. Has someone an idea, how I could fix this issue?Or should I use the ODBC-Connection? Are there any disadvantages? Thanks a lot for you help!Greetings from Berlin,-Sebastian |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-20 : 22:02:11
|
| Use whatever worked. |
 |
|
|
|
|
|
SQL-Server 2005 and Access 2007 adp - way too slow