I'm glad you bumbed this Jeff, because I had meant to get back to the OP with a better function to calculate, then forgot :(, ...

Stephen:

Here is a Much better...

Heh. Darn tootin'.

Heh. You know Jeff, I think that this might change that article that you're writing, just a little bit. I bet you don't mind too much though. ...

Oh, I see. It does repeat with...

Jeff Moden (1/31/2009)

---

Nah... I take it back... not clever... freakin' brilliant. The key to this whole thing is the grouping. You've gotta be able to group each "cluster"...

Oh. Well if that is true then clearly...

Well, you cannot fix it without testing, and we cannot help you any further without the information that we requested.

Please feel welcome to get back to us when...

Glad I could help.

Thanks for the response Joe. However, I need you to answer the questions that I asked earlier:

RBarryYoung (1/31/2009)

---

What is the error that you get?

Which derived table is the one...

Glad I could help.

The only way close to 90% is to parse the SQL of the procedure and see if that are any "data retrieval" SELECT statements (not sub-queries). Thats no easy...

Here is a non-cursor version of your sript:

Declare @Prefix varchar(255)

Declare @tmpstr varchar(MAX)

Set @Prefix = '

exec master.dbo.sp_addsrvrolemember @loginame='''

Set @tmpstr=''

Select @tmpstr = @tmpstr

+ Case When sysadmin = 1...

Well, two things that I noticed: 1) unnecessary use of a Cursor, and 2) "From syslogins" is invalid in 2005, should be "From sys.syslogins".

Hmm, well one thing that I noticed is your use of "COALESCE(COUNT(* ),0)". I think that I understand what you are trying to do with this, but I cannot...

What is the error that you get?

Which derived table is the one that is returning no rows?

And what would you like it to do in those cases?