I'm not sure why the sub-selects are being generated, but removing them doesn't make a difference. It's almost as if the query is trying to use the filtered index when...

Thanks for posting the link. I can safely eliminate any of the .Net-related causes because I have this issue simply running the query in management studio. All I know is...

The select statement on my post is complete - I just copied it from my post into SSMS, changed the offending join to a LEFT join as described in my...

ChrisM@home (10/9/2012)

---

Microsoft has a ton of relevant support articles:

http://support.microsoft.com/search/default.aspx?query=a+severe+error+occurred&catalog=LCID%3D2057&mode=r

Of those, this looks promising:

http://support.microsoft.com/kb/948525

Scanning through this lot, here's what I'd suggest:

List the version / SP / CU level etc of the...

Jason's suggestion sounds spot on.

I would just add that you need to be careful with the metadata. If the destination table structures aren't the same then you will get...

This keeps getting stranger... I've got a few tables with very similar filtered indexes and I've been going through our stored procedures adding the Value <> 0 filter to a...

Thanks for the responses everyone.

I tried the following code which ChrisM@Work suggested:

SELECT dgs.Shift, SUM(dgs.Value) AS ShiftTotal

FROM Reporting.fctDeltaGammaShift dgs

INNER JOIN Reporting.dimLifeLicence LifeLic

ON dgs.LifeLicenceID = LifeLic.ID

AND LifeLic.LifeLicence IN ('LL','LA','CAL')

INNER JOIN Reporting.dimCategory cat

ON...

Thanks for the response. I don't think it's related to the link you sent because I'm not using INTERSECT. Here is the query which generates the error:

SELECT Shift, SUM(Value) AS...