What part of it is actually normalised??? That's gonna be the real performance killer.

"Last, Your manager has the ability to fire your ass, so you may want to let him "Win"."

Now that's something I don't like to do... I'd try calling it a...

That still doesn't give us the schema, sample data and needed output. Plus execution plans could really be a big help here.

HTH.

Ok, so you can't run the query once/how or whatever and insert the data in reporting table for fast access.

We'll need more info to suggest improvements on the query. ...

UPDATE dbo.YourTableName SET FieldName = REPLACE (FieldName, '-', '-3')

That's how I'd do it... but maybe there's another way in RS (never worked with that product).

Ya it makes sens, I think .

How is that gonna be used in the application?

Even simpler than that.

Table Images

ImageID

ImagePath (or the image itself)

...

Table

Classification

ClassificationID

ImageID (foreign key to the images table)

...

Then

Select Columns, List, from dbo.Classifications S inner join dbo.Images I on S.ImageID = I.imageID

Well maybe you can post a short version .

Is it for reporting?

I'll go with the doesn't matter part (assuming sql server 2k +... and maybe even 7 but I never worked with them).

It's the server that takes the fastest possible way...

Shouldn't the image be in a separate table.

That allows you to join to that table using a case expression and it follows the normalization rules.

Are you using a stored proc/function for this operation??

Nope either... the list of constraints is REALLLLLLLY lllllllllong .

Why do you want to do an indexed view for this task... and what is...

Declare @Date datetime

declare @Time datetime

set @Date = DATEADD(D, 0, DATEDIFF(D, 0, GetDate()))

set @Time = DATEADD(D, - DateDiff(D, 0, GetDate()), GetDate())

Select @Date, @Time, @Date + @Time, DATEADD(MS, DATEDIFF(MS, 0, @Time), @Date)