Very Computer

I'm new to SQL server and I've been reading up on replication and am
still not sure what to do.  Here's the situation.

I've got my store inventory in an SQL Server 2000 db on my local
computer, and another copy on my non-local web host's server.  I add
new inventory on my local copy and occasionaly change old listing
information.  I don't make changes on a regular schedule and don't
usually have the local server running, so I want to be able to
manually run the replication, not have it auto run on a schedule.  The
only changes made to the data at the web-host's copy would be changes
made to the quantity column of an item when it sells and that change
would be through an asp page.

Previously when I used Access I had written an asp page to just copy
the quantity info from the online db to my newly updated local one and
then replace the online one with the new updated copy.  This was a
pain to do, so I was hoping that relication would be the
solution...but it seems all forms of it want to add columns and change
my data to work.

Any suggestions as to what method and options to use would be
appreciated.

Thanks

MO,

Only Merge replication adds columns, and just one, to a table. Merge also
adds triggers. Transactional and Merge both add system tables and many
system stored procedures to the publisher and subscriber. Transactional just
adds less, but realistically it's only one-way, and not meant for only
occasional connections.

If you have to be able to update the same table or tables from both the web
site and your local machine, then Merge is the most practical solution.

Ron
--
Ron Talmage
SQL Server MVP

Quote:> I'm new to SQL server and I've been reading up on replication and am
> still not sure what to do.  Here's the situation.

> I've got my store inventory in an SQL Server 2000 db on my local
> computer, and another copy on my non-local web host's server.  I add
> new inventory on my local copy and occasionaly change old listing
> information.  I don't make changes on a regular schedule and don't
> usually have the local server running, so I want to be able to
> manually run the replication, not have it auto run on a schedule.  The
> only changes made to the data at the web-host's copy would be changes
> made to the quantity column of an item when it sells and that change
> would be through an asp page.

> Previously when I used Access I had written an asp page to just copy
> the quantity info from the online db to my newly updated local one and
> then replace the online one with the new updated copy.  This was a
> pain to do, so I was hoping that relication would be the
> solution...but it seems all forms of it want to add columns and change
> my data to work.

> Any suggestions as to what method and options to use would be
> appreciated.

> Thanks

The only methods that does not require schema changes are transactional and
snapshot.   However, the data changes are only going to flow one direction.
To get data to flow in both directions, you need to make schema changes.

--

Mike
SQL Server MVP
http://www.mssqlserver.com