Replication

undefined

Hi,

I have successfully replicated a database (type : Transactional), but when i have executed a Alter scripts to effect the schema of the database it worked. My concern is whether the replication was done successfully or not ?
Can we change the schema of a replicated database by plain Alter scripts ?
Plz let me know....

Thanks
RakeshDepending on what you altered. If you want to alter rules or foreign keys without checking replication, you don't have to do anything to the replication setup. But if you change table schma, you need to either use the replication system procedures to change it or you have to drop all subscriptions and initialize them.|||I am able to alter the table schema by using Replication stored procedures, but my concern is, i am also able to change the table schema by simple alter statements on the primary database, but these changes are not making into secondary database i,e subscriber database. Do we get any error Msg trying to alter a table schema of a replicated database ?|||Yes, you should get an error messge when you try to use an ALTER TABLE command against a replicated table. The ALTER TABLE should fail, but it sounds like it is working for you.

Is it possible that the table you are affecting isn't being replicated (either it was never included in a publication, or that its article has been dropped from the publication)?

-PatP|||Yes, you should get an error messge when you try to use an ALTER TABLE command against a replicated table. The ALTER TABLE should fail, but it sounds like it is working for you.

Is it possible that the table you are affecting isn't being replicated (either it was never included in a publication, or that its article has been dropped from the publication)?

-PatP

In case of merge replication it is not possible to alter repilcated table but for transaction replication it works. Welcome to Microsoft...

Replication

I have replication configured in an sql 2005 environment. I have
executed the wizard twice but each time the following maintenance jobs
are missing
Reinitialize subscriptions having data validation failures
Agent history clean up: distribution
Replication monitoring refresher for distribution.
Replication agents checkup
Distribution clean up: distribution
Expired subscription clean up
If someone can tell me what most be done to have these jobs created
or why the wizard failed to create them it would be a big help.What do you set up exactly? Distributor, Publisher and Subscriber? Also what
Replication method do you setup? Merge, Transactional, Snapshot?
--
Ekrem Önsoy
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>I have replication configured in an sql 2005 environment. I have
> executed the wizard twice but each time the following maintenance jobs
> are missing
>
> Reinitialize subscriptions having data validation failures
> Agent history clean up: distribution
> Replication monitoring refresher for distribution.
> Replication agents checkup
> Distribution clean up: distribution
> Expired subscription clean up
> If someone can tell me what most be done to have these jobs created
> or why the wizard failed to create them it would be a big help.
>|||On Oct 8, 4:22 pm, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also w=hat
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem =D6nsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide q=uoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.|||Hello,
What version of SQL 2005 you are using. As there was bug prior SP1. try
increasing the size of your model db try configuring again.
Thanks
Ajay Rengunthwar
MCDBA,MCTS
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191876823.867493.221310@.50g2000hsm.googlegroups.com...
On Oct 8, 4:22 pm, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also
> what
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem Önsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide
> > quoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.

Replicating stored procedure/trigger permissions to another database

I need to come up with a script that when executed it will create a stored procedure and trigger along with permissions. Is there a way to make this into a package. Any ideas?So you want to take a stored procedure that is in the current database, and somehow "automagically project" that procedure intact to another (subscriber) database?

That's a novel thought.. It could be done, and it wouldn't be terribly hard.

-PatP|||There is no "automagic" in it, just use SQL-DMO object model. Just one method is involved. Examples are in BOL.|||things to automate
-add a user to master table
-add Permissions to xp_cmdshell
-create trigger in table
-create stored procedure in needed database
-uncheck Non-SysAdmin job setup Proxy Account box and create proxy account

I image that I could write this all out by using a T-SQL stored procedure. But, some things that I don't know is: where it should be stored? or what would be the most efficient way of going about this?

Don't know where to start but to create the procedure and then I'll figure out what to do from there.