Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. orangefluffy

    Internal Query Processor Error ... query too long :(

    It's working way faster! My old SQL is so elementary. It's embarrassing. Thanks Esquared for pointing out George's statement regarding Split. I am new on this forum. I feel a bit lost.
  2. orangefluffy

    Internal Query Processor Error ... query too long :(

    Thank you everyone. It's working and working better now. Yes, the nodeId list is created dynamically. I tried ESquared's solution. dbo.Split isn't available in SQL server 2000. I ended up inserting data into a temp table to store the nodeIDs. =============================================...
  3. orangefluffy

    Internal Query Processor Error ... query too long :(

    Hi All, I am getting the following error in SQL 2000. Internal Query Processor Error: The query processor could not produce a query plan. Contact your primary support provider for more information. My query gets way too long, maybe in-efficient and now, it's giving me an error. ---- Here is...
  4. orangefluffy

    The query processor could not produce a query plan??

    sorry. first time posting here. I don't see a sql forum. btw, my sql server has sp4
  5. orangefluffy

    The query processor could not produce a query plan??

    Hi All, I am getting the following error in SQL 2000. Internal Query Processor Error: The query processor could not produce a query plan. Contact your primary support provider for more information. My query gets way too long, maybe in-efficient and now, it's giving me an error. ---- Here is...

Part and Inventory Search

Back
Top