@Brian is right, the query is more complicated and it was just a placeholder. When I get back in the office on Monday, I will run some more speed tests. I am not the DBA and the city office where I am working doesn't have access to SQL Server Management Studio. All of that is kept by the IT Staff in a different building and they are really anal about answering questions. Adding to that, there is a cold war between the city office I am working in and the IT department. This means there isn't much communication or willingness to help each other. The office has experienced database problems for years. I just learned from our office IT representative that some of his queries in the past have failed for no reason - that might explain why some of mine were failing through executesql. Also, he and I have experienced wildly varying execution times on queries, even ones made within seconds of each other. It doesn't explain all of the behavior I have experienced, like why it is so much slower on executesql than in MS Server Express and why executesql seems to fail more on larger queries, but I am content to chalk this up to a local database issue right now. Once the project is done, I will use more leverage to get to the bottom of this IT problem. Thanks all. I will use your suggestions when I investigate.
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
