I'll save a bookmark so that we can finish this discussion in ±70 years .

Convert to date time then... I can assume the computing power will be so great by then than a 5000 rows table won't take more than one 0.0000000001 MS to process.

Sounds a lot like a homework question... or someone's trying to learn sql all by himself!

--set joe celko angry rant mode on

Just a question here.  Do you store you ints in varchars and your varchars in ntext.

If you really need to speed this query...

Please do not cross-post.  We monitor all boards.

Finish this thread here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=291&messageid=327483

Consider this thread closed.

SET FMTONLY ON

GO

SELECT * FROM dbo.FnName ('Dummy value')

GO

SET FMTONLY OFF

This will return the column names only without executing the Query.

All of those... plus I get to pick when I come in and go out .

EXEC master.dbo.xp_cmdshell @s-2

Keep the clustered index

Delete with 25K rows batch

Backup the log more regulaly (maybe even each loop if you are very low on space).

I don't think removing a single index will...

I already implied that... maybe I was too subtile .

Alright, please post the final answer so that others may benefit from your findings!

Insert into Table (Date, John, George, Joe, Fred) VALUES (GetDate(), 'John', NULL, NULL, NULL)

Substitute the value part with parameters and that will always work.

Do you see anything wrong with this...

Please provide the table DDL, some sample data and the required results from that data.  I just don't want to guess at this answer .

Why?  The columns name shouldn't change often in the life of the application!

Where are those Joe Celko quotes when you need them?!?!!

DECLARE @Time AS CHAR(6)

SET @Time = '181533'

--this assumes that there are always 6 digits in the column

SELECT DATEADD(SS, CONVERT(INT, LEFT(@Time, 2)) * 3600 + CONVERT(INT, SUBSTRING(@Time, 3, 2)) * 60...