Log Shipping with clustered database.

Hi,
We are running SQL Server Failover cluster in Active/Passive mode.
Now, we want to setup DR server for this clustered database using
Log shipping.
But my concern is, can we do log shipping with clustered database ?
and the answer of this question is Yes then Please let me know How ?
Thanks & Regards,
Sajid C.
Yep...you can. Just like how you do it in a non-clustered instance. The only
problem you will have in here is if you want to be notified thru email if
your restore jobs fail as MAPI is not supported in a clustered environment.
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God has plan for
them"
"csajid@.gmail.com" wrote:

> Hi,
> We are running SQL Server Failover cluster in Active/Passive mode.
> Now, we want to setup DR server for this clustered database using
> Log shipping.
> But my concern is, can we do log shipping with clustered database ?
> and the answer of this question is Yes then Please let me know How ?
>
> Thanks & Regards,
> Sajid C.
>
|||Hi,
Thanks for your reply.
Can you please provide me some document or any link for the same.
What are the necessary steps which should i take to do this task.
Thanks & Regards,
Sajid C.
bass_player wrote:[vbcol=seagreen]
> Yep...you can. Just like how you do it in a non-clustered instance. The only
> problem you will have in here is if you want to be notified thru email if
> your restore jobs fail as MAPI is not supported in a clustered environment.
> --
> MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
> "Helping people grow and develop their full potential as God has plan for
> them"
>
> "csajid@.gmail.com" wrote:

Log Shipping with clustered database.

Hi,
We are running SQL Server Failover cluster in Active/Passive mode.
Now, we want to setup DR server for this clustered database using
Log shipping.
But my concern is, can we do log shipping with clustered database ?
and the answer of this question is Yes then Please let me know How ?
Thanks & Regards,
Sajid C.Yep...you can. Just like how you do it in a non-clustered instance. The only
problem you will have in here is if you want to be notified thru email if
your restore jobs fail as MAPI is not supported in a clustered environment.
--
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God has plan for
them"
"csajid@.gmail.com" wrote:
> Hi,
> We are running SQL Server Failover cluster in Active/Passive mode.
> Now, we want to setup DR server for this clustered database using
> Log shipping.
> But my concern is, can we do log shipping with clustered database ?
> and the answer of this question is Yes then Please let me know How ?
>
> Thanks & Regards,
> Sajid C.
>|||Hi,
Thanks for your reply.
Can you please provide me some document or any link for the same.
What are the necessary steps which should i take to do this task.
Thanks & Regards,
Sajid C.
bass_player wrote:
> Yep...you can. Just like how you do it in a non-clustered instance. The only
> problem you will have in here is if you want to be notified thru email if
> your restore jobs fail as MAPI is not supported in a clustered environment.
> --
> MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
> "Helping people grow and develop their full potential as God has plan for
> them"
>
> "csajid@.gmail.com" wrote:
> > Hi,
> >
> > We are running SQL Server Failover cluster in Active/Passive mode.
> >
> > Now, we want to setup DR server for this clustered database using
> > Log shipping.
> >
> > But my concern is, can we do log shipping with clustered database ?
> > and the answer of this question is Yes then Please let me know How ?
> >
> >
> > Thanks & Regards,
> > Sajid C.
> >
> >

Log Shipping with clustered database.

Hi,
We are running SQL Server Failover cluster in Active/Passive mode.
Now, we want to setup DR server for this clustered database using
Log shipping.
But my concern is, can we do log shipping with clustered database ?
and the answer of this question is Yes then Please let me know How ?
Thanks & Regards,
Sajid C.Yep...you can. Just like how you do it in a non-clustered instance. The onl
y
problem you will have in here is if you want to be notified thru email if
your restore jobs fail as MAPI is not supported in a clustered environment.
--
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God has plan for
them"
"csajid@.gmail.com" wrote:

> Hi,
> We are running SQL Server Failover cluster in Active/Passive mode.
> Now, we want to setup DR server for this clustered database using
> Log shipping.
> But my concern is, can we do log shipping with clustered database ?
> and the answer of this question is Yes then Please let me know How ?
>
> Thanks & Regards,
> Sajid C.
>|||Hi,
Thanks for your reply.
Can you please provide me some document or any link for the same.
What are the necessary steps which should i take to do this task.
Thanks & Regards,
Sajid C.
bass_player wrote:[vbcol=seagreen]
> Yep...you can. Just like how you do it in a non-clustered instance. The o
nly
> problem you will have in here is if you want to be notified thru email if
> your restore jobs fail as MAPI is not supported in a clustered environment
.
> --
> MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
> "Helping people grow and develop their full potential as God has plan for
> them"
>
> "csajid@.gmail.com" wrote:
>

log shipping status

We have set up log shipping in standby mode so users can run some reports.
Every once in while, the restores long runner and our users would like to
know how much more time before its done.
Is there any query they could run to see what files its restoring or the
last file it has restored so they can get a feel of what Tlog file is being
processed.
It may not be perfect, but its a lot better if they know that the last Tlog
file restored or the current file its restoring is just 10 mins ago vs 10
hrs ago.
Thanks
Hassan
Take a look at DBCC LOGINFO(dbid) command
"Hassan" <hassan@.test.com> wrote in message
news:OIv5slyKIHA.3848@.TK2MSFTNGP05.phx.gbl...
> We have set up log shipping in standby mode so users can run some reports.
> Every once in while, the restores long runner and our users would like to
> know how much more time before its done.
> Is there any query they could run to see what files its restoring or the
> last file it has restored so they can get a feel of what Tlog file is
> being processed.
> It may not be perfect, but its a lot better if they know that the last
> Tlog file restored or the current file its restoring is just 10 mins ago
> vs 10 hrs ago.
> Thanks
>

log shipping status

We have set up log shipping in standby mode so users can run some reports.
Every once in while, the restores long runner and our users would like to
know how much more time before its done.
Is there any query they could run to see what files its restoring or the
last file it has restored so they can get a feel of what Tlog file is being
processed.
It may not be perfect, but its a lot better if they know that the last Tlog
file restored or the current file its restoring is just 10 mins ago vs 10
hrs ago.
ThanksHassan
Take a look at DBCC LOGINFO(dbid) command
"Hassan" <hassan@.test.com> wrote in message
news:OIv5slyKIHA.3848@.TK2MSFTNGP05.phx.gbl...
> We have set up log shipping in standby mode so users can run some reports.
> Every once in while, the restores long runner and our users would like to
> know how much more time before its done.
> Is there any query they could run to see what files its restoring or the
> last file it has restored so they can get a feel of what Tlog file is
> being processed.
> It may not be perfect, but its a lot better if they know that the last
> Tlog file restored or the current file its restoring is just 10 mins ago
> vs 10 hrs ago.
> Thanks
>

log shipping status

We have set up log shipping in standby mode so users can run some reports.
Every once in while, the restores long runner and our users would like to
know how much more time before its done.
Is there any query they could run to see what files its restoring or the
last file it has restored so they can get a feel of what Tlog file is being
processed.
It may not be perfect, but its a lot better if they know that the last Tlog
file restored or the current file its restoring is just 10 mins ago vs 10
hrs ago.
ThanksHassan
Take a look at DBCC LOGINFO(dbid) command
"Hassan" <hassan@.test.com> wrote in message
news:OIv5slyKIHA.3848@.TK2MSFTNGP05.phx.gbl...
> We have set up log shipping in standby mode so users can run some reports.
> Every once in while, the restores long runner and our users would like to
> know how much more time before its done.
> Is there any query they could run to see what files its restoring or the
> last file it has restored so they can get a feel of what Tlog file is
> being processed.
> It may not be perfect, but its a lot better if they know that the last
> Tlog file restored or the current file its restoring is just 10 mins ago
> vs 10 hrs ago.
> Thanks
>

log shipping sql 2005 database remains in (restoring...) mode

I've been playing with the SQL 2005 log shipping and have been running into a
few problems.
My system is configured on a virtual server with two instances of SQL 2005.
The OS is Windows 2003. I'm shipping logs from the default instance to the
named instance with the default having the primary database and the named,
the secondary.
When I use the log shipping wizard, and have it do the initial restore to
the secondary, all appears to work well but the database remains in
"(Restoring ...) in the Management Studio (MS) GUI. So after starting over
and manually restoring the database to the secondary, I used the wizard again
to set this up and now the Agent jobs indicate success in applying the logs
but again, the database continues to show as (Restoring ...) in the MS GUI.
It is indeed unavailable as you can't query it in a Query window. I tried
this with upgraded SQL 2000 databases and newly created SQL 2005 databases,
both with the same result.
Has anyone run into this and can you tell me what might be happening?
Hi
By default, you can not access the destination DB in a log shipping
partnership. It was the same in SQL Server 2000.
If you want to have read only access, subject to having your connections
dropped when the next log restore occurs,
you need to execute a restore with the additional parameter of "STANDBY =
{standby_file_name}".
This can not be done in the GUI.
What are you trying to achieve?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
> I've been playing with the SQL 2005 log shipping and have been running
> into a
> few problems.
> My system is configured on a virtual server with two instances of SQL
> 2005.
> The OS is Windows 2003. I'm shipping logs from the default instance to the
> named instance with the default having the primary database and the named,
> the secondary.
> When I use the log shipping wizard, and have it do the initial restore to
> the secondary, all appears to work well but the database remains in
> "(Restoring ...) in the Management Studio (MS) GUI. So after starting over
> and manually restoring the database to the secondary, I used the wizard
> again
> to set this up and now the Agent jobs indicate success in applying the
> logs
> but again, the database continues to show as (Restoring ...) in the MS
> GUI.
> It is indeed unavailable as you can't query it in a Query window. I tried
> this with upgraded SQL 2000 databases and newly created SQL 2005
> databases,
> both with the same result.
> Has anyone run into this and can you tell me what might be happening?
|||My goal was to have a readable database on the destination side that could be
accessible in case of failure of the primary database. I guess I'm ignorant
of a basic tenent of log shipping and for that I apologize. Apparently, the
process is working as it should be and I thank you for pointing that out. (I
never used log shipping in 2000 since we only have standard edition). I will
"read up" on the subject a bit more. Thanks much!
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> By default, you can not access the destination DB in a log shipping
> partnership. It was the same in SQL Server 2000.
> If you want to have read only access, subject to having your connections
> dropped when the next log restore occurs,
> you need to execute a restore with the additional parameter of "STANDBY =
> {standby_file_name}".
> This can not be done in the GUI.
> What are you trying to achieve?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
> news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
>
>

log shipping sql 2005 database remains in (restoring...) mode

I've been playing with the SQL 2005 log shipping and have been running into
a
few problems.
My system is configured on a virtual server with two instances of SQL 2005.
The OS is Windows 2003. I'm shipping logs from the default instance to the
named instance with the default having the primary database and the named,
the secondary.
When I use the log shipping wizard, and have it do the initial restore to
the secondary, all appears to work well but the database remains in
"(Restoring ...) in the Management Studio (MS) GUI. So after starting over
and manually restoring the database to the secondary, I used the wizard agai
n
to set this up and now the Agent jobs indicate success in applying the logs
but again, the database continues to show as (Restoring ...) in the MS GUI.
It is indeed unavailable as you can't query it in a Query window. I tried
this with upgraded SQL 2000 databases and newly created SQL 2005 databases,
both with the same result.
Has anyone run into this and can you tell me what might be happening?Hi
By default, you can not access the destination DB in a log shipping
partnership. It was the same in SQL Server 2000.
If you want to have read only access, subject to having your connections
dropped when the next log restore occurs,
you need to execute a restore with the additional parameter of "STANDBY =
{standby_file_name}".
This can not be done in the GUI.
What are you trying to achieve?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
> I've been playing with the SQL 2005 log shipping and have been running
> into a
> few problems.
> My system is configured on a virtual server with two instances of SQL
> 2005.
> The OS is Windows 2003. I'm shipping logs from the default instance to the
> named instance with the default having the primary database and the named,
> the secondary.
> When I use the log shipping wizard, and have it do the initial restore to
> the secondary, all appears to work well but the database remains in
> "(Restoring ...) in the Management Studio (MS) GUI. So after starting over
> and manually restoring the database to the secondary, I used the wizard
> again
> to set this up and now the Agent jobs indicate success in applying the
> logs
> but again, the database continues to show as (Restoring ...) in the MS
> GUI.
> It is indeed unavailable as you can't query it in a Query window. I tried
> this with upgraded SQL 2000 databases and newly created SQL 2005
> databases,
> both with the same result.
> Has anyone run into this and can you tell me what might be happening?|||My goal was to have a readable database on the destination side that could b
e
accessible in case of failure of the primary database. I guess I'm ignorant
of a basic tenent of log shipping and for that I apologize. Apparently, the
process is working as it should be and I thank you for pointing that out. (
I
never used log shipping in 2000 since we only have standard edition). I wil
l
"read up" on the subject a bit more. Thanks much!
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> By default, you can not access the destination DB in a log shipping
> partnership. It was the same in SQL Server 2000.
> If you want to have read only access, subject to having your connections
> dropped when the next log restore occurs,
> you need to execute a restore with the additional parameter of "STANDBY =
> {standby_file_name}".
> This can not be done in the GUI.
> What are you trying to achieve?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
> news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
>
>

log shipping sql 2005 database remains in (restoring...) mode

I've been playing with the SQL 2005 log shipping and have been running into a
few problems.
My system is configured on a virtual server with two instances of SQL 2005.
The OS is Windows 2003. I'm shipping logs from the default instance to the
named instance with the default having the primary database and the named,
the secondary.
When I use the log shipping wizard, and have it do the initial restore to
the secondary, all appears to work well but the database remains in
"(Restoring ...) in the Management Studio (MS) GUI. So after starting over
and manually restoring the database to the secondary, I used the wizard again
to set this up and now the Agent jobs indicate success in applying the logs
but again, the database continues to show as (Restoring ...) in the MS GUI.
It is indeed unavailable as you can't query it in a Query window. I tried
this with upgraded SQL 2000 databases and newly created SQL 2005 databases,
both with the same result.
Has anyone run into this and can you tell me what might be happening?Hi
By default, you can not access the destination DB in a log shipping
partnership. It was the same in SQL Server 2000.
If you want to have read only access, subject to having your connections
dropped when the next log restore occurs,
you need to execute a restore with the additional parameter of "STANDBY ={standby_file_name}".
This can not be done in the GUI.
What are you trying to achieve?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
> I've been playing with the SQL 2005 log shipping and have been running
> into a
> few problems.
> My system is configured on a virtual server with two instances of SQL
> 2005.
> The OS is Windows 2003. I'm shipping logs from the default instance to the
> named instance with the default having the primary database and the named,
> the secondary.
> When I use the log shipping wizard, and have it do the initial restore to
> the secondary, all appears to work well but the database remains in
> "(Restoring ...) in the Management Studio (MS) GUI. So after starting over
> and manually restoring the database to the secondary, I used the wizard
> again
> to set this up and now the Agent jobs indicate success in applying the
> logs
> but again, the database continues to show as (Restoring ...) in the MS
> GUI.
> It is indeed unavailable as you can't query it in a Query window. I tried
> this with upgraded SQL 2000 databases and newly created SQL 2005
> databases,
> both with the same result.
> Has anyone run into this and can you tell me what might be happening?|||My goal was to have a readable database on the destination side that could be
accessible in case of failure of the primary database. I guess I'm ignorant
of a basic tenent of log shipping and for that I apologize. Apparently, the
process is working as it should be and I thank you for pointing that out. (I
never used log shipping in 2000 since we only have standard edition). I will
"read up" on the subject a bit more. Thanks much!
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> By default, you can not access the destination DB in a log shipping
> partnership. It was the same in SQL Server 2000.
> If you want to have read only access, subject to having your connections
> dropped when the next log restore occurs,
> you need to execute a restore with the additional parameter of "STANDBY => {standby_file_name}".
> This can not be done in the GUI.
> What are you trying to achieve?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
> news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
> > I've been playing with the SQL 2005 log shipping and have been running
> > into a
> > few problems.
> >
> > My system is configured on a virtual server with two instances of SQL
> > 2005.
> > The OS is Windows 2003. I'm shipping logs from the default instance to the
> > named instance with the default having the primary database and the named,
> > the secondary.
> >
> > When I use the log shipping wizard, and have it do the initial restore to
> > the secondary, all appears to work well but the database remains in
> > "(Restoring ...) in the Management Studio (MS) GUI. So after starting over
> > and manually restoring the database to the secondary, I used the wizard
> > again
> > to set this up and now the Agent jobs indicate success in applying the
> > logs
> > but again, the database continues to show as (Restoring ...) in the MS
> > GUI.
> > It is indeed unavailable as you can't query it in a Query window. I tried
> > this with upgraded SQL 2000 databases and newly created SQL 2005
> > databases,
> > both with the same result.
> >
> > Has anyone run into this and can you tell me what might be happening?
>
>

Log Shipping -SQL 2000

Is there a way to detach a database that is in warm
standby mode and attach it back in the same mode and
continue with T-logs restores ?Not to my knowledge, no.
Why would you want to do such a thing? It seems illogical.
>--Original Message--
>Is there a way to detach a database that is in warm
>standby mode and attach it back in the same mode and
>continue with T-logs restores ?
>.
>sql

Log Shipping Resync process

Does anyone know how to reset or resync the Log Shipping Transaction on
the Standby Server?
I am in testing mode and ran a backup log dbname with truncate_only and
it caused my log shipping mechanism to fail and now I need to know how
to resync the process without having to Re-implement the maintenance
plan.
P.S. Is there a better method of shrinking my database logs using Log
Shipping?
Thanks,
BillTry this.
1) Disable all the logshipping jobs so they don't run
while you work. These are "Logshipping copy %"
and "Logshipping restore %" on the secondary; and "DB
Backup" and "Transaction log backup" on the primary.
2) Manually run the "DB Backup" job on the primary.
3) Copy that backup file to the secondary and restore the
file using the norecovery and standby options in the
restore database command. The standby option is if your
secondary was in readonly mode.
4) The databases should now be in sync. Run the
trasaction log backup on the primary. Then run the
Logshipping copy job on the secondary. Then run the
Logshipping restore job on the secondary. They should all
run successfully.
5) remember to reenable all your logshipping jobs.
This was a very quick summary. Hope it helps.
>--Original Message--
>Does anyone know how to reset or resync the Log Shipping
Transaction on
>the Standby Server?
>
>I am in testing mode and ran a backup log dbname with
truncate_only and
>it caused my log shipping mechanism to fail and now I
need to know how
>to resync the process without having to Re-implement the
maintenance
>plan.
>P.S. Is there a better method of shrinking my database
logs using Log
>Shipping?
>Thanks,
>Bill
>.
>

Log shipping error - database in use

I am using MS builtin log-shipping functionality in
SQL2000.
My log shipping maintenance plan has a secondary load
state of 'standby' mode. And I have selected
the 'terminate users in database' option - however,
occasionally my log-shipping job is failing with '3101 -
database in use' error.
However, I thought that by selecting 'terminate users in
database' option - this should never happen ?
Has anyone seen anything similar before ?'terminate users in database' will not work always and
does not guarantee anything, a terminated process may drop
into a rollback mode and then it could take a long time to
finally get disappeared.
>--Original Message--
>I am using MS builtin log-shipping functionality in
>SQL2000.
>My log shipping maintenance plan has a secondary load
>state of 'standby' mode. And I have selected
>the 'terminate users in database' option - however,
>occasionally my log-shipping job is failing with '3101 -
>database in use' error.
>However, I thought that by selecting 'terminate users in
>database' option - this should never happen ?
>Has anyone seen anything similar before ?
>.
>

log shipping enquires

Hi,
I have set up log shipping in the following :
load/copy frequency - 1 mins
backup frequency - 5 mins
secondary db - standby mode
issue :
when i made some changes to a record of the primary db's tbl , it was not
reflected in the secondary db's table.
Is it due to the fact that the secondary db is a Read-Only ?
and if i do want to delete log shipping , what shld be the correct way in
doing this
appreciate ur advise
tks & rdgs
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1the reason why the cahnges in primary DB are not reflected on secondary
maybe that you didnt setup the log shipping properly.
You can cross check if if have any out of sync errors...
and abt deleting the log shipping the best way will be ... from the
maintenance plan remove log shipping and then delete the plan.|||Did you wait long enough for the changs to be sent? You can verify the tran
log backups by looking in the directories on each machine. You can also
verify the backup and restore by looking in the errorlog. The log shipping
monitor will display the status of everything. If it isn't getting there,
you will be seeing errors.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"maxzsim via SQLMonster.com" <u14644@.uwe> wrote in message
news:5af9a1affdb26@.uwe...
> Hi,
> I have set up log shipping in the following :
> load/copy frequency - 1 mins
> backup frequency - 5 mins
> secondary db - standby mode
> issue :
> when i made some changes to a record of the primary db's tbl , it was not
> reflected in the secondary db's table.
> Is it due to the fact that the secondary db is a Read-Only ?
> and if i do want to delete log shipping , what shld be the correct way in
> doing this
> appreciate ur advise
> tks & rdgs
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1|||tks ..
Shadow wrote:
>the reason why the cahnges in primary DB are not reflected on secondary
>maybe that you didnt setup the log shipping properly.
>You can cross check if if have any out of sync errors...
>and abt deleting the log shipping the best way will be ... from the
>maintenance plan remove log shipping and then delete the plan.
--
Message posted via http://www.sqlmonster.com|||Hi,
I have managed to set up the log shipping correctly as i could see the
changes on my destination DB . However, i have specified that copy is 0
minutes , and load is 1 minutes but it took something like around 5 minutes
to see the updated data in my destination DB.
how can i acutally make the updates "almost immediate" ? or this is normal
as copying the txn log takes time and need to wait till user "give up" the
exclusive lock , then copy the txn log over and then load from the txn log ?
appreciate ur advice
tks & rdgs
Michael Hotek wrote:
>Did you wait long enough for the changs to be sent? You can verify the tran
>log backups by looking in the directories on each machine. You can also
>verify the backup and restore by looking in the errorlog. The log shipping
>monitor will display the status of everything. If it isn't getting there,
>you will be seeing errors.
>> Hi,
>[quoted text clipped - 16 lines]
>> tks & rdgs
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1|||You can't. The entire thing runs as a set of jobs. The most frequently a
job can run is every minute and that is NOT recommended for log shipping
unless you want to watch the monitor throw a LOT of errors. You usually set
up the backup job at 2 minutes or more. (2 minutes is the lowest you want
to go). That means a new backup will be generated every 2 minutes. It then
takes time to copy over and time to restore. Most of that time is simply
the job shutting down and waiting for the SQL Server Agent to kick it off
again. 5 minutes start to finish is about the best you are going to get
with log shipping. If you need lower latency than that, you have to go to
either Database Mirroring (2005 only) or the replication engine.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"maxzsim via SQLMonster.com" <u14644@.uwe> wrote in message
news:5b378dc949992@.uwe...
> Hi,
> I have managed to set up the log shipping correctly as i could see the
> changes on my destination DB . However, i have specified that copy is 0
> minutes , and load is 1 minutes but it took something like around 5
> minutes
> to see the updated data in my destination DB.
> how can i acutally make the updates "almost immediate" ? or this is
> normal
> as copying the txn log takes time and need to wait till user "give up" the
> exclusive lock , then copy the txn log over and then load from the txn log
> ?
> appreciate ur advice
> tks & rdgs
>
> Michael Hotek wrote:
>>Did you wait long enough for the changs to be sent? You can verify the
>>tran
>>log backups by looking in the directories on each machine. You can also
>>verify the backup and restore by looking in the errorlog. The log
>>shipping
>>monitor will display the status of everything. If it isn't getting there,
>>you will be seeing errors.
>> Hi,
>>[quoted text clipped - 16 lines]
>> tks & rdgs
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1|||tks for ur clarifications ..
Cheers ..
Michael Hotek wrote:
>You can't. The entire thing runs as a set of jobs. The most frequently a
>job can run is every minute and that is NOT recommended for log shipping
>unless you want to watch the monitor throw a LOT of errors. You usually set
>up the backup job at 2 minutes or more. (2 minutes is the lowest you want
>to go). That means a new backup will be generated every 2 minutes. It then
>takes time to copy over and time to restore. Most of that time is simply
>the job shutting down and waiting for the SQL Server Agent to kick it off
>again. 5 minutes start to finish is about the best you are going to get
>with log shipping. If you need lower latency than that, you have to go to
>either Database Mirroring (2005 only) or the replication engine.
>> Hi,
>[quoted text clipped - 26 lines]
>> tks & rdgs
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1

Log shipping and switching recovery modes

I'm a bit confused (a normal state).
With log shipping, is it possible to switch recovery mode from/to Full and
Bulk Logged to alleviate problems caused by reindexing/defragging?
Some documents appear to say Full recovery mode only for log shipping but
others say no problem with Bulk Logged.
Paul
I just tested in my Pubs DB.
1; Set in Full mode.
2; Full Backup.
3; Set in BL mode.
4; TLog Backup.
5; Did a successful Restore.
Despite my 30 second test, Id highly recommend your doing lots of testing
before you implement anything like this.
ChrisR
"Paul Cahill" wrote:

> I'm a bit confused (a normal state).
> With log shipping, is it possible to switch recovery mode from/to Full and
> Bulk Logged to alleviate problems caused by reindexing/defragging?
> Some documents appear to say Full recovery mode only for log shipping but
> others say no problem with Bulk Logged.
> Paul
>
>
|||Thanks Chris
Paul
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:20A96EA2-0684-42C7-9C75-952285D92C25@.microsoft.com...[vbcol=seagreen]
>I just tested in my Pubs DB.
> 1; Set in Full mode.
> 2; Full Backup.
> 3; Set in BL mode.
> 4; TLog Backup.
> 5; Did a successful Restore.
> Despite my 30 second test, Id highly recommend your doing lots of testing
> before you implement anything like this.
> --
> ChrisR
>
> "Paul Cahill" wrote:

Log shipping and switching recovery modes

I'm a bit confused (a normal state).
With log shipping, is it possible to switch recovery mode from/to Full and
Bulk Logged to alleviate problems caused by reindexing/defragging?
Some documents appear to say Full recovery mode only for log shipping but
others say no problem with Bulk Logged.
PaulI just tested in my Pubs DB.
1; Set in Full mode.
2; Full Backup.
3; Set in BL mode.
4; TLog Backup.
5; Did a successful Restore.
Despite my 30 second test, Id highly recommend your doing lots of testing
before you implement anything like this.
--
ChrisR
"Paul Cahill" wrote:
> I'm a bit confused (a normal state).
> With log shipping, is it possible to switch recovery mode from/to Full and
> Bulk Logged to alleviate problems caused by reindexing/defragging?
> Some documents appear to say Full recovery mode only for log shipping but
> others say no problem with Bulk Logged.
> Paul
>
>|||Thanks Chris
Paul
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:20A96EA2-0684-42C7-9C75-952285D92C25@.microsoft.com...
>I just tested in my Pubs DB.
> 1; Set in Full mode.
> 2; Full Backup.
> 3; Set in BL mode.
> 4; TLog Backup.
> 5; Did a successful Restore.
> Despite my 30 second test, Id highly recommend your doing lots of testing
> before you implement anything like this.
> --
> ChrisR
>
> "Paul Cahill" wrote:
>> I'm a bit confused (a normal state).
>> With log shipping, is it possible to switch recovery mode from/to Full
>> and
>> Bulk Logged to alleviate problems caused by reindexing/defragging?
>> Some documents appear to say Full recovery mode only for log shipping but
>> others say no problem with Bulk Logged.
>> Paul
>>

Log shipping and switching recovery modes

I'm a bit confused (a normal state).
With log shipping, is it possible to switch recovery mode from/to Full and
Bulk Logged to alleviate problems caused by reindexing/defragging?
Some documents appear to say Full recovery mode only for log shipping but
others say no problem with Bulk Logged.
PaulI just tested in my Pubs DB.
1; Set in Full mode.
2; Full Backup.
3; Set in BL mode.
4; TLog Backup.
5; Did a successful Restore.
Despite my 30 second test, Id highly recommend your doing lots of testing
before you implement anything like this.
ChrisR
"Paul Cahill" wrote:

> I'm a bit confused (a normal state).
> With log shipping, is it possible to switch recovery mode from/to Full and
> Bulk Logged to alleviate problems caused by reindexing/defragging?
> Some documents appear to say Full recovery mode only for log shipping but
> others say no problem with Bulk Logged.
> Paul
>
>|||Thanks Chris
Paul
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:20A96EA2-0684-42C7-9C75-952285D92C25@.microsoft.com...[vbcol=seagreen]
>I just tested in my Pubs DB.
> 1; Set in Full mode.
> 2; Full Backup.
> 3; Set in BL mode.
> 4; TLog Backup.
> 5; Did a successful Restore.
> Despite my 30 second test, Id highly recommend your doing lots of testing
> before you implement anything like this.
> --
> ChrisR
>
> "Paul Cahill" wrote:
>

Log Shipping and SQL Server Licence Requirement

Given that the secondary server can be configured in standby mode, what is
the minimum SQL Server licensing requirement for the secondary server?
thanks in advance
JamesThe "secondary server" is not in standby mode, only the database(s) you log
ship is. So you need a
license for that server as well. See http://www.microsoft.com/sql/howtobuy/faq.asp

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> Given that the secondary server can be configured in standby mode, what is
> the minimum SQL Server licensing requirement for the secondary server?
> thanks in advance
> James|||The EULA states that the passive node in a cluster configuration as well as
the SQL Server hosting only standby databases in a log-shipping
configuration may be hosted for disaster recovery purposes as long as SQL
Server is licensed for the host with the most CPUs if one were licensed
under the per-processor mode.
For CAL based installations, it is the number of CALs that need to be kept
up to date, but the SQL Server host that is acting in a passive capacity can
be installed under the active's license as long as only one is active at any
given moment.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
The "secondary server" is not in standby mode, only the database(s) you
log ship is. So you need a
license for that server as well. See
http://www.microsoft.com/sql/howtobuy/faq.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> Given that the secondary server can be configured in standby mode, what
is
> the minimum SQL Server licensing requirement for the secondary server?
> thanks in advance
> James|||I believe MS wants you license the warm standby as a production server.
Hence, it needs to have money spent on it..
Eric D. Smith
St. Louis, MO
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uHl12Jn8EHA.3416@.TK2MSFTNGP09.phx.gbl...
> That doesn't goes with the FAQ page I referred to:
> Q. If I am doing log shipping in an active/passive failover
configuration, how should I
> license the backup server?
>
> A. In this scenario, the active and passive servers must be
licensed identically, so that the
> passive server can process the same workload as the active server in the
event of a failover.
>
> Makes one wonder whether to go by the EULA or the FAQ page. I guess that
the EULA is more legally
> binding, so I would carefully read the text...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
> news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
as[vbcol=seagreen]
SQL[vbcol=seagreen]
kept[vbcol=seagreen]
can[vbcol=seagreen]
any[vbcol=seagreen]
wrote[vbcol=seagreen]
what[vbcol=seagreen]
server?[vbcol=seagreen]
>
>

Log Shipping and SQL Server Licence Requirement

Given that the secondary server can be configured in standby mode, what is
the minimum SQL Server licensing requirement for the secondary server?
thanks in advance
James
The "secondary server" is not in standby mode, only the database(s) you log ship is. So you need a
license for that server as well. See http://www.microsoft.com/sql/howtobuy/faq.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> Given that the secondary server can be configured in standby mode, what is
> the minimum SQL Server licensing requirement for the secondary server?
> thanks in advance
> James
|||The EULA states that the passive node in a cluster configuration as well as
the SQL Server hosting only standby databases in a log-shipping
configuration may be hosted for disaster recovery purposes as long as SQL
Server is licensed for the host with the most CPUs if one were licensed
under the per-processor mode.
For CAL based installations, it is the number of CALs that need to be kept
up to date, but the SQL Server host that is acting in a passive capacity can
be installed under the active's license as long as only one is active at any
given moment.
Sincerely,
Anthony Thomas

"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
The "secondary server" is not in standby mode, only the database(s) you
log ship is. So you need a
license for that server as well. See
http://www.microsoft.com/sql/howtobuy/faq.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> Given that the secondary server can be configured in standby mode, what
is
> the minimum SQL Server licensing requirement for the secondary server?
> thanks in advance
> James
|||That doesn't goes with the FAQ page I referred to:
Q. If I am doing log shipping in an active/passive failover configuration, how should I
license the backup server?
A. In this scenario, the active and passive servers must be licensed identically, so that the
passive server can process the same workload as the active server in the event of a failover.
Makes one wonder whether to go by the EULA or the FAQ page. I guess that the EULA is more legally
binding, so I would carefully read the text...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
> The EULA states that the passive node in a cluster configuration as well as
> the SQL Server hosting only standby databases in a log-shipping
> configuration may be hosted for disaster recovery purposes as long as SQL
> Server is licensed for the host with the most CPUs if one were licensed
> under the per-processor mode.
> For CAL based installations, it is the number of CALs that need to be kept
> up to date, but the SQL Server host that is acting in a passive capacity can
> be installed under the active's license as long as only one is active at any
> given moment.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
> The "secondary server" is not in standby mode, only the database(s) you
> log ship is. So you need a
> license for that server as well. See
> http://www.microsoft.com/sql/howtobuy/faq.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
> news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> is
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||I believe MS wants you license the warm standby as a production server.
Hence, it needs to have money spent on it..
Eric D. Smith
St. Louis, MO
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uHl12Jn8EHA.3416@.TK2MSFTNGP09.phx.gbl...
> That doesn't goes with the FAQ page I referred to:
> Q. If I am doing log shipping in an active/passive failover
configuration, how should I
> license the backup server?
>
> A. In this scenario, the active and passive servers must be
licensed identically, so that the
> passive server can process the same workload as the active server in the
event of a failover.
>
> Makes one wonder whether to go by the EULA or the FAQ page. I guess that
the EULA is more legally[vbcol=seagreen]
> binding, so I would carefully read the text...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
> news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
as[vbcol=seagreen]
SQL[vbcol=seagreen]
kept[vbcol=seagreen]
can[vbcol=seagreen]
any[vbcol=seagreen]
wrote[vbcol=seagreen]
what[vbcol=seagreen]
server?
>
>

Log Shipping and SQL Server Licence Requirement

Given that the secondary server can be configured in standby mode, what is
the minimum SQL Server licensing requirement for the secondary server?
thanks in advance
JamesThe "secondary server" is not in standby mode, only the database(s) you log ship is. So you need a
license for that server as well. See http://www.microsoft.com/sql/howtobuy/faq.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> Given that the secondary server can be configured in standby mode, what is
> the minimum SQL Server licensing requirement for the secondary server?
> thanks in advance
> James|||This is a multi-part message in MIME format.
--=_NextPart_000_07A3_01C4F23E.E02BFD90
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
The EULA states that the passive node in a cluster configuration as well as
the SQL Server hosting only standby databases in a log-shipping
configuration may be hosted for disaster recovery purposes as long as SQL
Server is licensed for the host with the most CPUs if one were licensed
under the per-processor mode.
For CAL based installations, it is the number of CALs that need to be kept
up to date, but the SQL Server host that is acting in a passive capacity can
be installed under the active's license as long as only one is active at any
given moment.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
The "secondary server" is not in standby mode, only the database(s) you
log ship is. So you need a
license for that server as well. See
http://www.microsoft.com/sql/howtobuy/faq.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> Given that the secondary server can be configured in standby mode, what
is
> the minimum SQL Server licensing requirement for the secondary server?
>
> thanks in advance
> James
--=_NextPart_000_07A3_01C4F23E.E02BFD90
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

The EULA states that the passive node =in a cluster configuration as well as the SQL Server hosting only standby =databases in a log-shipping configuration may be hosted for disaster recovery =purposes as long as SQL Server is licensed for the host with the most CPUs if one =were licensed under the per-processor mode.
For CAL based installations, it is =the number of CALs that need to be kept up to date, but the SQL Server host that is =acting in a passive capacity can be installed under the active's license as long =as only one is active at any given moment.
Sincerely,
Anthony Thomas
--
"Tibor Karaszi" wrote in message news:%23ASMAQj8EHA.=3236@.TK2MSFTNGP15.phx.gbl...The "secondary server" is not in standby mode, only the database(s) you =log ship is. So you need a license for that server as well. See http://www.microsoft.com/sql/howtobuy/faq.asp">http://www.microso=ft.com/sql/howtobuy/faq.asp-- Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asp">http://www.karaszi.=com/sqlserver/default.asphttp://www.solidqualitylearning.com/">http://www.solidqualitylear=ning.com/http://www.sqlug.se/">http://www.sqlug.se/"James-=Aus" wrote in message news:7A4=6C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...> Given that the secondary server can be configured in standby mode, =what is> the minimum SQL Server licensing requirement for the =secondary server?>> thanks in advance> James

---

--=_NextPart_000_07A3_01C4F23E.E02BFD90--|||That doesn't goes with the FAQ page I referred to:
Q. If I am doing log shipping in an active/passive failover configuration, how should I
license the backup server?
A. In this scenario, the active and passive servers must be licensed identically, so that the
passive server can process the same workload as the active server in the event of a failover.
Makes one wonder whether to go by the EULA or the FAQ page. I guess that the EULA is more legally
binding, so I would carefully read the text...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
> The EULA states that the passive node in a cluster configuration as well as
> the SQL Server hosting only standby databases in a log-shipping
> configuration may be hosted for disaster recovery purposes as long as SQL
> Server is licensed for the host with the most CPUs if one were licensed
> under the per-processor mode.
> For CAL based installations, it is the number of CALs that need to be kept
> up to date, but the SQL Server host that is acting in a passive capacity can
> be installed under the active's license as long as only one is active at any
> given moment.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
> The "secondary server" is not in standby mode, only the database(s) you
> log ship is. So you need a
> license for that server as well. See
> http://www.microsoft.com/sql/howtobuy/faq.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
> news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> > Given that the secondary server can be configured in standby mode, what
> is
> > the minimum SQL Server licensing requirement for the secondary server?
> >
> > thanks in advance
> > James
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end|||I believe MS wants you license the warm standby as a production server.
Hence, it needs to have money spent on it.. :(
Eric D. Smith
St. Louis, MO
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uHl12Jn8EHA.3416@.TK2MSFTNGP09.phx.gbl...
> That doesn't goes with the FAQ page I referred to:
> Q. If I am doing log shipping in an active/passive failover
configuration, how should I
> license the backup server?
>
> A. In this scenario, the active and passive servers must be
licensed identically, so that the
> passive server can process the same workload as the active server in the
event of a failover.
>
> Makes one wonder whether to go by the EULA or the FAQ page. I guess that
the EULA is more legally
> binding, so I would carefully read the text...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
> news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > The EULA states that the passive node in a cluster configuration as well
as
> > the SQL Server hosting only standby databases in a log-shipping
> > configuration may be hosted for disaster recovery purposes as long as
SQL
> > Server is licensed for the host with the most CPUs if one were licensed
> > under the per-processor mode.
> >
> > For CAL based installations, it is the number of CALs that need to be
kept
> > up to date, but the SQL Server host that is acting in a passive capacity
can
> > be installed under the active's license as long as only one is active at
any
> > given moment.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > --
> >
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote
> > in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
> > The "secondary server" is not in standby mode, only the database(s) you
> > log ship is. So you need a
> > license for that server as well. See
> > http://www.microsoft.com/sql/howtobuy/faq.asp
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> > http://www.sqlug.se/
> >
> >
> > "James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
> > news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> > > Given that the secondary server can be configured in standby mode,
what
> > is
> > > the minimum SQL Server licensing requirement for the secondary
server?
> > >
> > > thanks in advance
> > > James
> >
> >
>
>

log shipping - synch

I have to schedule the automatic restore the standby database for
testing backups . The database was already in log shipping mode. Up to
what point do I need to restore the database without affecting the log
shipping sequence? Can we query the log shipping tables for the last
scn applied and recover up to that point? Any suggestoions are welcome.

Thanks

TramHi

Have you checked out other posts regarding re-syncing log shipping. Such as:
http://tinyurl.com/cot3k

If you want to look at manual log shipping check out
http://www.winnetmag.com/Artic*le/A...3231/23231.html
http://tinyurl.com/4ez3l
http://tinyurl.com/6rdth

John

"tram" <tram_e@.hotmail.com> wrote in message
news:1117879701.158308.305390@.o13g2000cwo.googlegr oups.com...
>I have to schedule the automatic restore the standby database for
> testing backups . The database was already in log shipping mode. Up to
> what point do I need to restore the database without affecting the log
> shipping sequence? Can we query the log shipping tables for the last
> scn applied and recover up to that point? Any suggestoions are welcome.
>
> Thanks
> Tram