It sounds like you might be dealing with a case of bad parameter sniffing. Instead of freeing the entire proc cache and the buffer cache (which requires reloading everything), try...

Absolutely run the Upgrade Advisor prior to the upgrade.

I suspect the deprecated code you're thinking of is the old ANSI 89 OUTER JOIN syntax

SELECT *

FROM Table1,Table2

WHERE Table1.ID *= TAble2.ID;

You...

I'm totally with Gail on this, remove the hints as a first step, then look at the execution plan to understand where things are going wrong.

If UserID is coming up NULL, then your problem is here:

set @UserId =(select UserId from aspnet_Users where UserName= @Username)

Not with the other statements.

Take the script you have, turn it into an ad hoc TSQL statement and run it through sp_msforeachdb

No way to know that for sure based on what you provided. It could be almost anything. Look to see if you have errors before this one. Also, if you...

If you're just moving data from a single server to a second server then you need to tune the procedures and processes in place. If you're trying to copy the...

Wrap the whole thing in a transaction first. Then, use the OUTPUT clause to output to a temp table or a table variable (a table variable would probably work well...

Exactly what I was thinking. Even if you could, and assuming you have a key constraint in place, you can't,...

Also, check for blocked processes and collect the wait stats before & during running the procedure to see what's causing stuff to slow down.

Another vote for reading Gail's excellent articles.

You can take a look at sys.dm_exec_requests to see if you're getting blocking on any of the processes. I'd probably start there on a...

I have seen backups cause problems with a server, but usually only if that server is already operating right at the edge, with extremely have I/O & Memory operations. In...

If the transaction completes during the database backup process, it will be included in the backup. Data that is changed during the backup process is logged at the end of...

Same process as any rollout or upgrade, you have a solid set of tested backups. The key word in that sentence is tested. Other than that, since the old days...

I don't think you can without taking the log shipping offline and then rebuilding it.