I may be misunderstanding your request, but why not just use NEWID()

SELECT TOP 1000 FirstName

FROM SampleData..First_Names

ORDER BY NEWID()

FIRST: I'm not attacking anyone, I'm just convinced that my second answer (Only after Matt pointed out an error) will work.

SECOND: Ravi's code will work as well. 😀

Matt, I think...

Jeff Moden (11/29/2007)

---

... and, unless you made the serious mistake of how the server handles null, you cannot compare against a null with signs of equality. It just doesn't...

Matt Miller (11/29/2007)

---

Sorry Jason - gotta part ways with ya here......

Use COALESCE. It returns the first NON-NULL value in the list.

WHERE

col1 = COALESCE(@variable, col1)

Sorry, you got me on this one.

On the Datasource Properties, what are the settings for Connect using: ?

The error points to a Datasource Security issue not report parameter.

I'm not sure, but I'll bet it's obvious. 😀

Anywho, I believe this would be more efficient.

INSERT INTO DC_CLAIMS (CLAIM_SK)

SELECT DISTINCT

...

Ahmed, I'm not clear on what you mean here.:ermm:

Ahmed,

Actually that's not true. However, Lowell is correct in that the @Result= needs to appear directly after the SELECT.

So...

SELECT

CASE @Ind

...

And for more complex "Columns into Rows/Rows into Columns" Look up the PIVOT and UNPIVOT functions new to 2005. They've proven quite handy.

What about ...

DECLARE

@Ind int

,@Result nvarchar(50)

SELECT

CASE @Ind

WHEN 1 THEN...

You guys and your details! :w00t:

divide the number by 1,024. :w00t:

Too funny.. :hehe:

It does appear to "remember" the votes. I just noticed while hovering over the stars, it tells you how many votes were made.