Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts

Wednesday, March 28, 2012

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

Wednesday, March 7, 2012

log shipping barfing

sql2k sp2
Log Shipping gets set up successfully. The db gets created
on the secondary box. All the TLog backups get transferred
to the secondary box. But then after some time it gets out
of sync. In the reporting file there is the message:
(snippet)
(SQL Server does not exist or access is denied)
How could this be since it was able to intialize the new
db? If it never did that and I got this message it would
make more sense than creating the db but not baing able to
connect after that.
TIA, ChrisChris,
Which job is failing? Sounds like the restore job on the secondary. Are you
sure SQL Agent on the secondary can connect to the secondary SQL Server?
Ron
--
Ron Talmage
SQL Server MVP
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:05e001c3a4ca$1a848f70$a301280a@.phx.gbl...
> sql2k sp2
> Log Shipping gets set up successfully. The db gets created
> on the secondary box. All the TLog backups get transferred
> to the secondary box. But then after some time it gets out
> of sync. In the reporting file there is the message:
> (snippet)
> (SQL Server does not exist or access is denied)
> How could this be since it was able to intialize the new
> db? If it never did that and I got this message it would
> make more sense than creating the db but not baing able to
> connect after that.
> TIA, Chris
>|||Are you
>sure SQL Agent on the secondary can connect to the
secondary SQL Server?
Not sure Im following on this one.
>--Original Message--
>Chris,
>Which job is failing? Sounds like the restore job on the
secondary. Are you
>sure SQL Agent on the secondary can connect to the
secondary SQL Server?
>Ron
>--
>Ron Talmage
>SQL Server MVP
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message
>news:05e001c3a4ca$1a848f70$a301280a@.phx.gbl...
>> sql2k sp2
>> Log Shipping gets set up successfully. The db gets
created
>> on the secondary box. All the TLog backups get
transferred
>> to the secondary box. But then after some time it gets
out
>> of sync. In the reporting file there is the message:
>> (snippet)
>> (SQL Server does not exist or access is denied)
>> How could this be since it was able to intialize the new
>> db? If it never did that and I got this message it would
>> make more sense than creating the db but not baing able
to
>> connect after that.
>> TIA, Chris
>
>.
>