BoL also says the following:

Indexes can be created on either a single column or a combination of columns in a table and are implemented in the form of B-trees. An...

One minor comment on your superfluous indexes...

If you have an index on a,b,c then a second index on a is indeed a waste of space and time. The index on c...

You don't like developers do you? Personally the idea of chastisng a developer because they don't agree with you strikes me as arrogance that really doesn't belong in an IT...

Table-valued functions may also be used in the from clause

SELECT blah FROM dbo.SomeFunction(@Param1, @Param2)

In addition to the restrictions already listed, functions cannot have any side effect. Hence you cannot insert...

Thanks, interesting reading (the entire article)

I'm tending to suspect there's a problem with the disk system (though the SAN people disagree, naturally). The server's not short on memory, got 48GB...

Converting that many records shouldn't fill TempDB.

Try a restart of SQL (assuming that this is not a production system and you can restart SQL without impacting users) as a...

What error do you get? It might be because there are non-numeric values in the column.

Try this

SELECT SUM(CAST(col AS FLOAT)) FROM tbl WHERE ISNUMERIC(col)=1

Looks like your problem is lack of available hard drive space.

You said you had 16GB free of 19GB on drive C, but the tempdb is on drive C and...

In the interests of keeping all relevent info in one thread, see

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=238067

I can't see pictures that are on your hard drive. Please post the results of sp_helptext in text.

Please don't cross-post. Replies to the following thread

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=238067

OK, so it's not HDD space.

Please run sp_helpdb 'TempDB' and post the output

It looks like either the disk that TempDB is on is full, or the TempDB database is set with fixed size and has filled up.

Check the disk, check the properties...

As an aside. Consider moving the insert into a stored procedure and calling the stored procedure from your app. It's more efficient and more secure.

As written, your code is potentialy...

Sure. You can have as many ouput parameters as you want.

CREATE PROCEDURE Test

 @Out1 int OUTPUT,

 @Out2 char(1) OUTPUT

AS

 SELECT @Out1=1, @Out2='Y'

GO

DECLARE @Var1 int, @Var2 char(1)

EXEC Test @Var1 OUTPUT, @Var2 OUTPUT

SELECT @Var1, @Var2

--

I...