Don't use the GUI

Do your restores with T-SQL statements. Restore the normal log backups, in sequence, with norecovery, then restore the tail log backup. Extension is irrelevant, SQL doesn't care...

That is a .net error. SQL Server is not written in .net, hence it's not a SQL Server error.

It's an application error.

Yes, you can use T-SQL to restore multiple log backups.

Use T-SQL.

RESTORE LOG ....

Tell him that SQL is designed to use all the memory it is allocated and that using 90% of the...

There's another session from somewhere else which is causing this. Identify where that other session is coming from.

Because it's no more eligible to run than any other process. If it...

You can't kill system processes, and from the value of the spid, that's likely a system process.

Why do you want to kill it?

Highly unlikely.

Lynn Pettis (4/7/2014)

yuvipoy (4/7/2014)

inorder to hide my business process i have renamed the column.

while pasting here i did not mention as b.column names for the columns.

For execution plan since it...

Are you aware of the side effects of nolock?

Are your users happy to be getting reports and results which are intermittently incorrect?

You are aware of the side effects of nolock? Your users are happy with intermittent errors in their reports?

mark 95074 (4/5/2014)

System.Data.SqlClient.SqlError: The log in this backup set terminates at LSN 2804703000000039200001, which is too early to apply to the database. A more recent log backup that includes LSN...

yuvipoy, you know full well by this point what we need to answer performance questions.

Table definitions, index definitions and execution plan please. Otherwise there is absolutely nothing anyone can say....

Correct

Then my ancillary table...