When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.com
Easy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Showing posts with label following. Show all posts
Showing posts with label following. Show all posts
Wednesday, March 28, 2012
Log Shipping Setup Problem
When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I have
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is not
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Log Shipping Setup Problem
When using the Database Maintenance Plan WIzard to setup log shipping I have
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I ha
ve
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is n
ot
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
the following problem:
While Adding a Destination Database, usually when you select a server from
the server list, the Transaction Log Desination Directory is automatically
filled in with a default.
When I select one particular server from the list, this does not get
automatically filled in and the server name that I selected from the list
does not show up in the Server Name: field, even though it appeared in the
drop down list. Other server do not exhibit this behavior but function
correctly.
From what I understand, the server will not show up in the list if it is not
SQL Entreprise Edition, so I don't think that should be the problem.
Any ideas?
Thanks,
Matthew Bando
Matthew.Bando@.REMOVE-csctgi.comEasy solution. Evidently, having the destination (secondary) server
registered in EM is not enough. I actually had to open an active connectino
in EM to the secondary server before startnig the Database Maintenance Plan
Wizard.
Matthew
"Matthew Bando" wrote:
> When using the Database Maintenance Plan WIzard to setup log shipping I ha
ve
> the following problem:
> While Adding a Destination Database, usually when you select a server from
> the server list, the Transaction Log Desination Directory is automatically
> filled in with a default.
> When I select one particular server from the list, this does not get
> automatically filled in and the server name that I selected from the list
> does not show up in the Server Name: field, even though it appeared in the
> drop down list. Other server do not exhibit this behavior but function
> correctly.
> From what I understand, the server will not show up in the list if it is n
ot
> SQL Entreprise Edition, so I don't think that should be the problem.
> Any ideas?
> Thanks,
> Matthew Bando
> Matthew.Bando@.REMOVE-csctgi.com
Wednesday, March 21, 2012
Log Shipping Monitoring
When I execute the following SP:
EXEC msdb..sp_get_log_shipping_monitor_info @.secondary_database_name =
'pubs%'
I get some information regarding [copy_delta] and [load_delta]
I'm pretty sure copy_delta are there number of files copied over from the
source server. I don't know what the load_delta means though. Sometimes it
shows a low number then sometimes it shows a high number. I intially
thought it was the number of transaction logs that got loaded into the
standby server but when that number hits 69 and it only copied 3, it doesn't
make sense. There is also no documenation on BOL or microsoft's web site on
this.
Regards,
Tim
Hi Tim,
Based on my research, load_delta indicates the the difference in minutes
between the last updated date of the last backup file and the last updated
date of the last loaded file. In ths code of the sp_log_shipping_in_sync
stored procedure, which is called in sp_get_log_shipping_monitor_info, you
may see the following codes.
SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
Also, the @.last_updated is @.restoredt, which is got from the following
codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_backup_filename, @.backupdt OUTPUT
IF (@.rv <> 0)
SElECT @.backupdt = @.last_backup_last_updated
the@.compare_with is @.backupdt, which is got form the followig codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_loaded_filename, @.restoredt OUTPUT
IF (@.rv <> 0)
SElECT @.restoredt = @.last_loaded_last_updated
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks,
this is exactly what I am looking for.
Regards,
Tim
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PIofhxLNEHA.928@.cpmsftngxa10.phx.gbl...
> Hi Tim,
> Based on my research, load_delta indicates the the difference in minutes
> between the last updated date of the last backup file and the last
updated
> date of the last loaded file. In ths code of the sp_log_shipping_in_sync
> stored procedure, which is called in sp_get_log_shipping_monitor_info, you
> may see the following codes.
> SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
> Also, the @.last_updated is @.restoredt, which is got from the following
> codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_backup_filename, @.backupdt OUTPUT
> IF (@.rv <> 0)
> SElECT @.backupdt = @.last_backup_last_updated
> the@.compare_with is @.backupdt, which is got form the followig codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_loaded_filename, @.restoredt OUTPUT
> IF (@.rv <> 0)
> SElECT @.restoredt = @.last_loaded_last_updated
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>
EXEC msdb..sp_get_log_shipping_monitor_info @.secondary_database_name =
'pubs%'
I get some information regarding [copy_delta] and [load_delta]
I'm pretty sure copy_delta are there number of files copied over from the
source server. I don't know what the load_delta means though. Sometimes it
shows a low number then sometimes it shows a high number. I intially
thought it was the number of transaction logs that got loaded into the
standby server but when that number hits 69 and it only copied 3, it doesn't
make sense. There is also no documenation on BOL or microsoft's web site on
this.
Regards,
Tim
Hi Tim,
Based on my research, load_delta indicates the the difference in minutes
between the last updated date of the last backup file and the last updated
date of the last loaded file. In ths code of the sp_log_shipping_in_sync
stored procedure, which is called in sp_get_log_shipping_monitor_info, you
may see the following codes.
SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
Also, the @.last_updated is @.restoredt, which is got from the following
codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_backup_filename, @.backupdt OUTPUT
IF (@.rv <> 0)
SElECT @.backupdt = @.last_backup_last_updated
the@.compare_with is @.backupdt, which is got form the followig codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_loaded_filename, @.restoredt OUTPUT
IF (@.rv <> 0)
SElECT @.restoredt = @.last_loaded_last_updated
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks,
this is exactly what I am looking for.
Regards,
Tim
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PIofhxLNEHA.928@.cpmsftngxa10.phx.gbl...
> Hi Tim,
> Based on my research, load_delta indicates the the difference in minutes
> between the last updated date of the last backup file and the last
updated
> date of the last loaded file. In ths code of the sp_log_shipping_in_sync
> stored procedure, which is called in sp_get_log_shipping_monitor_info, you
> may see the following codes.
> SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
> Also, the @.last_updated is @.restoredt, which is got from the following
> codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_backup_filename, @.backupdt OUTPUT
> IF (@.rv <> 0)
> SElECT @.backupdt = @.last_backup_last_updated
> the@.compare_with is @.backupdt, which is got form the followig codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_loaded_filename, @.restoredt OUTPUT
> IF (@.rv <> 0)
> SElECT @.restoredt = @.last_loaded_last_updated
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>
Log Shipping Monitoring
When I execute the following SP:
EXEC msdb..sp_get_log_shipping_monitor_info @.secondary_database_name = 'pubs%'
I get some information regarding [copy_delta] and [load_delta]
I'm pretty sure copy_delta are there number of files copied over from the
source server. I don't know what the load_delta means though. Sometimes it
shows a low number then sometimes it shows a high number. I intially
thought it was the number of transaction logs that got loaded into the
standby server but when that number hits 69 and it only copied 3, it doesn't
make sense. There is also no documenation on BOL or microsoft's web site on
this.
Regards,
TimHi Tim,
Based on my research, load_delta indicates the the difference in minutes
between the last updated date of the last backup file and the last updated
date of the last loaded file. In ths code of the sp_log_shipping_in_sync
stored procedure, which is called in sp_get_log_shipping_monitor_info, you
may see the following codes.
SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
Also, the @.last_updated is @.restoredt, which is got from the following
codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_backup_filename, @.backupdt OUTPUT
IF (@.rv <> 0)
SElECT @.backupdt = @.last_backup_last_updated
the@.compare_with is @.backupdt, which is got form the followig codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_loaded_filename, @.restoredt OUTPUT
IF (@.rv <> 0)
SElECT @.restoredt = @.last_loaded_last_updated
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Thanks,
this is exactly what I am looking for.
Regards,
Tim
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PIofhxLNEHA.928@.cpmsftngxa10.phx.gbl...
> Hi Tim,
> Based on my research, load_delta indicates the the difference in minutes
> between the last updated date of the last backup file and the last
updated
> date of the last loaded file. In ths code of the sp_log_shipping_in_sync
> stored procedure, which is called in sp_get_log_shipping_monitor_info, you
> may see the following codes.
> SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
> Also, the @.last_updated is @.restoredt, which is got from the following
> codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_backup_filename, @.backupdt OUTPUT
> IF (@.rv <> 0)
> SElECT @.backupdt = @.last_backup_last_updated
> the@.compare_with is @.backupdt, which is got form the followig codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_loaded_filename, @.restoredt OUTPUT
> IF (@.rv <> 0)
> SElECT @.restoredt = @.last_loaded_last_updated
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>
EXEC msdb..sp_get_log_shipping_monitor_info @.secondary_database_name = 'pubs%'
I get some information regarding [copy_delta] and [load_delta]
I'm pretty sure copy_delta are there number of files copied over from the
source server. I don't know what the load_delta means though. Sometimes it
shows a low number then sometimes it shows a high number. I intially
thought it was the number of transaction logs that got loaded into the
standby server but when that number hits 69 and it only copied 3, it doesn't
make sense. There is also no documenation on BOL or microsoft's web site on
this.
Regards,
TimHi Tim,
Based on my research, load_delta indicates the the difference in minutes
between the last updated date of the last backup file and the last updated
date of the last loaded file. In ths code of the sp_log_shipping_in_sync
stored procedure, which is called in sp_get_log_shipping_monitor_info, you
may see the following codes.
SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
Also, the @.last_updated is @.restoredt, which is got from the following
codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_backup_filename, @.backupdt OUTPUT
IF (@.rv <> 0)
SElECT @.backupdt = @.last_backup_last_updated
the@.compare_with is @.backupdt, which is got form the followig codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_loaded_filename, @.restoredt OUTPUT
IF (@.rv <> 0)
SElECT @.restoredt = @.last_loaded_last_updated
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Thanks,
this is exactly what I am looking for.
Regards,
Tim
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PIofhxLNEHA.928@.cpmsftngxa10.phx.gbl...
> Hi Tim,
> Based on my research, load_delta indicates the the difference in minutes
> between the last updated date of the last backup file and the last
updated
> date of the last loaded file. In ths code of the sp_log_shipping_in_sync
> stored procedure, which is called in sp_get_log_shipping_monitor_info, you
> may see the following codes.
> SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
> Also, the @.last_updated is @.restoredt, which is got from the following
> codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_backup_filename, @.backupdt OUTPUT
> IF (@.rv <> 0)
> SElECT @.backupdt = @.last_backup_last_updated
> the@.compare_with is @.backupdt, which is got form the followig codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_loaded_filename, @.restoredt OUTPUT
> IF (@.rv <> 0)
> SElECT @.restoredt = @.last_loaded_last_updated
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>
Monday, March 19, 2012
log shipping load failure
Hi guys,
In my lodg shipping setup i selected the option terminate
users in database. but if the database is open the restore
is failing with following error.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
[Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
access could not be obtained because the database is in
use.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating abnormally.
is it normal?
as fars as i know with the above option selected it should
terminate the users and restore succesfully.
thanks
Biju
Why do you have connections open to the read-only DB?
What connections are open when this happens?
"biju george" wrote:
> Hi guys,
> In my lodg shipping setup i selected the option terminate
> users in database. but if the database is open the restore
> is failing with following error.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
> access could not be obtained because the database is in
> use.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
> is terminating abnormally.
> is it normal?
> as fars as i know with the above option selected it should
> terminate the users and restore succesfully.
> thanks
> Biju
>
|||yes i have opened sql query analyser
[vbcol=seagreen]
>--Original Message--
>Why do you have connections open to the read-only DB?
>What connections are open when this happens?
>
>"biju george" wrote:
terminate[vbcol=seagreen]
restore[vbcol=seagreen]
Exclusive[vbcol=seagreen]
LOG[vbcol=seagreen]
should
>.
>
In my lodg shipping setup i selected the option terminate
users in database. but if the database is open the restore
is failing with following error.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
[Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
access could not be obtained because the database is in
use.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating abnormally.
is it normal?
as fars as i know with the above option selected it should
terminate the users and restore succesfully.
thanks
Biju
Why do you have connections open to the read-only DB?
What connections are open when this happens?
"biju george" wrote:
> Hi guys,
> In my lodg shipping setup i selected the option terminate
> users in database. but if the database is open the restore
> is failing with following error.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
> access could not be obtained because the database is in
> use.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
> is terminating abnormally.
> is it normal?
> as fars as i know with the above option selected it should
> terminate the users and restore succesfully.
> thanks
> Biju
>
|||yes i have opened sql query analyser
[vbcol=seagreen]
>--Original Message--
>Why do you have connections open to the read-only DB?
>What connections are open when this happens?
>
>"biju george" wrote:
terminate[vbcol=seagreen]
restore[vbcol=seagreen]
Exclusive[vbcol=seagreen]
LOG[vbcol=seagreen]
should
>.
>
log shipping load failure
Hi guys,
In my lodg shipping setup i selected the option terminate
users in database. but if the database is open the restore
is failing with following error.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
[Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
access could not be obtained because the database is in
use.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating abnormally.
is it normal?
as fars as i know with the above option selected it should
terminate the users and restore succesfully.
thanks
Biju
..
Biju,
no, this is not normal. Can you double check that the option was enabled by
editing the maintenance plan. If it definitely is, then have a look at the
current activity window (locked objects, TSQL etc) on the standby server to
see which process is locking the database and what exactly it is doing. This
should give some ideas as to what the issue is.
Regards,
Paul Ibison
|||Hi paul,
yes i checked the option it is enabled.
>--Original Message--
>Biju,
>no, this is not normal. Can you double check that the
option was enabled by
>editing the maintenance plan. If it definitely is, then
have a look at the
>current activity window (locked objects, TSQL etc) on the
standby server to
>see which process is locking the database and what
exactly it is doing. This
>should give some ideas as to what the issue is.
>Regards,
>Paul Ibison
>
>.
>
|||Biju,
OK - have a look at the processes locking the database in the current
activity window (or sp_who, sp_who2, sp_lock etc).
If necessary do a trace.
Regards,
Paul Ibison
In my lodg shipping setup i selected the option terminate
users in database. but if the database is open the restore
is failing with following error.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
[Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
access could not be obtained because the database is in
use.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating abnormally.
is it normal?
as fars as i know with the above option selected it should
terminate the users and restore succesfully.
thanks
Biju
..
Biju,
no, this is not normal. Can you double check that the option was enabled by
editing the maintenance plan. If it definitely is, then have a look at the
current activity window (locked objects, TSQL etc) on the standby server to
see which process is locking the database and what exactly it is doing. This
should give some ideas as to what the issue is.
Regards,
Paul Ibison
|||Hi paul,
yes i checked the option it is enabled.
>--Original Message--
>Biju,
>no, this is not normal. Can you double check that the
option was enabled by
>editing the maintenance plan. If it definitely is, then
have a look at the
>current activity window (locked objects, TSQL etc) on the
standby server to
>see which process is locking the database and what
exactly it is doing. This
>should give some ideas as to what the issue is.
>Regards,
>Paul Ibison
>
>.
>
|||Biju,
OK - have a look at the processes locking the database in the current
activity window (or sp_who, sp_who2, sp_lock etc).
If necessary do a trace.
Regards,
Paul Ibison
Monday, March 12, 2012
Log shipping fails the second time.
Log shipping fails the second time to restore 5Gb transactional log backup with the following error.
Error 823: [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID)
detected during read at offset 0x000001f340e000 in file 'e:\program files\microsoft sql server\DBName.mdf'.
There is no hardware problem. The restore failed in a test server on the same step with the same error message.
The DBCC CHECKDB does not give any error message.
What it might be?
My guess is that the transaction log backup is corrupt and is laying down a full-page format log record (which contains a full page image) that has a corrupt page ID. Is the source database clean as far as CHECKDB is concerned?|||
CHECKDB does not give any error. The transactional backup got corrupted after indexes rebuild operation. It does not happen every time. Is there any way to check transactional backup integrity?
|||yes its possible to check the integrity of a backup file.just refer this command......
Restore verifyonly from disk='Full path of your tran log file'.........it will check whether all the pages in the trn file are readable and also if the backup set is complete........
Log shipping fails the second time.
Log shipping fails the second time to restore 5Gb transactional log backup with the following error.
Error 823: [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID)
detected during read at offset 0x000001f340e000 in file 'e:\program files\microsoft sql server\DBName.mdf'.
There is no hardware problem. The restore failed in a test server on the same step with the same error message.
The DBCC CHECKDB does not give any error message.
What it might be?
My guess is that the transaction log backup is corrupt and is laying down a full-page format log record (which contains a full page image) that has a corrupt page ID. Is the source database clean as far as CHECKDB is concerned?|||
CHECKDB does not give any error. The transactional backup got corrupted after indexes rebuild operation. It does not happen every time. Is there any way to check transactional backup integrity?
|||yes its possible to check the integrity of a backup file.just refer this command......
Restore verifyonly from disk='Full path of your tran log file'.........it will check whether all the pages in the trn file are readable and also if the backup set is complete........
log shipping failover to stand by server
Hi Guys
in logshipping to fail over to stand by server do i have
to do any role change
as far as i know i have to run following script at the
stand by server. am i right?
RESTORE DATABASE database_name WITH RECOVERY
EXEC SP_DBOPTION 'database_name', 'read
only', 'false'
EXEC SP_DBOPTION 'database_name', 'dbo use
only', 'false'
pls advice me
Thanks
Biju
Biju,
have a look at 'log shipping, role changes' in BOL. You don't need to run
your script manually, but run
sp_change_primary_role
sp_change_secondary_role
sp_change_monitor_role
Usually the logins have already been transferred so there's nothing else to
do. These sprocs are useful because they'll try to get the last log (the
live one) if at all possible.
HTH,
Paul Ibison
|||BUT I DONT want to change roles.
>--Original Message--
>Biju,
>have a look at 'log shipping, role changes' in BOL. You
don't need to run
>your script manually, but run
>sp_change_primary_role
>sp_change_secondary_role
>sp_change_monitor_role
>Usually the logins have already been transferred so
there's nothing else to
>do. These sprocs are useful because they'll try to get
the last log (the
>live one) if at all possible.
>HTH,
>Paul Ibison
>
>.
>
|||Biju,
the name is perhaps slightly unintuitive. sp_change_secondary_role:
(a) Copies the final production database transaction log backup to the
standby server along with any additional transaction log backups that were
not previously copied.
(b) Disables the log-shipping transaction copy job on the standby server.
(c) Restores all transaction log backups not previously restored to the
standby database and initiates the recovery of the standby database.
(d) Terminates and rolls back all pending transactions.
(e) Sets the access level of the standby database after completion of the
system stored procedure to multiuser mode.
(f) Creates a log-shipping database maintenance plan on the new primary
server for the new production database. The SQL Server Agent job defined in
this plan backs up the transaction log of the new production database to the
folder location you specified when you set up log shipping.
HTH,
Paul Ibison
in logshipping to fail over to stand by server do i have
to do any role change
as far as i know i have to run following script at the
stand by server. am i right?
RESTORE DATABASE database_name WITH RECOVERY
EXEC SP_DBOPTION 'database_name', 'read
only', 'false'
EXEC SP_DBOPTION 'database_name', 'dbo use
only', 'false'
pls advice me
Thanks
Biju
Biju,
have a look at 'log shipping, role changes' in BOL. You don't need to run
your script manually, but run
sp_change_primary_role
sp_change_secondary_role
sp_change_monitor_role
Usually the logins have already been transferred so there's nothing else to
do. These sprocs are useful because they'll try to get the last log (the
live one) if at all possible.
HTH,
Paul Ibison
|||BUT I DONT want to change roles.
>--Original Message--
>Biju,
>have a look at 'log shipping, role changes' in BOL. You
don't need to run
>your script manually, but run
>sp_change_primary_role
>sp_change_secondary_role
>sp_change_monitor_role
>Usually the logins have already been transferred so
there's nothing else to
>do. These sprocs are useful because they'll try to get
the last log (the
>live one) if at all possible.
>HTH,
>Paul Ibison
>
>.
>
|||Biju,
the name is perhaps slightly unintuitive. sp_change_secondary_role:
(a) Copies the final production database transaction log backup to the
standby server along with any additional transaction log backups that were
not previously copied.
(b) Disables the log-shipping transaction copy job on the standby server.
(c) Restores all transaction log backups not previously restored to the
standby database and initiates the recovery of the standby database.
(d) Terminates and rolls back all pending transactions.
(e) Sets the access level of the standby database after completion of the
system stored procedure to multiuser mode.
(f) Creates a log-shipping database maintenance plan on the new primary
server for the new production database. The SQL Server Agent job defined in
this plan backs up the transaction log of the new production database to the
folder location you specified when you set up log shipping.
HTH,
Paul Ibison
Friday, March 9, 2012
Log Shipping Error on SQL 2000 SP4
I'm attempting to configure log shipping on 2 servers with SQL Server 2000 sp4 Enterprise Edition. I keep getting the following error when the job attemtps to execute.
Error 14261: The specified primary_server_name.primary_database_name('C')
already exists.
I have tried this KB http://support.microsoft.com/kb/298743 and i got the same error again!
Please HELP!any hints ? :(|||Just a wild guess... Are you logshipping to the same instance or between to SQL instances? If the latter is the case, have you ran the MS solution on both instances? (just to be sure)
Error 14261: The specified primary_server_name.primary_database_name('C')
already exists.
I have tried this KB http://support.microsoft.com/kb/298743 and i got the same error again!
Please HELP!any hints ? :(|||Just a wild guess... Are you logshipping to the same instance or between to SQL instances? If the latter is the case, have you ran the MS solution on both instances? (just to be sure)
Log shipping error
I m getting following error in copy/restore operation
"The process cannot access the file because it is being used by another
process."
This come against the file first_file_000000000000.trn every time copy
restore is done. Only first time it went successful. Error number is 32.
Please tell me how to avoid thisVSS
You could be getting this messaqge because it is trying to restore the log
before the copy is finished. How often do you backup and copy the transaction
log?
There is a setting for load delay. The default is 0, you could try setting
that to wait longer for the copy to finish.
Hope this helps
John
"VSS" wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
>|||VSS wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
Isn't it obvious what you need to do? The error message tells you that
some other process is using the file that you're trying to copy/restore.
Not a SQL Server problem. You need to figure out what is using that
file. Take a look at http://www.sysinternals.com for some utilities
that will help you figure that out.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
"The process cannot access the file because it is being used by another
process."
This come against the file first_file_000000000000.trn every time copy
restore is done. Only first time it went successful. Error number is 32.
Please tell me how to avoid thisVSS
You could be getting this messaqge because it is trying to restore the log
before the copy is finished. How often do you backup and copy the transaction
log?
There is a setting for load delay. The default is 0, you could try setting
that to wait longer for the copy to finish.
Hope this helps
John
"VSS" wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
>|||VSS wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
Isn't it obvious what you need to do? The error message tells you that
some other process is using the file that you're trying to copy/restore.
Not a SQL Server problem. You need to figure out what is using that
file. Take a look at http://www.sysinternals.com for some utilities
that will help you figure that out.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Log shipping error
Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
local user on both machines same username and password.
The user has the following on both servers.
act as operating system
logon as a batch job
logon as a service
When I run through the Database Maintenance Plan Wizard, at the last
screen when doing the steps I get the error.
Unable to copy the initialization file to the secondary server.
I have searched endlessly for the reason but have been unsuccessful.
Can anyone shed some light on what I could be missing.
Thanks.
I think, your local accoutn not geeting acces the seconary mechines
folder. create a Mapped drive to the secondary server and try to copy
the backup.
pisquem@.gmail.com wrote:
> Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
> local user on both machines same username and password.
> The user has the following on both servers.
> act as operating system
> logon as a batch job
> logon as a service
> When I run through the Database Maintenance Plan Wizard, at the last
> screen when doing the steps I get the error.
> Unable to copy the initialization file to the secondary server.
> I have searched endlessly for the reason but have been unsuccessful.
> Can anyone shed some light on what I could be missing.
> Thanks.
|||I tried as you described and I was able to map a drive, connect to it
and copy the file over.
Any other ideas?
local user on both machines same username and password.
The user has the following on both servers.
act as operating system
logon as a batch job
logon as a service
When I run through the Database Maintenance Plan Wizard, at the last
screen when doing the steps I get the error.
Unable to copy the initialization file to the secondary server.
I have searched endlessly for the reason but have been unsuccessful.
Can anyone shed some light on what I could be missing.
Thanks.
I think, your local accoutn not geeting acces the seconary mechines
folder. create a Mapped drive to the secondary server and try to copy
the backup.
pisquem@.gmail.com wrote:
> Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
> local user on both machines same username and password.
> The user has the following on both servers.
> act as operating system
> logon as a batch job
> logon as a service
> When I run through the Database Maintenance Plan Wizard, at the last
> screen when doing the steps I get the error.
> Unable to copy the initialization file to the secondary server.
> I have searched endlessly for the reason but have been unsuccessful.
> Can anyone shed some light on what I could be missing.
> Thanks.
|||I tried as you described and I was able to map a drive, connect to it
and copy the file over.
Any other ideas?
Log shipping error
Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
local user on both machines same username and password.
The user has the following on both servers.
act as operating system
logon as a batch job
logon as a service
When I run through the Database Maintenance Plan Wizard, at the last
screen when doing the steps I get the error.
Unable to copy the initialization file to the secondary server.
I have searched endlessly for the reason but have been unsuccessful.
Can anyone shed some light on what I could be missing.
Thanks.I think, your local accoutn not geeting acces the seconary mechines
folder. create a Mapped drive to the secondary server and try to copy
the backup.
pisquem@.gmail.com wrote:
> Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
> local user on both machines same username and password.
> The user has the following on both servers.
> act as operating system
> logon as a batch job
> logon as a service
> When I run through the Database Maintenance Plan Wizard, at the last
> screen when doing the steps I get the error.
> Unable to copy the initialization file to the secondary server.
> I have searched endlessly for the reason but have been unsuccessful.
> Can anyone shed some light on what I could be missing.
> Thanks.|||I tried as you described and I was able to map a drive, connect to it
and copy the file over.
Any other ideas?
local user on both machines same username and password.
The user has the following on both servers.
act as operating system
logon as a batch job
logon as a service
When I run through the Database Maintenance Plan Wizard, at the last
screen when doing the steps I get the error.
Unable to copy the initialization file to the secondary server.
I have searched endlessly for the reason but have been unsuccessful.
Can anyone shed some light on what I could be missing.
Thanks.I think, your local accoutn not geeting acces the seconary mechines
folder. create a Mapped drive to the secondary server and try to copy
the backup.
pisquem@.gmail.com wrote:
> Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
> local user on both machines same username and password.
> The user has the following on both servers.
> act as operating system
> logon as a batch job
> logon as a service
> When I run through the Database Maintenance Plan Wizard, at the last
> screen when doing the steps I get the error.
> Unable to copy the initialization file to the secondary server.
> I have searched endlessly for the reason but have been unsuccessful.
> Can anyone shed some light on what I could be missing.
> Thanks.|||I tried as you described and I was able to map a drive, connect to it
and copy the file over.
Any other ideas?
Log shipping error
I m getting following error in copy/restore operation
"The process cannot access the file because it is being used by another
process."
This come against the file first_file_000000000000.trn every time copy
restore is done. Only first time it went successful. Error number is 32.
Please tell me how to avoid thisVSS
You could be getting this messaqge because it is trying to restore the log
before the copy is finished. How often do you backup and copy the transactio
n
log?
There is a setting for load delay. The default is 0, you could try setting
that to wait longer for the copy to finish.
Hope this helps
John
"VSS" wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
>|||VSS wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
Isn't it obvious what you need to do? The error message tells you that
some other process is using the file that you're trying to copy/restore.
Not a SQL Server problem. You need to figure out what is using that
file. Take a look at http://www.sysinternals.com for some utilities
that will help you figure that out.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
"The process cannot access the file because it is being used by another
process."
This come against the file first_file_000000000000.trn every time copy
restore is done. Only first time it went successful. Error number is 32.
Please tell me how to avoid thisVSS
You could be getting this messaqge because it is trying to restore the log
before the copy is finished. How often do you backup and copy the transactio
n
log?
There is a setting for load delay. The default is 0, you could try setting
that to wait longer for the copy to finish.
Hope this helps
John
"VSS" wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
>|||VSS wrote:
> I m getting following error in copy/restore operation
> "The process cannot access the file because it is being used by another
> process."
> This come against the file first_file_000000000000.trn every time copy
> restore is done. Only first time it went successful. Error number is 32.
> Please tell me how to avoid this
>
Isn't it obvious what you need to do? The error message tells you that
some other process is using the file that you're trying to copy/restore.
Not a SQL Server problem. You need to figure out what is using that
file. Take a look at http://www.sysinternals.com for some utilities
that will help you figure that out.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
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 droptable.com
http://www.droptable.com/Uwe/Forum...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 droptable.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 droptable.com
> http://www.droptable.com/Uwe/Forum...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.droptable.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:[vbcol=seagreen]
>Did you wait long enough for the changs to be sent? You can verify the tra
n
>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.
>
>[quoted text clipped - 16 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...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 droptable.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:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200602/1|||tks for ur clarifications ..
Cheers ..
Michael Hotek wrote:[vbcol=seagreen]
>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 se
t
>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 the
n
>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.
>
>[quoted text clipped - 26 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200602/1
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 droptable.com
http://www.droptable.com/Uwe/Forum...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 droptable.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 droptable.com
> http://www.droptable.com/Uwe/Forum...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.droptable.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:[vbcol=seagreen]
>Did you wait long enough for the changs to be sent? You can verify the tra
n
>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.
>
>[quoted text clipped - 16 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...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 droptable.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:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200602/1|||tks for ur clarifications ..
Cheers ..
Michael Hotek wrote:[vbcol=seagreen]
>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 se
t
>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 the
n
>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.
>
>[quoted text clipped - 26 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200602/1
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 droptable.com
http://www.droptable.com/Uwe/Forums...erver/200601/1
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.
|||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 droptable.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 droptable.com
> http://www.droptable.com/Uwe/Forums...erver/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.droptable.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:[vbcol=seagreen]
>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.
>[quoted text clipped - 16 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/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 droptable.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:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200602/1
|||tks for ur clarifications ..
Cheers ..
Michael Hotek wrote:[vbcol=seagreen]
>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.
>[quoted text clipped - 26 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200602/1
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 droptable.com
http://www.droptable.com/Uwe/Forums...erver/200601/1
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.
|||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 droptable.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 droptable.com
> http://www.droptable.com/Uwe/Forums...erver/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.droptable.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:[vbcol=seagreen]
>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.
>[quoted text clipped - 16 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/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 droptable.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:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200602/1
|||tks for ur clarifications ..
Cheers ..
Michael Hotek wrote:[vbcol=seagreen]
>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.
>[quoted text clipped - 26 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200602/1
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
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
Subscribe to:
Posts (Atom)