<hurricane_number_one@yahoo.com> wrote in message
news:1138315553.781086.111300@f14g2000cwb.googlegroups.com...
>I have an application that uses SQL Server and can be run on mutiple
> computers over a local area network. One of my clients has requested
> to have SQL Server running at their main office and have each client
> machine at a different location connecting to SQL Server over the
> internet. I have been able to set this up fine by just pointing the
> client machines to the main office PC by entering the server's IP in
> the client's DSN and opening up the SQL Server port on the main office
> computer's firewall but restricting access to only the IPs of the
> client computers. This all works fine except that when writing large
> number of records it's incredibly slow. If I'm writing 1000+ records
> in a LAN it wouldn't take very long but when I try the same over the
> internet it takes so long that I thought something was wrong and gave
> up waiting. I don't know how long it would take but I waited at least
> 30 mins and it didn't complete. I'm using disconnected recordsets so
> it should be sending all the data at once.
> Any idea why it would be running so slow? I would expect some slowdown
> over the internet but it is pratically non-functional. What can I try
> to speed it up??? I know the connection does work because it works fine
> for smaller number of records. Any suggestions?
>

<hurricane_number_one@yahoo.com> wrote in message
news:1138346871.157193.53420@z14g2000cwz.googlegroups.com...
> It's done in VB6. I'm not using a SP. I open a recordset, disconnect
> it, do my additions/updates then re-connect it and use UpdateBatch,
> which I thought did all the data at once. If I were to just make one
> massive insert statement, then use DBConnection.execute("INSERT
> INTO.....") would that be faster? Any other suggestions?
> Thanks!
>