Thanks for the reply. Actually, this is properly normalized, rather, as normalized as it can get. The courseId uniquely identifies a course in our Blackboard system.
So far, I haven't seen any performance issues. I even had to add a couple other joins to get enrollment and user details. Still, it's pretty darn quick. Thanks -----Original Message----- From: Jeff Becker [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 4:07 PM To: CF-Talk Subject: Re: (ot) SQL Join With LIKE in Join Criteria Very interesting Michael. A good solution based on the environment your working with. I'm no DBA, but I do have a feeling this is an example where proper normalization would help out significantly. In terms of performance, I have no idea if you'll have a problem, but I believe anytime a LIKE '% is used, its a whole table scan and thus performance could be an issue. Good solution.. not sure what you can do to get around the LIKE '% . Will be interested to hear what more DBA types will say about this. Jeff ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:312386 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
