Please let me know, if there is a way to create a full backup daily with log backups/ differential backups.

My Primary Server is too far. I am sitting at the DR Site. I cannot transfer fullbackup daily. I need to take full backup and copy to tape.

Regards,
nvn

I have been a frequent visitor of your Site, and must say it is quite informative and helpful !! Hearty Thank You.

I was wondering if you could also let us know something about the “Security”

Regards,
Rukku

can i restore LOG without restore the FULL backup at first, namely i need to restore a full backup first then i need to add new files to make partitioning on 2 tables, after that i need to restore LOG backup. so i need the database to be online but i will not make any transaction on database while it’s online.

it this double?

I tried to restore SQL Server 2000 xxx.bak database on another database. The code is

Use Master
go

Alter Database xxx
SET SINGLE_USER With ROLLBACK IMMEDIATE

RESTORE DATABASE xxx
FROM DISK = N’E:\Backup\xxxxx\xxxxxx.bak’
WITH FILE = 1,
MOVE N’xxx99_Data’
TO N’E:\MSSQLDATA\exercises_edi.mdf’,
MOVE N’xxx99_Log’
TO N’E:\MSSQLLOGS\exercises_edi.ldf’,
NOUNLOAD,
REPLACE,
STATS = 10
GO

The process got disconnected in the middle and still the database appears to be in “restoring mode”. How can I stop that mode and start again from scratch

My sql server database goes to recovery mode on every 2-3 hours. current database size is 3173 MB.

Could you please any one help to resolve this?

Thanks

how to achieve it

The command syntax is
RESTORE DATABASE dbname WITH RECOVERY

where dbname is the name of the database you are recovering.

restore database with recovery

Microsoft suggests this practice to prevent accidental recovery before all logs are restored.

I have current Live server which from now I want to use as Secondary for Log shipping. and then setup a new server as Primary.
But I don’t know how to convert current live to take in NoRecovery Mode without data loss.

I am very confused in this.

Thanks!

yes i understand i cant use standby clause. Currently my db full backup restored using recovery mode so that the users can access the db after restoration. This happens on a weekend. Now we are unable to restore the daily transactional logs as the DB is in the recovery mode. In this scenario we have following questions
1. how can we change the mode of the DB to No recovery?
2. Is there anyother way that we can restore the transaction logs when the DB is in recovery mode?
3. From some of the article i found out that, the transaction logs should be restored with “no Recovery” and the final transaction log should be restored with “Recovery”

You can not use WITH STANDBY clause to restore a SQL Server 2000 database in SQL Server 2005.
You would have to upgrade the source server to 2005.

Regards,
Pinal Dave

We have a Production DB Server (SQL Server 2000) and Reporting DB Server (SQL Server 2005)
Earlier both servers were having SQL 2000. But now they have upgraded Reporting DB Server to SQL 2005.
Backup Process – We have a process which syncs 5 databases between Production and Reporting. Complete restore is taken on a weekly basis (Sunday) and transaction logs are taken on a daily basis.

After upgradation of Reporting server to SQL Server 2005, backup process is not running as expected.
We were able to restore the complete backup successfully which happens weekly. But having some issues while restoring transaction logs.

While trying to restore the database and transaction logs , we have 3 status modes:
Recovery : We can’t use it, as it does not allow to restore transaction logs. If transaction logs are not there, we can use it very well for complete backup.
NoRecovery : It can be used to restore but again database is no useable. It will be in recovery mode.
StandBy : In the old reporting server(SQL 2000), they were using StandBy mode.
It is read-only mode. But we are not able to use it as it says a message “This backup cannot be restored using WITH STANDBY because a database upgrade
is needed. Reissue the RESTORE without WITH STANDBY.”
As backup is from SQL 2000, it can’t be restored on SQL 2005.

We have restored the complete backup which was done using “recovery” mode. If complete backup is done in “recovery” mode, it is not restoring transaction logs.

Could you please help me out in resolving this issue

A database in recovey mode can be made accessible using STANDBY option. This option is usually used in log shipping to make the secondary database available.

Regards,
Pinal Dave

When a transaction log recovery is running on the database with recovery mode, can th database be accessible to other users, for example can we fire a select query to the database? If yes then what is the process to do so? Since, we tried that when we were running the recovery on the DB and we parallely fired a select query, the recovery got aborted.

Please suggest.

Our aim is that when we are restoring the transaction log the database should be accessible to the users.

Thanks in advance!!

Once a database converted in RECOVERY mode, no more transaction log backup can be restored. You can not set a database back to NORECOVERY mode.
So to resotre more transactional log backups keep the database in NORECOERY mode.

Regards,
Pinal Dave

A running database con not be changed to standby mode. Only a data in no-recovery state can be moved to standby mode. This is an option that is specified while restoring a database or transaction log.

Regards,
Pinal Dave