Can't find log-shipping option

In the text on the link (part 2 - below) - I cannot find the "Transaction
Log Shipping" option Is this an SP4 option only for SQL Server 2000?
http://msdn2.microsoft.com/en-gb/library/ms189071.aspx
Right-click the database you want to use as your primary database in the log
shipping configuration, and then click Properties.
Under Select a page, click Transaction Log Shipping.
Clear the Enable this as a primary database in a log shipping configuration
check box.
Regards,
Jamie
I may be asking the wrong question - Is there a wizard that assists in the
creation of log shipping or is it done strictly with a DTS package?
Regards,
Jamie
"thejamie" wrote:

> In the text on the link (part 2 - below) - I cannot find the "Transaction
> Log Shipping" option Is this an SP4 option only for SQL Server 2000?
> http://msdn2.microsoft.com/en-gb/library/ms189071.aspx
> ----
> Right-click the database you want to use as your primary database in the log
> shipping configuration, and then click Properties.
> Under Select a page, click Transaction Log Shipping.
> Clear the Enable this as a primary database in a log shipping configuration
> check box.
> --
> Regards,
> Jamie
|||Jamie,
the original MSDN2 link you supplied applies to SQL Server 2005, but as you
are tlaking about DTS you must be using SQL Server 2000. In your edition of
sql server, you'll set this up using a maintenance plan. In the first screen
there's a checkbox at the bottom for log shipping.
Rgds,
Paul Ibison
|||Actually, it looks from the description you are giving me that the SQL Server
2000 Standard edition does not support log shipping. We are running both
but are not currently in a position to migrate to 2005.
Regards,
Jamie
"Paul Ibison" wrote:

> Jamie,
> the original MSDN2 link you supplied applies to SQL Server 2005, but as you
> are tlaking about DTS you must be using SQL Server 2000. In your edition of
> sql server, you'll set this up using a maintenance plan. In the first screen
> there's a checkbox at the bottom for log shipping.
> Rgds,
> Paul Ibison
>
>
|||Paul,
I can see from looking at various articles on the web that log shipping is
possible without the enterprise version. Are there sample scripts available
for this (SQL Server 2000)?
Regards,
Jamie
"Paul Ibison" wrote:

> Jamie,
> the original MSDN2 link you supplied applies to SQL Server 2005, but as you
> are tlaking about DTS you must be using SQL Server 2000. In your edition of
> sql server, you'll set this up using a maintenance plan. In the first screen
> there's a checkbox at the bottom for log shipping.
> Rgds,
> Paul Ibison
>
>
|||Jamie - these scripts are in the Backoffice Resource Kit, and are also on
some sites (eg
http://www.sql-server-performance.com/sql_server_log_shipping.asp).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I also see that we have not turned on our backup logs option. Is there an
impact on the server if I turn it on?
Regards,
Jamie
"Paul Ibison" wrote:

> Jamie - these scripts are in the Backoffice Resource Kit, and are also on
> some sites (eg
> http://www.sql-server-performance.com/sql_server_log_shipping.asp).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||This is pretty much standard on a production server. If you only have simple
recovery mode, the DR plan will rely on complete backups only and will
therefore expose you to a large potential data loss. Much better to use FULL
and regular log backups. There will be an impact on the production server as
the log backup will need to access the disk, but this is unavoidable to have
a decent DR plan, and if the backups begin to take too long on the disk, you
can use LiteSpeed
(http://www.quest.com/litespeed_for_sql_server/overview.aspx) or equivalent.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
After turning on the option to save the transaction logs, in six short
hours, there was an accumulation of over 10gig of data. I suspect that given
the absense of a wizard, my better choice is the litespeed or a similar tool.
Is there a reason you chose litespeed - there are a couple of other products
reviewed in this month's sql mag... I suspect that I have more to manage
than I can handle at this point.
Regards,
Jamie
"Paul Ibison" wrote:

> This is pretty much standard on a production server. If you only have simple
> recovery mode, the DR plan will rely on complete backups only and will
> therefore expose you to a large potential data loss. Much better to use FULL
> and regular log backups. There will be an impact on the production server as
> the log backup will need to access the disk, but this is unavoidable to have
> a decent DR plan, and if the backups begin to take too long on the disk, you
> can use LiteSpeed
> (http://www.quest.com/litespeed_for_sql_server/overview.aspx) or equivalent.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
>
|||Jamie,
I looked at a couple and simply went for the market leader on the assumption
that they were less likely to go bust
If you start using this type of tool, the log-shipping will have to be
hand-crafted as SQL Server won't recognise the backup files. This sounds
like a pain, but in reality log shipping is very simple technology and can
easily be created via a series of your own jobs. Using SQLLiteSpeed in this
way is supported as it has extended stored procedures to do the backup and
the restore.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .