2005 to 2012 is greater than 2 major versions. Try this, 2005 to 2008 or 08R2, up the compatibility level, new bak, then restore to 2012.

Basically "90 compatibility level...

Did you see this?

http://www.sqlservercentral.com/articles/Extended+Property/137761/[/url]

I didn't read all your code, sorry.

Is this helpful?

(common alternative to a cursor)

while @RowCnt <= @MaxRows

begin

...

Select @RowCnt = @RowCnt + 1

end

Is it the alloc_unit_type_desc (LOB Data) from dm_db_index_physical_stats causing your pain?

Sounds like a permissions issue to the destination path on the subscriber.

Extended Events = NBAN (Node by agonizing node)?

Seriously though, this is the best article I've seen. Anyone got one better? [EDIT: ...for pre-"view target data..."]

https://www.brentozar.com/archive/2015/01/query-extended-events-target-xml/[/url]

Just brainstorming here...

Based on your limitations you could try to get creative with the timelimit and delay parameters of the OLA script with the intent of slowing down your index...

Have you tried bumping the timeout? I'd start with that and go from there.

Normalize by block number?

I usually take this route: http://www.ideaexcursion.com/2009/01/05/connecting-to-oracle-from-sql-server/[/url]

I also usually create a local ODBC > System DSN connection, via the TNSNAMES.ora file, so that I can verify my credentials and general connectivity.

Make...

I've used it on many servers to resolve timeouts when backing up to network storage without any negative side effects.

...and yes you would implement on your prod box.

What evidence do you have exactly?

Your user could be using impersonation to execute as another user.

The log shipping restore job is failing because,

You need to restore the LOG backups that are older than UserInfo_1_20160222093006.trn. Specifically,

since...

I thought you already did that:

If you haven't, try just re-running the log shipping restore job and checking the logs to see what the problem...