﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Teradata Forums / Teradata  / Teradata Advanced Analytics User Group  / Is there a performance hit selecting rows based upon a constructed CASE column? / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>Teradata Forums</description><link>http://www.teradata.com/teradataforum/</link><webMaster>info@teradata.com</webMaster><lastBuildDate>Fri, 05 Sep 2008 19:39:35 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Is there a performance hit selecting rows based upon a constructed CASE column?</title><link>http://www.teradata.com/teradataforum/Topic11127-22-1.aspx</link><description>Hi Ti,you're right, there's no difference. Btw, if you want to lower CPU usage, stay away from conversions involving type casts from char to numeric/date and vice versa.Dieter</description><pubDate>Thu, 03 Apr 2008 03:11:43 GMT</pubDate><dc:creator>dnoeth</dc:creator></item><item><title>Is there a performance hit selecting rows based upon a constructed CASE column?</title><link>http://www.teradata.com/teradataforum/Topic11127-22-1.aspx</link><description>Hi,Quick question.  I think there is no difference, but I need to be sure.In a SELECT or INSERT statement if I use a CASE statement to create a new column and then select rows based upon the value of that new column, is it any slower (or faster) than simply repeating the logic of the CASE statement as a direct WHERE condition?I'm processing a *lot* of data with nasty string functions and I need every ounce of optimisation I can get :)ThanksTim</description><pubDate>Wed, 02 Apr 2008 17:35:59 GMT</pubDate><dc:creator>TimManns</dc:creator></item></channel></rss>