Avoiding the 2100 parameter limit in LINQ-to-SQL
In a project I am currently working on, I need to access 2 databases in LINQ in the following manner:

1: I get a list of all trip numbers between a specified date range from DB1, and store this as a list of 'long' values

2: I perform an extensive query with a lot of joins on DB2, but only looking at trips that have their trip number included in the above list. 

Problem is, the trip list from DB1 often returns over 2100 items - and I of course hit the 2100 parameter limit in SQL, which causes my second query to fail. I've been looking at ways around this, such as described [here][1], but this has the effect of essentially changing my query to LINQ-to-Objects, which causes a lot of issues with my joins

Are there any other work arounds I can do? 


  [1]: http://stackoverflow.com/questions/567963/linq-expression-to-return-property-value/568771#568771
Avoiding the 2100 parameter limit in LINQ-to-SQL
===

In a project I am currently working on, I need to access 2 databases in LINQ in the following manner:

1: I get a list of all trip numbers between a specified date range from DB1, and store this as a list of 'long' values

2: I perform an extensive query with a lot of joins on DB2, but only looking at trips that have their trip number included in the above list. 

Problem is, the trip list from DB1 often returns over 2100 items - and I of course hit the 2100 parameter limit in SQL, which causes my second query to fail. I've been looking at ways around this, such as described [here][1], but this has the effect of essentially changing my query to LINQ-to-Objects, which causes a lot of issues with my joins

Are there any other work arounds I can do? 


  [1]: http://stackoverflow.com/questions/567963/linq-expression-to-return-property-value/568771#568771