MSDB and MASTER DB

Im using MS SQL2000 and have and replication scheme with log
shipping. Is posible replicate by log shipping or transactional
replication schemes this DBs
Thanks
I'm not sure what the question is really here - the subject seems so
different to the body text
If you want to know the pros and cons of transactional replication vs log
shipping, please see this article:
http://www.replicationanswers.com/Standby.asp
If you are looking to set up a combination of log shipping and replication,
then please tell us a little more...
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Both system db's are in simple mode. Microsoft recommends backing the msdb
database up and shipping it. While it is possible to restore a master
database to another server, Microsoft recommends you transfer objects to the
standby server.
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
<gnp1977@.gmail.com> wrote in message
news:1173280868.971366.142840@.c51g2000cwc.googlegr oups.com...
Im using MS SQL2000 and have and replication scheme with log
shipping. Is posible replicate by log shipping or transactional
replication schemes this DBs
Thanks
|||Hi, thanks for the answer, I need transfer the content of two DB to a
standby server...One of this have 35mb and the other have 13GB.
What method is the better? Transactional or Log Shipping?
And other thing, de DBs MASTER and MSDB can be replicated to the
stand by server, I need this because is a Continuity of Bussines site.
Thanks
|||For these volumes I would use transactional replication if possible. For the
master and msdb databases, what sort of objects are you moving?
In master your linked servers and logins live. Do these change much? There
is a SQL DTS/SSIS job which will transfer the logins. Your msdb databsae
will contain DTS packages and jobs. These can be scripted/exported and sent
to the standby server.
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
<gnp1977@.gmail.com> wrote in message
news:1173296916.452161.294790@.n33g2000cwc.googlegr oups.com...
Hi, thanks for the answer, I need transfer the content of two DB to a
standby server...One of this have 35mb and the other have 13GB.
What method is the better? Transactional or Log Shipping?
And other thing, de DBs MASTER and MSDB can be replicated to the
stand by server, I need this because is a Continuity of Bussines site.
Thanks

msdb and log shipping question

Hi,
We have set up an log shipping for DatabaseA between Server1 and Server2.
Now that log shipping was canceled and the DatabaseA in Server2 was also
deleted.
Is there any info still kept in the Server2 regarding to the log shipping
and DatabaseA?
I built a new log shipping plan but it was no good cause the transaction
didn't copy to the Server2, while other log shipping for other databases
were OK.
Thanks for help.
JasonHi Jason
Have you looked at http://msdn2.microsoft.com/en-us/library/ms187045.aspx
John
"Jason Huang" wrote:

> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>
>|||If you did not remove the Log Shipping according to the procedure then the
jobs of old Log Shipping must be left in the Jobs node under SQL Server
Agent. You better purge them.
After deletion of the DatabaseA from the Server2, did you restore a copy of
the DatabaseA on the Server1 on Server2 in a STANDBY or NORECOVERY recovery
state?
You can check the history of the jobs that are created for the new Log
Shipping to find the exact error. There are three jobs created for Log
Shipping. One of them is for backing up the transaction log on the primary
server and the second is to copy it to some place and the last one is to
restore that copied transaction log file to the secondary server. Check
their job histories accordingly to find a track of the error.
Ekrem nsoy
"Jason Huang" <JasonHuang8888@.hotmail.com> wrote in message
news:OhOaSWbTIHA.4272@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>

msdb and log shipping question

Hi,
We have set up an log shipping for DatabaseA between Server1 and Server2.
Now that log shipping was canceled and the DatabaseA in Server2 was also
deleted.
Is there any info still kept in the Server2 regarding to the log shipping
and DatabaseA?
I built a new log shipping plan but it was no good cause the transaction
didn't copy to the Server2, while other log shipping for other databases
were OK.
Thanks for help.
Jason
Hi Jason
Have you looked at http://msdn2.microsoft.com/en-us/library/ms187045.aspx
John
"Jason Huang" wrote:

> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>
>
|||If you did not remove the Log Shipping according to the procedure then the
jobs of old Log Shipping must be left in the Jobs node under SQL Server
Agent. You better purge them.
After deletion of the DatabaseA from the Server2, did you restore a copy of
the DatabaseA on the Server1 on Server2 in a STANDBY or NORECOVERY recovery
state?
You can check the history of the jobs that are created for the new Log
Shipping to find the exact error. There are three jobs created for Log
Shipping. One of them is for backing up the transaction log on the primary
server and the second is to copy it to some place and the last one is to
restore that copied transaction log file to the secondary server. Check
their job histories accordingly to find a track of the error.
Ekrem nsoy
"Jason Huang" <JasonHuang8888@.hotmail.com> wrote in message
news:OhOaSWbTIHA.4272@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>

msdb and log shipping question

Hi,
We have set up an log shipping for DatabaseA between Server1 and Server2.
Now that log shipping was canceled and the DatabaseA in Server2 was also
deleted.
Is there any info still kept in the Server2 regarding to the log shipping
and DatabaseA?
I built a new log shipping plan but it was no good cause the transaction
didn't copy to the Server2, while other log shipping for other databases
were OK.
Thanks for help.
JasonHi Jason
Have you looked at http://msdn2.microsoft.com/en-us/library/ms187045.aspx
John
"Jason Huang" wrote:
> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>
>|||If you did not remove the Log Shipping according to the procedure then the
jobs of old Log Shipping must be left in the Jobs node under SQL Server
Agent. You better purge them.
After deletion of the DatabaseA from the Server2, did you restore a copy of
the DatabaseA on the Server1 on Server2 in a STANDBY or NORECOVERY recovery
state?
You can check the history of the jobs that are created for the new Log
Shipping to find the exact error. There are three jobs created for Log
Shipping. One of them is for backing up the transaction log on the primary
server and the second is to copy it to some place and the last one is to
restore that copied transaction log file to the secondary server. Check
their job histories accordingly to find a track of the error.
--
Ekrem Önsoy
"Jason Huang" <JasonHuang8888@.hotmail.com> wrote in message
news:OhOaSWbTIHA.4272@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>