Replication Strategy

I have an app that has this design: MasterDB contains all the templates used
by the app and a record of all DealDB's created, DealDb contains just the
data, imported from various sources. A new DealDB is created for every new
"deal". The app works fine in the office, now I want to extend it for out of
office(in-transit) use. My idea is to install MSDE on the users PC's and:
1. When the deal is marked in-transit the app will not allow anyone in the
office access to it. So, I want to either detach/attach the DealDB to the
local MSDE or use Bacup/Restore to local MSDE and the same coming back to the
office. Is one better/safer/less error prone then the other? Can I attach a
DB if it was never detached/ can I restore a DB to server that was not the
one it was backed up on?
2. The MasterDB will have to be replicated to local MSDE when a user puts a
deal in-transit. When the user is back in the office all changes to the
local(MSDE)MasterDB will need to be replicated back to the network version.
While the DealDB will simply be either attached or restored back to the
network.
I guess I would use merge replication for the MasterDb? Going to local would
I use Push or Pull subscription, and what about going back to network Push or
Pull?
Can someone help me out with the details, is there a script I can use?
Thanks!
Yes you can set transformations in transactional replication
"mikeb" wrote:

> I have an app that has this design: MasterDB contains all the templates used
> by the app and a record of all DealDB's created, DealDb contains just the
> data, imported from various sources. A new DealDB is created for every new
> "deal". The app works fine in the office, now I want to extend it for out of
> office(in-transit) use. My idea is to install MSDE on the users PC's and:
> 1. When the deal is marked in-transit the app will not allow anyone in the
> office access to it. So, I want to either detach/attach the DealDB to the
> local MSDE or use Bacup/Restore to local MSDE and the same coming back to the
> office. Is one better/safer/less error prone then the other? Can I attach a
> DB if it was never detached/ can I restore a DB to server that was not the
> one it was backed up on?
> 2. The MasterDB will have to be replicated to local MSDE when a user puts a
> deal in-transit. When the user is back in the office all changes to the
> local(MSDE)MasterDB will need to be replicated back to the network version.
> While the DealDB will simply be either attached or restored back to the
> network.
> I guess I would use merge replication for the MasterDb? Going to local would
> I use Push or Pull subscription, and what about going back to network Push or
> Pull?
> Can someone help me out with the details, is there a script I can use?
> Thanks!
sql

Replication Progress

How can I see what the pending transacions are for a given server? Is
there an app that will show me this, or do I have to query a table?
TIA,
Larry...
If you are talking about transactional replication, sp_browsereplcmds can be
used. To filter out commands already replicated, you have to provide the
@.xact_seqno_start argument. The relevant value will be in the
MSreplication_subscriptions table - transaction_timestamp column.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

Replication Problems 32bit IIS 64 bit SQL 2005??

Hello, I have a several PPC app that use replication on seperate IIS
and SQL (2000) boxes with great success. We recently set up our first
2005 SQL install. It happens to be on a x64 machine. I am trying to
use the same IIS set up and just have it replicate with the same
database that has been migrated from 2000 to 2005.

>From the pocket IE browser I get the message "SQL Server Mobile Server
Agent 3.0" so all is good there. At the point where the replication
object in my app tries to synch I get the error message:
"An instance of the SQL Server Reconciler error object cannot be
created. Try reinstalling the replication components."
That is the only error. I have done a little digging and see mention
of repication not working between a 32 bit IIS box and a 64 bit SQL
2005 box. However the messages were from early 2006.
The snapshot share all seem to have the correct rights. I can creat my
publication with the correct articles. And as stated the hand held
gets the success message to PIE.
Can anyone shed a little light on this? Do I need a 32 bit version of
SQL 2005? Is there any other sort of tools I need to install on the
IIS or SQL side?
Any and all help greatly appreciated.
On Feb 21, 11:41 am, rplac...@.yahoo.com wrote:
> Hello, I have a several PPC app that use replication on seperate IIS
> and SQL (2000) boxes with great success. We recently set up our first
> 2005 SQL install. It happens to be on a x64 machine. I am trying to
> use the same IIS set up and just have it replicate with the same
> database that has been migrated from 2000 to 2005.
>
> Agent 3.0" so all is good there. At the point where the replication
> object in my app tries to synch I get the error message:
> "An instance of the SQL Server Reconciler error object cannot be
> created. Try reinstalling the replication components."
> That is the only error. I have done a little digging and see mention
> of repication not working between a 32 bit IIS box and a 64 bit SQL
> 2005 box. However the messages were from early 2006.
> The snapshot share all seem to have the correct rights. I can creat my
> publication with the correct articles. And as stated the hand held
> gets the success message to PIE.
> Can anyone shed a little light on this? Do I need a 32 bit version of
> SQL 2005? Is there any other sort of tools I need to install on the
> IIS or SQL side?
> Any and all help greatly appreciated.
No ideas at all?
Should I try posting to a different group?
Please help.
|||Please have a look at this thread form MS support and see if it helps:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=202038&SiteID=1
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||On Feb 22, 9:07 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> Please have a look at this thread form MS support and see if it helps:http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=202038&SiteID=1
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com
Thanks for the reply. That is not my set up the one referenced in the
article is SQL 2000...but I have my systems guys adding the client
tools as the article suggests.
Can anyone confirm or refute that if IIS is running on at 32 bit
processor box and SQL 2005 is running on a 64 bit processor box that
replication will NOT work? I saw some post mentioning to try WOW and
SQL 2005 in 32 bit install. I'd like to get some MS confirmation that
SQL 2005 on a x64 box is not compatible first.
Thanks a ton!
|||On Feb 22, 1:47 pm, rplac...@.yahoo.com wrote:
> On Feb 22, 9:07 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
>
> Thanks for the reply. That is not my set up the one referenced in the
> article is SQL 2000...but I have my systems guys adding the client
> tools as the article suggests.
> Can anyone confirm or refute that if IIS is running on at 32 bit
> processor box and SQL 2005 is running on a 64 bit processor box that
> replication will NOT work? I saw some post mentioning to try WOW and
> SQL 2005 in 32 bit install. I'd like to get some MS confirmation that
> SQL 2005 on a x64 box is not compatible first.
> Thanks a ton!
I'm at the end of my rope here. But the powers that be do not want to
try a 32 bit version of SQL 2005 on a 64 bit box unless they know that
is the problem. I do not have the option of running 2005 on a 32 bit
box.
If anyone knows this answer or can point me in the right direction
please help. I just want to know if a 64 bit install of SQL 2005 will
not work with replication to a PPC device when IIS is on a seperate
machine running 32 bit.
Thanks!

replication OS Errror 5

I'm using SQLDistribution.SQLDistribution.2 Active X
within a PowerBuilder App. The pull subscribers intitiate
replication from the application. Both publishers and
subscribers are MSDE SQL 2000.
I get: The process could not read file 'bla
bla'\snapshot.pre' due to OS error 5 - UNLESS the user
login running the application has been specifically
granted full control on the snapshot share folder. The
snapshot folder is a public share, not an administrative
share.
It is not a realistic solution for me to grant every user
full control over the share folder. I thought by
using "Impersonate SQL Server Agent Account" for the
subscribcriptions, that the subscribing servers startup
login account would be used to access the snapshot share
folder but apparently not?
Is there someway to use the replication activex but avoid
having to grant every application user full control of the
snapshot folder?
Thanks,
Pat
the minimum security on the files and folders is read and list folder and
contents. The minimum share permission required is read. Is the allow
inheritable permissions from parent to propagate to this object checked?
Are you sure that the account you are using has both of these rights on the
snapshot share and underlying files and folders?
You are correct when you select the impersonate option on a pull
subscription the SQL Server agent account on the Subscriber must have rights
to access the snapshot folder.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Pat" <anonymous@.discussions.microsoft.com> wrote in message
news:47f001c4734c$19e2cfe0$a501280a@.phx.gbl...
> I'm using SQLDistribution.SQLDistribution.2 Active X
> within a PowerBuilder App. The pull subscribers intitiate
> replication from the application. Both publishers and
> subscribers are MSDE SQL 2000.
> I get: The process could not read file 'bla
> bla'\snapshot.pre' due to OS error 5 - UNLESS the user
> login running the application has been specifically
> granted full control on the snapshot share folder. The
> snapshot folder is a public share, not an administrative
> share.
> It is not a realistic solution for me to grant every user
> full control over the share folder. I thought by
> using "Impersonate SQL Server Agent Account" for the
> subscribcriptions, that the subscribing servers startup
> login account would be used to access the snapshot share
> folder but apparently not?
> Is there someway to use the replication activex but avoid
> having to grant every application user full control of the
> snapshot folder?
> Thanks,
> Pat