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
>
Showing posts with label reports. Show all posts
Showing posts with label reports. Show all posts
Wednesday, March 28, 2012
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
>
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
>
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
>
Friday, March 9, 2012
Log Shipping Copy Job reports successful, but copies nothing
I have set up log shipping between 2 servers but cant get it to
function correctly.
Everything seems to be fine, the backup job happens, dumping the
transaction log to the network share on the primary server(also the
monitoring server).
The copy job runs and completes in 1 second or less, but doesn't seem
to move anything even though it reports success.
If I look at the copy/restore history in the log shipping monitor, it
continuously says that the copy succeeded, but no files were moved and
the last file moved is first_file_00000000.trn
I have checked the settings for the shares, and they are both fine.
I am able to log into the secondary server using the Sql Agent account
and map to the network share on the primary server where the log files
are being created. No problem there.
If I manually move the files the restore job works fine.
The log_shipping_secondary table is getting updated by the restore job
too, and I am using sql authentication with the
log_shipping_monitor_probe account set to sysadmin and db_ownber in
msdb.
It seems to be just the copy jobs never seeming to find any files even
when they are there.
I am starting to go crazy! HELP!
-Gregory
Gregory,
usually when I troubleshoot this issue it is a problem with the setup of
directories and shares, which can be confusing in the wizard. Please can you
remove the existing maintenance plan and set up the directories/shares below
then recreate the plan.
You need a folder eg c:\ProductionLogs that is shared
(\\server\PRODUCTIONLOGS) on the production server.
You need a directory on the standby server c:\shippedlogs, not shared.
In the maintenance plan, the transaction log backup directory is
c:\ProductionLogs
The network sharename is \\server\PRODUCTIONLOGS
The destination is c:\shippedlogs.
HTH,
Paul Ibison
|||Log shipping gives me no love.
I tried as you suggested, created new network shares, deleted the
maintenance plan and recreated the plan using the info you supplied.
It continues to give me the same problem.
This is in the history for the job:
Executed as user: XXXXXXX\UserID. output
---
---
(null)
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998. The step succeeded..
So informational.
Beautiful huh?
Additional info:
The servers are not on a domain, they are both in a workgroup.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Gregory,
there isn't an easy way for me to debug this, and no offence to you but I'd
like to ensure this is not a setup issue.
Please can you send me screenshots of the options you select when you go
through the wizard?
TIA,
Paul Ibison
function correctly.
Everything seems to be fine, the backup job happens, dumping the
transaction log to the network share on the primary server(also the
monitoring server).
The copy job runs and completes in 1 second or less, but doesn't seem
to move anything even though it reports success.
If I look at the copy/restore history in the log shipping monitor, it
continuously says that the copy succeeded, but no files were moved and
the last file moved is first_file_00000000.trn
I have checked the settings for the shares, and they are both fine.
I am able to log into the secondary server using the Sql Agent account
and map to the network share on the primary server where the log files
are being created. No problem there.
If I manually move the files the restore job works fine.
The log_shipping_secondary table is getting updated by the restore job
too, and I am using sql authentication with the
log_shipping_monitor_probe account set to sysadmin and db_ownber in
msdb.
It seems to be just the copy jobs never seeming to find any files even
when they are there.
I am starting to go crazy! HELP!
-Gregory
Gregory,
usually when I troubleshoot this issue it is a problem with the setup of
directories and shares, which can be confusing in the wizard. Please can you
remove the existing maintenance plan and set up the directories/shares below
then recreate the plan.
You need a folder eg c:\ProductionLogs that is shared
(\\server\PRODUCTIONLOGS) on the production server.
You need a directory on the standby server c:\shippedlogs, not shared.
In the maintenance plan, the transaction log backup directory is
c:\ProductionLogs
The network sharename is \\server\PRODUCTIONLOGS
The destination is c:\shippedlogs.
HTH,
Paul Ibison
|||Log shipping gives me no love.
I tried as you suggested, created new network shares, deleted the
maintenance plan and recreated the plan using the info you supplied.
It continues to give me the same problem.
This is in the history for the job:
Executed as user: XXXXXXX\UserID. output
---
---
(null)
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998. The step succeeded..
So informational.
Beautiful huh?
Additional info:
The servers are not on a domain, they are both in a workgroup.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Gregory,
there isn't an easy way for me to debug this, and no offence to you but I'd
like to ensure this is not a setup issue.
Please can you send me screenshots of the options you select when you go
through the wizard?
TIA,
Paul Ibison
Friday, February 24, 2012
Log shipping and database snapshots
SQL Server 2005
Can a database snapshot be created on a log ship target standby database so
that read-only reports and/or datamarts be ran' I know this is fully
supported when using Database Mirroring but Microsoft isn't supporting this
in production environments yet Didn't know what the limitations were with a
database in standby and snapshots.
Thanks"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
so
> that read-only reports and/or datamarts be ran'
Sort of.
If you use RESTORE with STANDBY (check BOL for exact syntax) you can turn
the DB into a read-only mode.
Then later logs can be applied to it.
However, note that when those logs apply there can't be any users in the
database or else they will fail to be restored.
In addition, while they are being restored, you won't be able to read from
the database.
These limitations may or may not be a problem. A typical scenario is to do
something like from 5:00 PM -9:00 AM apply log files as normal. At 9:00 AM
stop applying log files and allow reports to be run. At 5:00 PM kick all
users from the database and start applying logs again.
> I know this is fully
> supported when using Database Mirroring but Microsoft isn't supporting
this
> in production environments yet Didn't know what the limitations were with
a
> database in standby and snapshots.
> Thanks
>|||A Database Snapshot can be created against a Mirror or against a source
database. It can NOT be created against a database that is the target for
Log Shipping. The database has to either be online and accessible or in a
mirroring role to have a Database Snapshot created against it.
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.
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
> so that read-only reports and/or datamarts be ran' I know this is
> fully supported when using Database Mirroring but Microsoft isn't
> supporting this in production environments yet Didn't know what the
> limitations were with a database in standby and snapshots.
> Thanks
>
Can a database snapshot be created on a log ship target standby database so
that read-only reports and/or datamarts be ran' I know this is fully
supported when using Database Mirroring but Microsoft isn't supporting this
in production environments yet Didn't know what the limitations were with a
database in standby and snapshots.
Thanks"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
so
> that read-only reports and/or datamarts be ran'
Sort of.
If you use RESTORE with STANDBY (check BOL for exact syntax) you can turn
the DB into a read-only mode.
Then later logs can be applied to it.
However, note that when those logs apply there can't be any users in the
database or else they will fail to be restored.
In addition, while they are being restored, you won't be able to read from
the database.
These limitations may or may not be a problem. A typical scenario is to do
something like from 5:00 PM -9:00 AM apply log files as normal. At 9:00 AM
stop applying log files and allow reports to be run. At 5:00 PM kick all
users from the database and start applying logs again.
> I know this is fully
> supported when using Database Mirroring but Microsoft isn't supporting
this
> in production environments yet Didn't know what the limitations were with
a
> database in standby and snapshots.
> Thanks
>|||A Database Snapshot can be created against a Mirror or against a source
database. It can NOT be created against a database that is the target for
Log Shipping. The database has to either be online and accessible or in a
mirroring role to have a Database Snapshot created against it.
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.
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
> so that read-only reports and/or datamarts be ran' I know this is
> fully supported when using Database Mirroring but Microsoft isn't
> supporting this in production environments yet Didn't know what the
> limitations were with a database in standby and snapshots.
> Thanks
>
Log shipping and database snapshots
SQL Server 2005
Can a database snapshot be created on a log ship target standby database so
that read-only reports and/or datamarts be ran' I know this is fully
supported when using Database Mirroring but Microsoft isn't supporting this
in production environments yet Didn't know what the limitations were with a
database in standby and snapshots.
Thanks"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
so
> that read-only reports and/or datamarts be ran'
Sort of.
If you use RESTORE with STANDBY (check BOL for exact syntax) you can turn
the DB into a read-only mode.
Then later logs can be applied to it.
However, note that when those logs apply there can't be any users in the
database or else they will fail to be restored.
In addition, while they are being restored, you won't be able to read from
the database.
These limitations may or may not be a problem. A typical scenario is to do
something like from 5:00 PM -9:00 AM apply log files as normal. At 9:00 AM
stop applying log files and allow reports to be run. At 5:00 PM kick all
users from the database and start applying logs again.
> I know this is fully
> supported when using Database Mirroring but Microsoft isn't supporting
this
> in production environments yet Didn't know what the limitations were with
a
> database in standby and snapshots.
> Thanks
>|||A Database Snapshot can be created against a Mirror or against a source
database. It can NOT be created against a database that is the target for
Log Shipping. The database has to either be online and accessible or in a
mirroring role to have a Database Snapshot created against it.
--
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.
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
> so that read-only reports and/or datamarts be ran' I know this is
> fully supported when using Database Mirroring but Microsoft isn't
> supporting this in production environments yet Didn't know what the
> limitations were with a database in standby and snapshots.
> Thanks
>
Can a database snapshot be created on a log ship target standby database so
that read-only reports and/or datamarts be ran' I know this is fully
supported when using Database Mirroring but Microsoft isn't supporting this
in production environments yet Didn't know what the limitations were with a
database in standby and snapshots.
Thanks"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
so
> that read-only reports and/or datamarts be ran'
Sort of.
If you use RESTORE with STANDBY (check BOL for exact syntax) you can turn
the DB into a read-only mode.
Then later logs can be applied to it.
However, note that when those logs apply there can't be any users in the
database or else they will fail to be restored.
In addition, while they are being restored, you won't be able to read from
the database.
These limitations may or may not be a problem. A typical scenario is to do
something like from 5:00 PM -9:00 AM apply log files as normal. At 9:00 AM
stop applying log files and allow reports to be run. At 5:00 PM kick all
users from the database and start applying logs again.
> I know this is fully
> supported when using Database Mirroring but Microsoft isn't supporting
this
> in production environments yet Didn't know what the limitations were with
a
> database in standby and snapshots.
> Thanks
>|||A Database Snapshot can be created against a Mirror or against a source
database. It can NOT be created against a database that is the target for
Log Shipping. The database has to either be online and accessible or in a
mirroring role to have a Database Snapshot created against it.
--
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.
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
> so that read-only reports and/or datamarts be ran' I know this is
> fully supported when using Database Mirroring but Microsoft isn't
> supporting this in production environments yet Didn't know what the
> limitations were with a database in standby and snapshots.
> Thanks
>
Subscribe to:
Posts (Atom)