Hi,
I have Production database that needs to copied over to Developement
envirnoment where our developers can debug the issues we have in production.
I decided to go with log shipping and scheduled it to copy log every night to
Developemnt from Production.It worked fine...but the database was on
developement(seondry server)in read-only mode which when I tried to remove
gave me an error "database is in warm standby mode, alter database option
fails"
How do I do that developer would have full access (Not in Read-Only)to that
database on secondry server.
I tried to delete the log shipping (with the fear if the changes made to
seondry appear in primary database) and delete the log shipping from
maitenance plan but still not able to bring the database on secondry out of
read0only mode.
Thanks
ShanRESTORE DATABASE dbname WITH RECOVERY will bring it to "normal" state. But you won't be able to
restore any further transaction log backups after this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Shan" <Shan@.discussions.microsoft.com> wrote in message
news:73B4BCC5-DED7-48C2-95EA-D289EE3E0BB3@.microsoft.com...
> Hi,
> I have Production database that needs to copied over to Developement
> envirnoment where our developers can debug the issues we have in production.
> I decided to go with log shipping and scheduled it to copy log every night to
> Developemnt from Production.It worked fine...but the database was on
> developement(seondry server)in read-only mode which when I tried to remove
> gave me an error "database is in warm standby mode, alter database option
> fails"
> How do I do that developer would have full access (Not in Read-Only)to that
> database on secondry server.
> I tried to delete the log shipping (with the fear if the changes made to
> seondry appear in primary database) and delete the log shipping from
> maitenance plan but still not able to bring the database on secondry out of
> read0only mode.
> Thanks
> Shan|||Thanks for your reply, It worked. Then what kind of approach I should be
adapting when I have to backup database from one server to another server on
regular bases provided that databases on secondry server available to user
for all activities(Not Read-Only). Through the wizard the only two options I
see is "No Recovery" and "Standby".
Thanks
Shan
"Tibor Karaszi" wrote:
> RESTORE DATABASE dbname WITH RECOVERY will bring it to "normal" state. But you won't be able to
> restore any further transaction log backups after this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Shan" <Shan@.discussions.microsoft.com> wrote in message
> news:73B4BCC5-DED7-48C2-95EA-D289EE3E0BB3@.microsoft.com...
> > Hi,
> >
> > I have Production database that needs to copied over to Developement
> > envirnoment where our developers can debug the issues we have in production.
> > I decided to go with log shipping and scheduled it to copy log every night to
> > Developemnt from Production.It worked fine...but the database was on
> > developement(seondry server)in read-only mode which when I tried to remove
> > gave me an error "database is in warm standby mode, alter database option
> > fails"
> >
> > How do I do that developer would have full access (Not in Read-Only)to that
> > database on secondry server.
> >
> > I tried to delete the log shipping (with the fear if the changes made to
> > seondry appear in primary database) and delete the log shipping from
> > maitenance plan but still not able to bring the database on secondry out of
> > read0only mode.
> >
> > Thanks
> >
> > Shan
>
>|||'That is not possible using backup and restore (which is what log shipping is using). How would you
expect to restore a backup based on a prior backup if you have done modifications in the database
since you restored that prior backup? You might want to look at replication instead. I suggest you
read:
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlhalp.mspx
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Shan" <Shan@.discussions.microsoft.com> wrote in message
news:60664FEF-29FD-4F97-AEC9-F3AA4654586B@.microsoft.com...
> Thanks for your reply, It worked. Then what kind of approach I should be
> adapting when I have to backup database from one server to another server on
> regular bases provided that databases on secondry server available to user
> for all activities(Not Read-Only). Through the wizard the only two options I
> see is "No Recovery" and "Standby".
> Thanks
> Shan
> "Tibor Karaszi" wrote:
>> RESTORE DATABASE dbname WITH RECOVERY will bring it to "normal" state. But you won't be able to
>> restore any further transaction log backups after this.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "Shan" <Shan@.discussions.microsoft.com> wrote in message
>> news:73B4BCC5-DED7-48C2-95EA-D289EE3E0BB3@.microsoft.com...
>> > Hi,
>> >
>> > I have Production database that needs to copied over to Developement
>> > envirnoment where our developers can debug the issues we have in production.
>> > I decided to go with log shipping and scheduled it to copy log every night to
>> > Developemnt from Production.It worked fine...but the database was on
>> > developement(seondry server)in read-only mode which when I tried to remove
>> > gave me an error "database is in warm standby mode, alter database option
>> > fails"
>> >
>> > How do I do that developer would have full access (Not in Read-Only)to that
>> > database on secondry server.
>> >
>> > I tried to delete the log shipping (with the fear if the changes made to
>> > seondry appear in primary database) and delete the log shipping from
>> > maitenance plan but still not able to bring the database on secondry out of
>> > read0only mode.
>> >
>> > Thanks
>> >
>> > Shan
>>
Monday, March 26, 2012
how delete Log Shipping?
Labels:
copied,
database,
debug,
delete,
developement,
developers,
envirnoment,
log,
microsoft,
mysql,
oracle,
production,
server,
shipping,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment