Data Transfer via Email

Hi,
I have a client that needs to transfer data changes from remote SQL
sites to their HQ central DB. I would prefer to use replication but
unfortunately this is not an option as they only want to use email.
We did a home rolled system about 10 years ago using Access with
custom flags for edits and additions in the DB and the changes were
written to ascii files. I don't want to go down this path again!!
Could anyone give suggestions as to the best direction
- Low bandwidth
- Simple to implement and maintain
- Robust
- Latest 'fashion'
The data changes are primarily in one direction - client->HQ and of
low volume say 5 edits per day. If the way to go is an XML file is
there a mechanism for field based selection, or does it have to be the
entire row?
Appreciate any input,
Thanks,
casey
Publish that table in a transactional replication publication and create a
local subscription and make sure you transaction retention is 1 day.
Then issue a call to sp_browsereplcmds and you will get a list of procedure
calls with parameters which you can email to the other SQL Server. If the
procs are on the remote server you will be able to run these procedures
there.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"casy" <mailkerry@.gmail.com> wrote in message
news:1176105883.833718.305870@.q75g2000hsh.googlegr oups.com...
> Hi,
> I have a client that needs to transfer data changes from remote SQL
> sites to their HQ central DB. I would prefer to use replication but
> unfortunately this is not an option as they only want to use email.
> We did a home rolled system about 10 years ago using Access with
> custom flags for edits and additions in the DB and the changes were
> written to ascii files. I don't want to go down this path again!!
> Could anyone give suggestions as to the best direction
> - Low bandwidth
> - Simple to implement and maintain
> - Robust
> - Latest 'fashion'
> The data changes are primarily in one direction - client->HQ and of
> low volume say 5 edits per day. If the way to go is an XML file is
> there a mechanism for field based selection, or does it have to be the
> entire row?
> Appreciate any input,
> Thanks,
> casey
>
|||Wow,
Thanks Hilary, just what I was looking for, will explore this option!
Casey
On Apr 9, 10:26 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> Publish that table in a transactional replication publication and create a
> local subscription and make sure you transaction retention is 1 day.
> Then issue a call to sp_browsereplcmds and you will get a list of procedure
> calls with parameters which you can email to the other SQL Server. If the
> procs are on the remote server you will be able to run these procedures
> there.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "casy" <mailke...@.gmail.com> wrote in message
> news:1176105883.833718.305870@.q75g2000hsh.googlegr oups.com...
>
>
>
>
>
> - Show quoted text -
|||The mouse is still warm...
New to tranactional replication so it will take a little time for me
to get up to speed. Having created a dummy set up as you suggested and
looked at the stored procedures my question is (before I invest some
serious time) ..
The main data source is -from- the client and installing full SQL
server is probably not an option on these numerous remote sites.
Is it possible/feasable to use Xpress on the client and set it up as a
transactional subscriber - maybe connect initially- and use the method
you outlined previously?
Pardon my ignorance if I am talking nonsense!
Casey
On Apr 10, 7:19 am, "casy" <mailke...@.gmail.com> wrote:
> Wow,
> Thanks Hilary, just what I was looking for, will explore this option!
> Casey
> On Apr 9, 10:26 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
>
>
>
>
>
>
>
>
>
> - Show quoted text -