Are you really updating a clustered key? That'd slow your updates waayyy doowwn.
Have you identified what query is causing this problem? Ok the situation is: When you use a clustered index, the information is PHYSICALLY stored in order on disk. By changing the clustered key, you are moving a heck of a lot of data around within your pages.... combine that with moving (updating) large binary data types of text, ntext, or image columns, the query engine doesn't like it at all. Simple solution. break the query into two steps. cheers, >>> [EMAIL PROTECTED] 08/04/05 10:47 am >>> Sorry forgot to change the subject: Does anyone know why this occurs and how to fix this? java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]The query processor could not produce a query plan from the optimizer because a query cannot update a text, ntext, or image column and a clustering key at the same time. Sometimes the above happens and sometimes it doesn't. Anyone seen or know what this actually means? Regards Andrew Scott Analyst Programmer CMS Transport Systems Level 2/33 Bank Street South Melbourne, Victoria, 3205 Phone: 03 9699 7988 - Fax: 03 9699 7976 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ Scott Thornton, Programmer Application Development Information Services and Telecommunications Hunter-New England Area Health Service Phone RNH +61 2 49236078 Fax +61 2 49236076 [EMAIL PROTECTED] --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
