Put the clustered index on a DATE COLUMN

Then > Delete from Table where DateCol between @StartDate and @EndDate.

That will speed it up a lot. Also make sure you have...

Why do you use the table function version instead of the inline version??

Seriously???? This function uses a select to get the data. It CANNOT be faster or even the same speed as the query that fetch the info without doing ANYTHING...

So you're working under 2 ids now???

Thanx for that info. But the real question is what do you have to do with that data???

Why not just rtrim()???

Also I do not have that script anymore (was done in a dts package).

What it did was basically this >>

For each tables in db loop

fetch the columns...

Ok, then you'll have to set it only once for the query analyser. Note that this setting is local for each computer, so if the guy always switches around...

What program are you using to present the data (that is causing that problem)?

Are you sure that there's more than 255 characters in the data you are seeing?

What the heck are you trying to do with that thing???

Sample data and output would be very usefull here...

Check the query analyser settings. There's one that "trims" the display to 255 characters. Just set that to the max value and you'll see your data at the...

Are you using something like : Select Col1 from dbo.MyTable to fetch the data (dbo. is the important part).

How is that informative to the users, the developpers? How do you track that error without documentation??

I seriously hope you're kidding with that one???

create the table first then :

insert into TableName (Columns) exec SP_HELP 'TABLE_NAME'

Seems like a bug. Have you tried a full select into to add the identity?

I know it would only be a workaround but if that gets you out of...