Viewing 15 posts - 32,626 through 32,640 (of 59,099 total)
In that case, I wonder if the OP ever got an answer from somewhere?
Also... I don't believe you can just "soft delete" when the HierarchyID is being used.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 6:39 pm
Tee Time (8/29/2011)
Very nice! I will definitely find the STUFF fuction useful. Learning more and more each day thanks to you all! 🙂
You do realize that all the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 6:37 pm
R.P.Rozema (8/30/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 6:30 pm
R.P.Rozema (8/30/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 6:26 pm
SQL_Ninja (9/7/2011)
I've sent you a pm on this one.
Why not post your answer here?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 6:11 pm
As Lowell pointed out, you have an accidental cross join (think "many-to-many" join and look for the arrows with counts larger than the table or index they're coming from) in...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 6:11 pm
toddasd (9/1/2011)
What would be the logic to populate those values?
Do you already have the columns defined?
Is the start value a running total?
That takes care of #2, but the important question...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 5:49 pm
sql_novice_2007 (9/7/2011)
When I run the above query I am getting the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 6:26 am
SQLServerMS (9/7/2011)
I need to populate the values for a column in a sequential manner as below, these need to be auto generated:
i1st it starts with
000001
000002
......
999999
A00001
A00002
......
A99999
B00001
......
B99999
......
Z99999
ZA0001
......
ZA9999
......
ZZZZZZ
How can i achieve this.......
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 6:12 am
cidr (9/6/2011)
I'll double check with them. I think the logic they had was that they wanted to slice/dice data, by productID, then by SalesmanID etc, not together.
However,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 12:26 am
SQLRNNR (9/6/2011)
Jeff Moden (9/6/2011)
Roy Ernest (9/6/2011)
Yay...!!! I beat the THREAD to the landmark. I hit 3000 posts before the thread hit 3000 pages. 🙂
I was going to post a prediction...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 12:20 am
mister.magoo (9/6/2011)
I would suggest you keep an eye on this because, from past experience, whenever Jeff goes quiet for a day or two...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2011 at 12:17 am
Roy Ernest (9/6/2011)
Yay...!!! I beat the THREAD to the landmark. I hit 3000 posts before the thread hit 3000 pages. 🙂
I was going to post a prediction that you'd easily...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2011 at 12:23 pm
I was ready for Y2K in 1980 and I'm ready for 2079-06-06 right now. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2011 at 11:18 am
Tom.Thomson (9/3/2011)
I guess pop tarts are nice, but that's purely guesswork as I haven't a clue what one is.
It's fruit flavored SOS with the "S" on the inside. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2011 at 10:59 am
Viewing 15 posts - 32,626 through 32,640 (of 59,099 total)