Select * From will do a full table scan, so indexes wont be used.

In data view click on the ... next to the Dataset name and on the fields tab add the fields manually. Fields will only be added automatically from non dynamic...

If you populate a temporary table with @BPCode then you can use where ShortName in (Select Shortname from #temptable)

If you run the command on its own through Management Studio what message do you get?

See http://www.sqlservercentral.com/scripts/Backup+%2f+Restore/30138/ this could be adapted

See http://www.sqlservercentral.com/scripts/Backup+%2f+Restore/30138/ this could be adapted

Try SELECT UPPER('John Doe')

Right click on the properties of the event and look at history. Has the alert ever been triggered? The history will tell you. If it has fired the failure to...

Try a different alert, I'll be honest I have been lucky enough not to come across any deadlocks in SQL Server 2005 databases I've supported - things have been looking...

Check checking did you enable the profile you created as per the article? Did the alert fire into the event log? do any of the other events fire?

AndyD

Default fill factors at 0% is fine if you have high spec’d servers and small databases that are not heavily used. In these cases also 90% won’t make a great...

Sorted, bringing file into sql server as an image and extracting from here as a file.

Depends on how you did the migration, you may need to check for orphan users...

EXEC sp_change_users_login 'Report'

I'd try one of the log reader tools available, to read through your logs, you may be able to download the tool for a short trial, which might be enough...

Some ideas....

* A review of fill factors is a good one for the agenda.

* Profile for duration and review SQL and indexes on tables on the longest running procedures.

*...