http://tinyurl.com/3nzl8ju

http://tinyurl.com/3lzuvjw

The error is being thrown at parse time , so the try catch block is not actually being entered.

Sure , you can have an action of a text box to a report passing through the parameter .

Or use a sub-report to show all three at once.

In addition to what Gail said you can force a merge join using 'LEFT MERGE JOIN'.

It will *probably* be a lot more expensive

Good work here Sean

@normanshongo2003 I would recommend Itzik ben gan's 2008 fundementals , not sure what 'exam' you have or for what reason , but i think you...

If you want the dept with the lowest , average salary you need to order by the average aggregate function and use the TOP clause

Please post the execution plans as per

http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

There are a fair few udf used there , remove those as see if performance improves.

UDFs (except inline table valued ones) perform poorly...

Wooo

A lot going on in there , as stated we need the actual plan.

The DDL of the view and tables involved would help us make sense of it ..

Please post execution plans as per

http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Views are no different from any other query, what does the execution plan look like ?

Combined with the Easter Holiday last weekend as well, April is not going to be the most...

Good stuff , sounds like you are on the right path.

From what i cant find those waits are specific to BACKUP...

Yes i would , you need to find which statement is causing the unusual usage.

The best tool for that would be running...

Also , are you using database snapshots ?

http://msdn.microsoft.com/en-us/library/ms175158%28v=SQL.90%29.aspx