Viewing 15 posts - 33,631 through 33,645 (of 59,099 total)
Roy Ernest (6/16/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2011 at 7:25 am
You didn't read the entire post! 😉 I told you how to get that. Just remove the "*," from the code. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2011 at 7:18 am
James Millar-305032 (6/15/2011)
I have to extract data into separate fields for the CA1, CA2,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 11:40 pm
Just my 2 cents. I agree with Remi... the recompile will likely keep the hang from happening again.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 11:31 pm
aracy (6/15/2011)
You're right, if it was smooth sailing then I wouldn't be here.
I got it to preform well. My problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 11:29 pm
If you just add it to the Model database, it'll be there for every new database you create. Make it a good one, though, because it will also appear...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 11:19 pm
Here you go... uses your original data and will, of course, handle additions such as subnodes on any other nodes including "B".
WITH
cteGetAllData (ChildID, ParentID, ChildName) AS
(
SELECT IdFolder,IdFolderParent,FolderName
...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 11:12 pm
nguyennd (6/15/2011)
ah, My customer make sure: no data like this:
A
--A1
----A1.1
--A2
----A2.2
------Item code = 3
------A2.2.1
--------Item code = 1
--A3
B
--Item code = 2
C
Every data input are reasonable.
That data doesn't match the original data you...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 11:04 pm
On second thought, I'd better ask... is the order of the hierarchy based on the number of subnodes that each level 2 node has under it?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 10:52 pm
Post the code you've written to do the first export you talked about and we'll show you how to modify it to do what you want.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 10:29 pm
Hi Grant,
I know your code is for a one-off test so performance may not matter, but I thought I'd show you a way to get rid of the While loop...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 10:23 pm
Rich Yarger (6/15/2011)
So - here is a small sampling for you to see. What would you do?
Heh... hunt the people responsible for this data travesty down and take them out...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 10:06 pm
Got a phrase that you use to share a difficult concept?
As a matter of fact, I do... [font="Arial Black"]RBAR[/font] 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 10:00 pm
SQLRNNR (6/15/2011)
Jeff Moden (6/15/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 9:37 pm
simon.mendoza (6/3/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2011 at 9:31 pm
Viewing 15 posts - 33,631 through 33,645 (of 59,099 total)