Are you absolutely sure it's file #2? SQL verifies a file before restoring it.

Check the backup file contents just to be sure:

RESTORE FILELISTONLY

FROM DISK = 'F:\For restore\Lss_backup_2013_10_13_000010_4544977\Lss_backup_2013_10_18_000012_9335308.dif'

Edit: Corrected backup...

T.Ashish (10/17/2013)

Jeff Moden (10/17/2013)

Thank...

Also, you need to review the SQL log from when the error first occurred. Sometimes when errors occur SQL gets stopped and restarted, which causes a log switch. ...

Or just:

ORDER BY 1

I often avoid using the column names at all in UNIONed queries, as the names somehow seem to

change a lot 🙂 :

The CROSS APPLY and SUBSTRING below should do what you need. Let us know if you need some clarification for getting it into an UPDATE statement.

DECLARE @leading_trailing_chars_to_eliminate varchar(10)

SET @leading_trailing_chars_to_eliminate...

You'll need to format the hours separately, as below, since style "114" will only handle up to 23 hours:

SELECT

CAST(DATEDIFF(ms, ActualStartTime, EndTime) / 3600000 AS varchar(3)) +

...

I think the code below is a reasonable interpretation, but whether it's correct or not is far from certain:

ALTER TABLE [Lkup].[ReceiptReasonCodes]

ADD [IsValidSap] [bit] NULL

I should have mentioned that. I was thinking...

You can't directly restrict sa (sysadmin) accounts from any activity in SQL Server. You would have to use a trigger to prevent sa activity.

For only non-sa, you could try:

DENY...

Use LEFT OUTER JOIN, but don't cast datetimes in any data table to dates to do comparisons; instead, use a range check.

Here's a sample join for the tables you've described:

SELECT...

Be aware that a global temp table means the code must be single-threaded, as simultaneous executions of the code would stomp on each other.

Here's my version to do only a single pass of the table.

But I'm not sure why you want to list only "D" in the result, since both "B" and "D"...

Seems to me like it must be two different RAID5 sets ... wouldn't different drives on the same RAID set already be using both drives?!

Either way, I'd delay your #1...

Neither CAST nor CASE is actually necessary here:

SIGN(CHARINDEX('@', <string_value>))

Btw, if weekdayid is unique (and it seems like it has to be for this table to make sense), get rid of the dopey IDENTITY column in this table! ...