We have a situation where we have a database on an
enterprise server which needs to be replicated onto a number
of laptops.
These laptops go out into the field and may need to be updated
from the enterprise server database several times each day.
The enterprise database is approximately 2 Gig but the amount of
changes that occur is probably in the order of 100 - 200 changes
across up to 40 tables. The time we have available to update these
laptops is minimal.
I am relatively new to SQLServer so I am interested in the
possibilities that are available to us , i.e.
- Identifying changes in the transaction log.
- Triggers on tables which dump to a staging table.
- Identifying changes that are made and using it to create an osql
file to apply to the laptop databases.
We are using SQLServer2000.
I am also interested in the possible disadvantages of any of
these approaches.
Thank you in advance.
enterprise server which needs to be replicated onto a number
of laptops.
These laptops go out into the field and may need to be updated
from the enterprise server database several times each day.
The enterprise database is approximately 2 Gig but the amount of
changes that occur is probably in the order of 100 - 200 changes
across up to 40 tables. The time we have available to update these
laptops is minimal.
I am relatively new to SQLServer so I am interested in the
possibilities that are available to us , i.e.
- Identifying changes in the transaction log.
- Triggers on tables which dump to a staging table.
- Identifying changes that are made and using it to create an osql
file to apply to the laptop databases.
We are using SQLServer2000.
I am also interested in the possible disadvantages of any of
these approaches.
Thank you in advance.
