I agree for database objects. But I like to name my variables bVerdict for booleans, sSomething for strings. Saves a lot of time on long procedures. But...

Why don't you take the time to index it? You're gonna kill the server with that query if it uses a table scan... even if it's a secondary operation.

Yup... looks like civilisation hasn't reached you yet. Sorry to hear that .

It's not long to do... Just browse through my list of posts, you'll come up with about the same results.

BTW I'm just being polite to the users so they aren't...

EM, you still use that thing????

ALTER TABLE dbo.TableName ADD

NewPhoneColName AS Right(Phone, 2)

you can then create an index on that column just like if it was a real one.

Amen .

Why not add a type of categorie and hardcode that type only?? You know you'll have to change this list everytime a new category fits it. This is...

So the answer would be too long I guess .

Approximate post count since I joined :

In case I'm gone when you read this...

This may help you :

IF Object_id('fnSplit_Set') > 0

DROP FUNCTION fnSplit_Set

GO

CREATE FUNCTION [dbo].[fnSplit_Set] (@IDS as varchar(8000), @vcDelimiter varchar(3))

RETURNS TABLE

WITH SCHEMABINDING

AS

Return

Select...

Is this what you mean?

Where Categories.ProductCategoryID in (16, 32, 33, 34, 45, 48, 64, 80, 96)

Because if you want ProductCategoryID = 16 and ProductCategoryID = 32... then it's just...

This will fail : isdate(dos) 1

You're asking the server to convert from char to datetime where the conversion is not possible... You'll have to use a char column in...

It still will take a lot of time to backup and you will lose performance on the application side to maintain the jpegs.

Are you afraid of losing the data integrity...

NP.

Not likely, I'm only one of many good t-sqler here. I just happen to post more than the average.