DevForce Community Forum : Problem with a RDBQuery http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce Classic : Problem with a RDBQuery Thu, 11 Jun 2026 10:49:15 -700 Wed, 26 Dec 2007 11:32:51 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=630 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Problem with a RDBQuery : The error message that you are... http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2291#2291 Author: davidklitzke
Subject: 630
Posted: 26-Dec-2007 at 11:32am

The error message that you are getting is from SQL Server, not DevForce,  SQL Server has a limitation of 2100 parameters that it will accept in a SQL statement.  There are other limitations as well.  For example, a SQL statement may not contain more than 8044 characters.

 
To handle very long queries, you will need to break the large query into multiple smaller queries.
]]> Wed, 26 Dec 2007 11:32:51 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2291#2291 Problem with a RDBQuery : The actual source of the error... http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2290#2290 Author: davidklitzke
Subject: 630
Posted: 26-Dec-2007 at 11:12am

The actual source of the error is coming from the SQL Server which has a limitation of 2098 parameters that it will accept in a SQL statement.  I assume that this number may change from one database to another.  There is also a hard coded limit of 8044 characters that the SQL Server will accept in a SQL statement.
 
You will need to break up your long query into a sequence of smaller queries to handle these very large queries.
]]> Wed, 26 Dec 2007 11:12:37 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2290#2290 Problem with a RDBQuery : You see, we were surprised, that... http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2284#2284 Author: Makarov
Subject: 630
Posted: 24-Dec-2007 at 6:45am

You see, we were surprised, that this restriction was not mentioned in the manual, and wasn't detected by object itself.
Are there any methods to reduce given RdbQuery to execution-safe fragments?
We are trying to implement one algorithm, but there are some problems, because constructor new RdbQuery(RdbQuery query) creates a copy, which fields refrence fields of initial object, not the copies.]]> Mon, 24 Dec 2007 06:45:09 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2284#2284 Problem with a RDBQuery : I am not sure that I understand... http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2283#2283 Author: IdeaBlade
Subject: 630
Posted: 21-Dec-2007 at 2:34pm

I am not sure that I understand your complaint.  Do you think that the number of arguments in the EntityQueryOp.In clause should be infinite?  Even if the number of arguments in DevForce could be increased, I am sure that there must be some limits in the database.]]> Fri, 21 Dec 2007 14:34:57 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2283#2283 Problem with a RDBQuery : Hi. I have following problem with... http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2273#2273 Author: Makarov
Subject: 630
Posted: 20-Dec-2007 at 8:21am

Hi.
I have following problem with a RDBQuery.
When number of arguments for EntityQueryOp.In clause exeeds 2100, an error occurs:
"The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100"]]> Thu, 20 Dec 2007 08:21:25 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=630&PID=2273#2273