Log Shipping Monitor - 2005

Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
Chris
Hi Chris
"Cgal" wrote:

> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not find
> the nice Log Shipping monitor that give you status on log shipping. I also
> searched through the Books Online documentation and several online resources
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) to
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john
|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john
|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database, and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Log Shipping Monitor - 2005

Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
ChrisHi Chris
"Cgal" wrote:

> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not fi
nd
> the nice Log Shipping monitor that give you status on log shipping. I als
o
> searched through the Books Online documentation and several online resourc
es
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) t
o
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database,
and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============

log shipping encryption

I have a few questions that are bugging me, being a newbie to SQL 2000
Enterprise. I want to set up a warm site server for disaster recovery of my
production server at a remote location. Both Sql servers will be behind
firewalls, (if that matters) and the remote site will not be a production
server; only receiving the shipped transaction logs and being updated
accordingly. For budgetary reasons, they are Internet attached via T1.
1. Is this setup possible?
2. If so, will SQL2000 allow me to encrypt the data it is shipping?
3. Why can't the Chiefs find a defense that will hold the other team to
less than 35 points so I can get rid of my ulcer?
Hoping for all three answers, but hey...2 out of 3 is still a good average.
Thanks in advance.
Hi
The setup is possible.
SQL does not support encryption at transport level, that function belongs to
the OS or network stack. You could connect the 2 servers via Windows VPN.
Setup the dial-up VPN, originating from the local server, to use the network
cards, with no-hangup, and auto-retry.
The VPN then can run compression (big benefit as most log files can be
compressed by up to 70%) and encryption.
Windows VPN is very efficent and is great for security needs like yours.
Regards
Mike
"Rod Hurley" wrote:

> I have a few questions that are bugging me, being a newbie to SQL 2000
> Enterprise. I want to set up a warm site server for disaster recovery of my
> production server at a remote location. Both Sql servers will be behind
> firewalls, (if that matters) and the remote site will not be a production
> server; only receiving the shipped transaction logs and being updated
> accordingly. For budgetary reasons, they are Internet attached via T1.
> 1. Is this setup possible?
> 2. If so, will SQL2000 allow me to encrypt the data it is shipping?
> 3. Why can't the Chiefs find a defense that will hold the other team to
> less than 35 points so I can get rid of my ulcer?
> Hoping for all three answers, but hey...2 out of 3 is still a good average.
> Thanks in advance.

Log Shipping between SQL Server versions

Is it possible to perform log shipping between a server running SQL 2000
Enterprise and another server running SQL 2005 Enterprise?
What would be the purpose of the secondary database?
Since you can restore SQL Server 2000 databases into SQL Server 2005
technically you can do log shipping to SQL Server 2005. But the opposite is
not possible because you can not restore SQL Server 2005 databases into SQL
Server 2000.
So, if you lose your SQL Server 2000 database and you only have the 2005
database. Do you plan to continue with 2005 only?
Ben Nevarez
Senior Database Administrator
"KnightFall1" wrote:

> Is it possible to perform log shipping between a server running SQL 2000
> Enterprise and another server running SQL 2005 Enterprise?
|||Hi Ben,
The original question relates to a work situation where we have a SQL 2000
Enterprise production database that needs to be replicated (for reporting
purposes) to an environment that has SQL 2005 running.
So I was curious if we could perform log shipping between the 2 servers to
replicate the database (assuming this is supported between these 2 versions
of SQL Server). This also brings up the question about whether transactional
replication is permitted between SQL 2000 and SQL 2005.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> What would be the purpose of the secondary database?
> Since you can restore SQL Server 2000 databases into SQL Server 2005
> technically you can do log shipping to SQL Server 2005. But the opposite is
> not possible because you can not restore SQL Server 2005 databases into SQL
> Server 2000.
> So, if you lose your SQL Server 2000 database and you only have the 2005
> database. Do you plan to continue with 2005 only?
> Ben Nevarez
> Senior Database Administrator
>
> "KnightFall1" wrote:
|||You say that you want to use the Secondary Server (in Log Shipping) for
reporting purposes. Then you should set its recovery state as STANDBY to
query against it. However then your users will be disconnected for the
coming Transaction Log to be applied to your Secondary Server. So your users
would experience disconnections.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...[vbcol=seagreen]
> Hi Ben,
> The original question relates to a work situation where we have a SQL 2000
> Enterprise production database that needs to be replicated (for reporting
> purposes) to an environment that has SQL 2005 running.
> So I was curious if we could perform log shipping between the 2 servers to
> replicate the database (assuming this is supported between these 2
> versions
> of SQL Server). This also brings up the question about whether
> transactional
> replication is permitted between SQL 2000 and SQL 2005.
> "Ben Nevarez" wrote:
|||Hi Ekrem,
The log shipping will be on a set schedule. Currently the business
requirement is once a day (we are still in the process of establishing a
specific time of day) for this process. So even if there is a disconnection,
the users on that end will know when the log shipping is occurring, so there
shouldn't be a problem.
Wouldn't you agree?
"Ekrem ?nsoy" wrote:

> You say that you want to use the Secondary Server (in Log Shipping) for
> reporting purposes. Then you should set its recovery state as STANDBY to
> query against it. However then your users will be disconnected for the
> coming Transaction Log to be applied to your Secondary Server. So your users
> would experience disconnections.
> --
> Ekrem ?nsoy
>
> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
>
|||Then your users would be querying a database which is older between 0-24
hours than the original one.
If this would not make any trouble and if you set up the Restore job (on the
Secondary Server) to start at a time when your users would be asleep then I
don't think there would be any problem with this setup.
P.S.
You know that your users will be able to use only SELECT against your
Secondary Database right? I just wanted to be sure you know about this.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:1F9B7D48-BCC2-4086-8CC5-CE2E01DE9959@.microsoft.com...[vbcol=seagreen]
> Hi Ekrem,
> The log shipping will be on a set schedule. Currently the business
> requirement is once a day (we are still in the process of establishing a
> specific time of day) for this process. So even if there is a
> disconnection,
> the users on that end will know when the log shipping is occurring, so
> there
> shouldn't be a problem.
> Wouldn't you agree?
>
> "Ekrem ?nsoy" wrote:

Log Shipping between SQL Server versions

Is it possible to perform log shipping between a server running SQL 2000
Enterprise and another server running SQL 2005 Enterprise?What would be the purpose of the secondary database?
Since you can restore SQL Server 2000 databases into SQL Server 2005
technically you can do log shipping to SQL Server 2005. But the opposite is
not possible because you can not restore SQL Server 2005 databases into SQL
Server 2000.
So, if you lose your SQL Server 2000 database and you only have the 2005
database. Do you plan to continue with 2005 only?
Ben Nevarez
Senior Database Administrator
"KnightFall1" wrote:

> Is it possible to perform log shipping between a server running SQL 2000
> Enterprise and another server running SQL 2005 Enterprise?|||Hi Ben,
The original question relates to a work situation where we have a SQL 2000
Enterprise production database that needs to be replicated (for reporting
purposes) to an environment that has SQL 2005 running.
So I was curious if we could perform log shipping between the 2 servers to
replicate the database (assuming this is supported between these 2 versions
of SQL Server). This also brings up the question about whether transactional
replication is permitted between SQL 2000 and SQL 2005.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> What would be the purpose of the secondary database?
> Since you can restore SQL Server 2000 databases into SQL Server 2005
> technically you can do log shipping to SQL Server 2005. But the opposite i
s
> not possible because you can not restore SQL Server 2005 databases into SQ
L
> Server 2000.
> So, if you lose your SQL Server 2000 database and you only have the 2005
> database. Do you plan to continue with 2005 only?
> Ben Nevarez
> Senior Database Administrator
>
> "KnightFall1" wrote:
>|||You say that you want to use the Secondary Server (in Log Shipping) for
reporting purposes. Then you should set its recovery state as STANDBY to
query against it. However then your users will be disconnected for the
coming Transaction Log to be applied to your Secondary Server. So your users
would experience disconnections.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...[vbcol=seagreen]
> Hi Ben,
> The original question relates to a work situation where we have a SQL 2000
> Enterprise production database that needs to be replicated (for reporting
> purposes) to an environment that has SQL 2005 running.
> So I was curious if we could perform log shipping between the 2 servers to
> replicate the database (assuming this is supported between these 2
> versions
> of SQL Server). This also brings up the question about whether
> transactional
> replication is permitted between SQL 2000 and SQL 2005.
> "Ben Nevarez" wrote:
>|||Hi Ekrem,
The log shipping will be on a set schedule. Currently the business
requirement is once a day (we are still in the process of establishing a
specific time of day) for this process. So even if there is a disconnection,
the users on that end will know when the log shipping is occurring, so there
shouldn't be a problem.
Wouldn't you agree?
"Ekrem ?nsoy" wrote:

> You say that you want to use the Secondary Server (in Log Shipping) for
> reporting purposes. Then you should set its recovery state as STANDBY to
> query against it. However then your users will be disconnected for the
> coming Transaction Log to be applied to your Secondary Server. So your use
rs
> would experience disconnections.
> --
> Ekrem ?nsoy
>
> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
>|||Then your users would be querying a database which is older between 0-24
hours than the original one.
If this would not make any trouble and if you set up the Restore job (on the
Secondary Server) to start at a time when your users would be asleep then I
don't think there would be any problem with this setup.
P.S.
You know that your users will be able to use only SELECT against your
Secondary Database right? I just wanted to be sure you know about this.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:1F9B7D48-BCC2-4086-8CC5-CE2E01DE9959@.microsoft.com...[vbcol=seagreen]
> Hi Ekrem,
> The log shipping will be on a set schedule. Currently the business
> requirement is once a day (we are still in the process of establishing a
> specific time of day) for this process. So even if there is a
> disconnection,
> the users on that end will know when the log shipping is occurring, so
> there
> shouldn't be a problem.
> Wouldn't you agree?
>
> "Ekrem ?nsoy" wrote:
>