It was a bug in SQL Server’s query optimizer. I brought a second co-worker to look over the queries and he was able to find a workaround. (a complex one that slows the query down, but IT WORKS) EDIT: When I say slow, I mean slow. The query ran in about 5 seconds before, and now it is up to over 20 minutes. THIS IS NOT MAKING ME A HAPPY PROGRAMMER!