detect replication erros

Hi,
I'm running SQL Sever 2000 SP4 and am replicating a database.
This is the scenario:
Server1 : holds the source database to be replicated (publisher)
Server2: is the one that receives the replicated data (suscriptor)
Some times it happens that the replication goes down and we do not realise
but until an user calls us.
We cannot implemet email notifications on the server2 as due to some
technical restrictions, MS Outlook cannot be installed on that server
What we want is a way that from server1 we are able to detect replication
failures and as this server has got SLQ Mail we'd (via a store procedure)
sent a notification off to the DBAs.
Any ideas?you can send mail without outlook
insert your message into "message" table,
create job in vbscript using CDO.Message and send mail over any smtp server
--
Aleksandar Grbic
MCDBA
"FJC" wrote:
> Hi,
> I'm running SQL Sever 2000 SP4 and am replicating a database.
> This is the scenario:
> Server1 : holds the source database to be replicated (publisher)
> Server2: is the one that receives the replicated data (suscriptor)
> Some times it happens that the replication goes down and we do not realise
> but until an user calls us.
> We cannot implemet email notifications on the server2 as due to some
> technical restrictions, MS Outlook cannot be installed on that server
> What we want is a way that from server1 we are able to detect replication
> failures and as this server has got SLQ Mail we'd (via a store procedure)
> sent a notification off to the DBAs.
> Any ideas?

detect replication erros

Hi,
I'm running SQL Sever 2000 SP4 and am replicating a database.
This is the scenario:
Server1 : holds the source database to be replicated (publisher)
Server2: is the one that receives the replicated data (suscriptor)
Some times it happens that the replication goes down and we do not realise
but until an user calls us.
We cannot implemet email notifications on the server2 as due to some
technical restrictions, MS Outlook cannot be installed on that server
What we want is a way that from server1 we are able to detect replication
failures and as this server has got SLQ Mail we'd (via a store procedure)
sent a notification off to the DBAs.
Any ideas?you can send mail without outlook
insert your message into "message" table,
create job in vbscript using CDO.Message and send mail over any smtp server
Aleksandar Grbic
MCDBA
"FJC" wrote:

> Hi,
> I'm running SQL Sever 2000 SP4 and am replicating a database.
> This is the scenario:
> Server1 : holds the source database to be replicated (publisher)
> Server2: is the one that receives the replicated data (suscriptor)
> Some times it happens that the replication goes down and we do not realise
> but until an user calls us.
> We cannot implemet email notifications on the server2 as due to some
> technical restrictions, MS Outlook cannot be installed on that server
> What we want is a way that from server1 we are able to detect replication
> failures and as this server has got SLQ Mail we'd (via a store procedure)
> sent a notification off to the DBAs.
> Any ideas?sql

Detaching replicated database

Hello there
I have database that i marked it before as publisher. Since then it showed
with hand near to it. And then i can't detach it.
I remove the publisher and it didn't help
What should i do for detach it now?
any help would be useful
Whell Paul
How can i get this book?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:27bd01c4af70$fd679b00$a301280a@.phx.gbl...
> I'm not too sure what stage the system is in - you
> mention you have removed the publisher - does this mean
> that you have disabled publishing, or removed the
> publication. I think it must be the latter. In this case
> try resetting the replication flags on the database in
> question. EG if it was Pubs:
> exec sp_dboption 'pubs','published',false
> exec sp_dboption 'pubs','merge publish',false
> After that you should be able to detack.
> HTH,
> Paul Ibison (SQL MVP)
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Oded,
I've been lucky enough to have a sort of advanced
preview, but to register for it when it comes out
publically (imminently AFAIK) have a look at this
address: http://www.nwsu.com/0974973602reg.html.
Apparently it will eventually be available on Amazon
etc. - Hilary will be able to give you more info (if he
doesn't see this thread then post a separate one in this
newsgroup FAO Hilary Cotter).
Regards,
Paul Ibison (SQL Server MVP)

detach/attach a replicated database

Is there some easy way to detach a replicated database without dropping the
replication around it ?
I guess while i was waiting for an answer, i tried to update the category
column in sysdatabases to 0 , detached the db, attached it again and updated
the column back to 1 and looked like everything worked fine.. I inserted a
record and it propogated through
Let me know if this is fine to do..
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:e%23kJuvaYFHA.3836@.TK2MSFTNGP10.phx.gbl...
> Is there some easy way to detach a replicated database without dropping
the
> replication around it ?
>
|||that trick is very helpful. It helped me unpublish the replicated database and then re-publish it quickly without going through the painful process again and again.
From http://www.developmentnow.com/g/114_2005_5_0_0_527842/detachattach-a-replicated-database.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
|||that trick is very helpful. It helped me unpublish the replicated database and then re-publish it quickly without going through the painful process again and again.
From http://www.developmentnow.com/g/114_2005_5_0_0_527842/detachattach-a-replicated-database.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com

Detach replicated DB?

Trying to detach a DB from the publisher/distributer via EM from another PC
on the network. The detach box has the message: ATTENTION: The database
cannot be detached while it is being replicated. And the OK button is
disabled. I took this as you cannot detach during replication. But it is
not being replicated now. Does this mean a DB set up as a publisher can't be
detached at all?
Thanks,
Steve
After reading further, it appears that I can't do this. So I have deleted
the publications. But I still get the ATTENTION message and can't detach.
"SteveInBeloit" wrote:

> Trying to detach a DB from the publisher/distributer via EM from another PC
> on the network. The detach box has the message: ATTENTION: The database
> cannot be detached while it is being replicated. And the OK button is
> disabled. I took this as you cannot detach during replication. But it is
> not being replicated now. Does this mean a DB set up as a publisher can't be
> detached at all?
> Thanks,
> Steve
|||From another post I read,
You will be unable to detach replicated databases. You have to script out
the publications, edit them for the new server, remove all job names, and
then drop the publications, unpublish the databases and detach them.
I have deleted the publications, but what is mean't by unpublish the database?
"SteveInBeloit" wrote:
[vbcol=seagreen]
> After reading further, it appears that I can't do this. So I have deleted
> the publications. But I still get the ATTENTION message and can't detach.
> "SteveInBeloit" wrote:
|||In EM, connect with your SQL Server, select Tools, Replication, Configure
Distributor, Publishers and subscribers, Click on the Published databases
tab, and uncheck the check marks for transactional or merge if the database
is published.
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
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:182E9763-9D45-4EB7-8C60-AB9F7F4F7ABD@.microsoft.com...
> From another post I read,
> You will be unable to detach replicated databases. You have to script out
> the publications, edit them for the new server, remove all job names, and
> then drop the publications, unpublish the databases and detach them.
> I have deleted the publications, but what is mean't by unpublish the
database?[vbcol=seagreen]
>
> "SteveInBeloit" wrote:
deleted[vbcol=seagreen]
detach.[vbcol=seagreen]
another PC[vbcol=seagreen]
database[vbcol=seagreen]
it is[vbcol=seagreen]
can't be[vbcol=seagreen]
|||Thank you!
"Hilary Cotter" wrote:

> In EM, connect with your SQL Server, select Tools, Replication, Configure
> Distributor, Publishers and subscribers, Click on the Published databases
> tab, and uncheck the check marks for transactional or merge if the database
> is published.
> --
> 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
> "SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
> news:182E9763-9D45-4EB7-8C60-AB9F7F4F7ABD@.microsoft.com...
> database?
> deleted
> detach.
> another PC
> database
> it is
> can't be
>
>
|||Hilary,
If you delete the publisher and the subscriber to detach the published
database, how do you reinstae the publisher and the subscriber? I hope I do
not have to do the replication all over from the beginning.
Thanks,
George Gopie
"Hilary Cotter" wrote:

> In EM, connect with your SQL Server, select Tools, Replication, Configure
> Distributor, Publishers and subscribers, Click on the Published databases
> tab, and uncheck the check marks for transactional or merge if the database
> is published.
> --
> 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
> "SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
> news:182E9763-9D45-4EB7-8C60-AB9F7F4F7ABD@.microsoft.com...
> database?
> deleted
> detach.
> another PC
> database
> it is
> can't be
>
>