Is this a permission issue .. Do you have access to these DBs ?

--

SQLBuddy

Restoring the system databases would help you in retaining the server level settings. If you restore MSDB, you would get all your old jobs. But if you need jobs from...

It's that way starting from SQL 2008 onwards. But SQL 2005 it's copied to the TLog Backup location ..

--

SQLBuddy

That's not sufficient. You need to restore the intermediate log backups too before you could restore that last log backup ..

--

SQLBuddy.

Check for WAITS, CX_PACKET WAITS and any IO issues. Also can you let us know the metrics for the CPU, Memory and the Disk counters.

Do you also experience any blockings...

It's hard to tell without seeing the actual insert statement or the execution plan. Please post it if possible ..

--

SQLBuddy

Don't use function in the where clause. That will slow down the performance by disabling the indexes. Do as Luiz mentioned.

--

SQLBuddy

Book recommended by Sean is a Good one to start with ..

--

SQLBuddy

Post the execution plan ..

--

SQLBuddy

Compare the server level settings of both 2005 and 2008 servers. Are they same or missed something on the new server.

Also check the DB file layout , tempdb layout...

Check the execution plan and see if it needs any index or maintenance.

--

SQLBuddy

You may get this error if the login cannot be validated by AD. Did you find anything in the application or Security logs ?

--

SQLBuddy

Try using this option "Optimize for Adhoc workloads " .. This reduces memory consumption by adhoc query plans and helps in eliminating procedure cache excessive consumption.

On 32 bit systems, Procedure...

Did you try the option " Be made using the login's security Context " ..

--

SQLBuddy

Try to do a restart of the passive node. And try it.

--

SQLBuddy