>I'll soon be installing an ASP application on our ISP web server that accesses a MSSQL DB also residing on the web server. Our vendors will be posting and updating data on this DB that I need to replicate back on our local version of MSSQL DB that in turn will update another MSSQL DB once vendor updates have been validated.
>
>In other words, very "hairy" setup where things can go wrong fast if data changes aren't replicated and updated in a timely manner.
>
>Anyway, it's relatively easy to setup replication between MSSQL servers "within" LAN/WAN (trusted connection) but can I setup and schedule replication between MSSQL servers through the Internet between our ISP and local MSSQL? What issues are involved and are there any hurdles I should know and solve? TIA.

The setup is basically the same going over the Internet. It's just a big WAN. The issues you have to be cognizant of:

1. The default port for SQL Server TCPIP connectivity is 1433. If using the Internet, you should think about changing this using teh Server Network Utility.
2. Make sure whatever port you configure your server to listen for is supported by your ISP. Some ISP limit the number of ports routed in order to prevent security problems.
3. Password protect every thing.

HTH.