Viewing 15 posts - 53,671 through 53,685 (of 59,072 total)
You'll have to run 8 separate searches, or columns
Or... we can cheat like hell 😛
--===== This just creates demonstrable test data and is NOT part of the solution
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 10:59 am
I've seen "Runnable" in 2k, but never "Running" and, as you probably found out, BOL 2k doesn't have much info on the sysProcesses table... but the following URL (from BOK...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 10:34 am
sp_MakeWebTask is one way...
Hundreds of other ways using OSQL, OpenRowset, etc to fill spreadsheet templates, make simple text files, etc, etc.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 10:17 am
Double posting is so rude... waste time answering one only to find answer on the other.
http://www.sqlservercentral.com/Forums/Topic430841-5-1.aspx
http://www.sqlservercentral.com/Forums/Topic430840-146-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 10:10 am
Double posting is so rude... waste time answering one only to find answer on the other.
http://www.sqlservercentral.com/Forums/Topic430841-5-1.aspx
http://www.sqlservercentral.com/Forums/Topic430840-146-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 10:10 am
But now I want to know the newly inserted row number
...and, if you're smart, you'll make the trigger code handle more than 1 row at a time. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 10:01 am
Two way street here, Jeff... how about posting your solution? Two reasons... like I said, "two way street" and the other is these types of problems typically lead to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 9:59 am
Double posting tends to tick folks off because they may spend some time of one of your posts trying to give you an answer only to find that a good...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 9:56 am
Double post...
http://www.sqlservercentral.com/Forums/Topic430917-373-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 9:42 am
Look in the Index of Books Online for "cross-tab reports"... good example there.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 9:37 am
Ok, Ray... I've changed the code above... minor tweak... should do what you want now... give 'er a try on a test table like the one you posted...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 9:00 am
I don't think there's any overhead with CI... it's a difference of only 1 bit (32) and only an internal difference of what the mask looks like.
I love CI because...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 12:29 am
p.s. Code above assumes all "Amounts" are negative... may have to make a second pass for positive "Amounts".
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 12:23 am
Yes sure you can add columns. Is it for Cleaning the data ?
Yes... and for storing it, too. The following works on the data you provided for the tbExtract...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2007 at 12:14 am
Yeah, I've seen that... but usually for smaller sets of rows.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2007 at 10:56 pm
Viewing 15 posts - 53,671 through 53,685 (of 59,072 total)