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 |
|
Trutter
Starting Member
3 Posts |
 Posted - 2010-03-24 : 04:35:54
|
| We are about to upgrade a SQL server 7 installation to SQL Server 2005. The server connects via ISDN to a number of remote clients and data is distributed to the clients using transactional replication also the clients write to server database occassionally via an ODBC connection. The clients are running MSDE 2000. Because of the ISDN installation and potential call costs we need to ensure that the systems do not connect unless required. Does anyone know of any settings or timers within SQL 2005 or MSDE 2000 which need to be set to ensure that the two systems do not periodically chatter and raise the ISDN line unnecessarily. |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-03-24 : 04:43:04
|
| Are these POS tills?Colleague of mine works on that side (our eCommerce package is linked to shops to show shop-stock and allow people to reserve-in-store etc.) and I think everything is now done with VPN and ADSL (hence raising the line problem gone away!)If interested send me a PM and I can put you in touch with him, we are in the UK - might have complimentary business interests, but if you are a competitor then maybe not!! |
 |
|
|
Trutter
Starting Member
3 Posts |
Posted - 2010-03-24 : 05:13:08
|
| These aren't POSIt is a distributed system monitoring and issuing instructions to a number of remote sites. We have tried to suggest to the customer that the network is upgraded at the same time as the server upgrade but they are not currently willing to go this.Any help would be welcome, as I am new to the forum I'm not sure how to send a PM |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-03-24 : 05:56:13
|
| OK, not relevant then. Rats!You can send a PM by clicking on User Name then "Send Email"I don't know enough about SQL replication to know if newer version will tickle the replication more often. We do that sort of things with roll-our-own logging of data to be transferred and then sending that on-demand to minimise WAN traffic - which will be of no help to you if you want to keep as much the same as possible.This thread on upgrading / migrating to SQL2008 may help. Most of it is relevant to SQL2005 upgrade (and there is a link to a SQL 2005 upgrade notes)http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=138230 |
|
|
|
|
|
|
SQL 2005 upgrade from SQL server 7