>> My question is why same size of t-log restore is taking different timings ?

Good question. Taking your best case scenario, 7 GB in 34 minutes, that works...

Amit, I think you should qualify your suggestions by stating that they are only applicable if the transaction log is not critical to the user. You really shouldn't be...

You could use the backup history tables for reference. The example below will list down all database which have not had a full backup taken in the last 24...

That is not possible. Restoring the transaction logs will always put the database in the state it was in at the end of that backup, or if using the...

After you restored from 'F:\MSSQL\BACKUP\my_test_log_02' with the STOPAT option, subsequent trx log restores need to start off from the same file i.e. restore 'F:\MSSQL\BACKUP\my_test_log_02' first without the STOPAT value, then...

>> run back up log, dbcc shrinkfile emptyfile and alter database and it still won't remove the log, shrink it or whatever due to some data in there...

CREATE DATABASE TheForce

GO

USE TheForce

GO

BACKUP DATABASE TheForce TO DISK = 'c:\TheForce_full.bak' WITH FORMAT

CREATE TABLE episodes (col1 int)

DECLARE @starttime DATETIME

SET @starttime = GETDATE()

INSERT INTO episodes VALUES (4)

WAITFOR DELAY '00:00:01'

INSERT INTO episodes VALUES...

If your first STOPAT recovery was used with the STANDBY or NORECOVERY (which doesn't make much sense) options, you can restore subsequent transaction logs. You do need to start...

Being a development box, I can imagine the sort of things that gets thrown at it 🙂

See the following links on how to find out how much of the transaction...

If the reasons Jeff mentioned were the cause of your issue, you can find out when those actions were performed by checking the SQL Server log. Recovery model changes...

Just tried it, it isn't possible to back up a database that's in standby mode using the COPY_ONLY option. Given your situation, looks like you're already doing the only...

Gail's probably won the bet as regards to your database's recovery model. If so, don't do anything else that would overwrite what's already in the active transaction log. ...

I take it that your concern lies with the fact that you can simply open a SQL Server backup...

See this link on log truncation and shrinking.

>> How can the page LSN be greater than log LSN ?since the log LSN for that page should be equal

One possibility may be when you restore individual pages...