Viewing 15 posts - 35,011 through 35,025 (of 59,102 total)
You bet. Thank you for the reply. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
February 17, 2011 at 6:21 am
GSquared (2/16/2011)
Fal (2/16/2011)
Koen Verbeeck (2/15/2011)
Fal (2/15/2011)
WayneS (2/15/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:33 pm
Fal (2/16/2011)
Brandie Tarvin (2/16/2011)
... But I'd avoid dark alleys, if I were you....
Well, there goes the joy in life.
But wait, you mentioned something about "tar and feathers"??
Steve.
Mmmmmm. Makes...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:32 pm
CirquedeSQLeil (2/16/2011)
For the execution of Wayne:
--get spid of code requestor
sp_whorequestedcodeIntheThread 'Wayne'
--use returned spids to verify the request
dbcc inputbuffer(61)
--output
'Wayne definitely requested code on the thread'
--yup that's the one
Kill 'Wayne'
just...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:31 pm
Ok... peeling one potato at a time, here's how to concatenate the CapturedTime's. I haven't tested it because I couldn't figure out how to populate the variables so they...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:22 pm
ColdCoffee (2/16/2011)
Yes we have got the sample data, but what do u want to achieve from that? I mean, can u be still more clear on your requirement.
The "Rosetta Stone"...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 5:54 pm
Stamey (2/16/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 9:18 am
Actually, if you use just the inner select in the code example and get rid of the next start date, you'll have your answer. Give it a try.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 7:00 am
I'm on my way to work. If someone else doesn't get to this first, I post a coded reply tonight.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:59 am
WayneS (2/15/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:54 am
sql_butterfly (2/15/2011)
I've attached the execution lan for update statement.
That's half of what we need... please post the code.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:48 am
Have a look here. Wayne S. wrote a nice bit of "SQL Spackle" which explains how to do it.
http://www.sqlservercentral.com/articles/comma+separated+list/71700/
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:47 am
Thanks for the book reference. I'll take a look. Michael Coles is one of the "good guys".
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2011 at 6:44 am
Use your query (without the running balance) to populate a TempTable, apply the correct clustered index in the order you want the running total (decrementing balance) be processed by, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 9:14 pm
No, I don't believe there is. Consider building a "sister" table and a trigger to populate it when something is modified.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 9:10 pm
Viewing 15 posts - 35,011 through 35,025 (of 59,102 total)