View Single Post
Old 08-24-2010, 08:12 AM   #266
GlenBarrington
Cheese Whiz
GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.
 
GlenBarrington's Avatar
 
Posts: 1,986
Karma: 11677147
Join Date: Jan 2010
Location: Springfield, Illinois
Device: Kindle PW, Samsung Tab A 10.1(2019), Pixel 6a.
Quote:
Originally Posted by meromana View Post
Yes, this is exactly the problem. I am grouping on columns that are not indexed (the tables/views I query are all part of a database that's "in development"),. . . Maria
DEVELOPMENT!?! (sorry for the late-ish response, I just caught this little phrase) You NEED to get the project manager involved! It is the height of LUNACY to tell a user that a query they are running in a development database that a query they have tweaked as best they can that there is something wrong with the query. I mean there could still be a LOT wrong with your queries, but the PM and the Database architect need to get involved at this point and make sure you aren't uncovering some inherent design fault!
GlenBarrington is offline   Reply With Quote