I'm a little on the illiterate side on SQL, but I cannot seem to get
my subscription pushed. I'm not sure what details I need to provide
to get help, so I'm having to do it in pieces as I find clues. See
the image below:
http://www.chuckchamblee.com/tcifiles/Image2.jpg
It shows as DEACTIVATED. How do I ACTIVATE it?
You need to run the snapshot agent.
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
"CChamblee" <cchamblee@.telcontrol-dot-com.no-spam.invalid> wrote in message
news:YqydnZQ_S_GxFn3fRVn_vQ@.giganews.com...
> I'm a little on the illiterate side on SQL, but I cannot seem to get
> my subscription pushed. I'm not sure what details I need to provide
> to get help, so I'm having to do it in pieces as I find clues. See
> the image below:
> http://www.chuckchamblee.com/tcifiles/Image2.jpg
> It shows as DEACTIVATED. How do I ACTIVATE it?
>
Showing posts with label pushed. Show all posts
Showing posts with label pushed. Show all posts
Monday, March 26, 2012
Push Replication
I have a general question. I want to push data from MSDE to SQL Server
2000. The pushed data is to end up in a 'staging' database on SQL
Server. As part of this process I want to run a stored procedure
against the staged data to update the production database (on the same
SQL Server). I then would like to move the updated production data back
to the staging database (using a stored procedure) and finally back to
the remote client running MSDE. Using events, ActiveX and/or scripts,
can this entire process be encapsulated? The desire is for the user to
connect to headquarters, send his updates, get his updates and
disconnect. Thank you in advance.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Sounds like republishing.
make the production database the publisher and the staging database a
subscriber. Then make another publication on your subscriber which the MSDE
database will subscribe to.
You can use Windows Synchronization Manager to control the pull, or use an
ActiveX control.
Merge replication would probably be the idea replication type.
"Alan Rubel" <alrubel@.hotmail.com> wrote in message
news:%2315ZV1htEHA.2196@.TK2MSFTNGP14.phx.gbl...
>I have a general question. I want to push data from MSDE to SQL Server
> 2000. The pushed data is to end up in a 'staging' database on SQL
> Server. As part of this process I want to run a stored procedure
> against the staged data to update the production database (on the same
> SQL Server). I then would like to move the updated production data back
> to the staging database (using a stored procedure) and finally back to
> the remote client running MSDE. Using events, ActiveX and/or scripts,
> can this entire process be encapsulated? The desire is for the user to
> connect to headquarters, send his updates, get his updates and
> disconnect. Thank you in advance.
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Thank you. I will try it.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
2000. The pushed data is to end up in a 'staging' database on SQL
Server. As part of this process I want to run a stored procedure
against the staged data to update the production database (on the same
SQL Server). I then would like to move the updated production data back
to the staging database (using a stored procedure) and finally back to
the remote client running MSDE. Using events, ActiveX and/or scripts,
can this entire process be encapsulated? The desire is for the user to
connect to headquarters, send his updates, get his updates and
disconnect. Thank you in advance.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Sounds like republishing.
make the production database the publisher and the staging database a
subscriber. Then make another publication on your subscriber which the MSDE
database will subscribe to.
You can use Windows Synchronization Manager to control the pull, or use an
ActiveX control.
Merge replication would probably be the idea replication type.
"Alan Rubel" <alrubel@.hotmail.com> wrote in message
news:%2315ZV1htEHA.2196@.TK2MSFTNGP14.phx.gbl...
>I have a general question. I want to push data from MSDE to SQL Server
> 2000. The pushed data is to end up in a 'staging' database on SQL
> Server. As part of this process I want to run a stored procedure
> against the staged data to update the production database (on the same
> SQL Server). I then would like to move the updated production data back
> to the staging database (using a stored procedure) and finally back to
> the remote client running MSDE. Using events, ActiveX and/or scripts,
> can this entire process be encapsulated? The desire is for the user to
> connect to headquarters, send his updates, get his updates and
> disconnect. Thank you in advance.
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Thank you. I will try it.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Subscribe to:
Posts (Atom)