Log Shipping support 2005 SP1

Whats new for SQL Server 2005 SP2 states:-

"The sqllogship application is now supported."

Can anybody confirm that log shipping is not supported in SQL Server 2005 SP1?

Thanks
Log shipping has always been available in SQL 2005. I beleive that this command line utility was introduced in SP2.

Log Shipping support 2005 SP1

Whats new for SQL Server 2005 SP2 states:-

"The sqllogship application is now supported."

Can anybody confirm that log shipping is not supported in SQL Server 2005 SP1?

Thanks
Log shipping has always been available in SQL 2005. I beleive that this command line utility was introduced in SP2.sql

Log Shipping Error 4323

Hi all,

Scenario : MS Windows 2003 SP1 - MS SQL Server 2000 EE SP4

Log Shipping

My secondary server was restoring backup logs successfully, but suddenly i got the following error:

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4323: [Microsoft][ODBC SQL Server Driver][SQL Server]The database is marked suspect. Transaction logs cannot be restored. Use RESTORE DATABASE to recover the database.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

How can I fix this situation without re create the maintenance plan ?

We had the same issue some time ago, this was related to a new file being created in a filegroup on the source. Don't know if this applies to your case, but restoring a backup of this new file on the secondary server solved the pb (unless we had to restore the whole db, sorry I can't remember, my memory is gone... together with the customer :o).

HTH,

Vincent

Log Shipping Error 4323

Hi all,

Scenario : MS Windows 2003 SP1 - MS SQL Server 2000 EE SP4

Log Shipping

My secondary server was restoring backup logs successfully, but suddenly i got the following error:

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4323: [Microsoft][ODBC SQL Server Driver][SQL Server]The database is marked suspect. Transaction logs cannot be restored. Use RESTORE DATABASE to recover the database.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

How can I fix this situation without re create the maintenance plan ?

We had the same issue some time ago, this was related to a new file being created in a filegroup on the source. Don't know if this applies to your case, but restoring a backup of this new file on the secondary server solved the pb (unless we had to restore the whole db, sorry I can't remember, my memory is gone... together with the customer :o).

HTH,

Vincent