Sean Lange (7/22/2013)

---

richard.noordam (7/22/2013)

---

it's because you aren't actually looping through the data. put an identity column in and then reference it with your count and it will likely work...

it's because you aren't actually looping through the data. put an identity column in and then reference it with your count and it will likely work fine.

you might also...

i actually didn't use such a solution, but did use a table variable and a coalesce statement to acheive the same thing.

I was, however, curious as to it's effect. ...

i believe what you want isn't = Null but IS NULL

apparently there is some application (ms access or some other 3rd party software) that is calling the sp_adduser stored proc.

I've deny'd execute on this sp to eliminate this issue...

i do have to say, you should give yourself a bit more credit, as our private message indicated you did understand my problem, and did suggest a potential solution, which...

You are looking for best practices in dealing with data is denormalized. I get that you have done this via dynamic cross tab but there isn't really a normal way...

first of all i was NOT looking for a specific solution. So your comment, and snarkyness are not appreciated, nor warranted.

I was indeed looking for a pattern of behavior...

well this is what was done to accomplish it. inelegant as it seems to me.

1. generates the SQL YearQuarter list.

declare YRQList cursor for

SELECT DISTINCT YearQuarterID from CCSGen.dbo.vwODSSM_YearQuarter where...

I should also add that the column list changes and gets added to on a quarterly basis (as defined by the institution i work at) and the data set...

96719672967396749781978297839784989198929893989499019902

09672967300009784000000

00000000000989499010

First row is the header.

each row has an identifier as well, but as i go thru the rows, what i should get the first occurance only.

the columns are varchar(4)

ie.

row...

I'm going to have to respectfully disagree with your indication as to what my solution should of been.

Yes, the solution you pointed to is very elegant, but it is also...

Leo Peysakhovich (6/20/2012)

---

Agreed with SSC-Enthusiastic. This solution is very danger to implement. Especially in environments where multiple DBAs and database developers controlling jobs in a heavy processing environment. If for...

Mike Dougherty-384281 (6/20/2012)

---

If the job fails to schedule its next occurrence then the job never runs again? So for quarterly jobs, you won't find out about the failure for...

The purpose of this example was a demonstration of individual steps for clarity.

Yes it could of very easily been done in less steps.