Viewing 15 posts - 55,891 through 55,905 (of 59,072 total)
And, don't use recursion to solve this... SQL Server 2000 cannot go "N" levels... it's limited to only 32 levels and then "BOOOOOOM!"
--Jeff Moden
Change is inevitable... Change for the better is not.
July 5, 2007 at 6:22 pm
Based on the original code you posted, you shouldn't have a problem...
The @bfr_tag holds 634 characters.
@general_notes holds a max of 2500 characters.
@day_notes holds a max of 2500 characters.
@nite_notes holds a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 5, 2007 at 6:20 pm
Thank you for the feedback...
If you are still having problems or need to use "row_number" (now that we know you are using 2k5) instead of an Identity column, please post...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 5, 2007 at 8:31 am
Actually, they did... nice red/white/and blue google with a bald eagle and the whole shootin' match. I believe Google logins sense which country you are in to allow for if...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 5, 2007 at 8:06 am
Thanks for the info Michael... I'm not much of a "web guy"... what makes it difficult to use "file shares" in the Web world... asking because I don't know and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 5, 2007 at 8:02 am
Remi is spot on both in statement and method suggested... you still don't need a cursor to do that. Do like remi recommended...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 5, 2007 at 7:58 am
First, you have a major bug in the code you posted... you don't create a value for @GenInfo_ID variable which means that you are populating the GenInfo_ID column of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2007 at 1:54 pm
Serqiy is correct... is the stuff you putting into @List available in a table anywhere? If so, we can resolve the whole table instead of using RBAR methods...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2007 at 11:45 am
If you're talking about the method in the URL I provided and not the BOL solution, some indexes will certainly help once the tree for the whole DB is constructed. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2007 at 11:40 am
Yeah... that's the bugger about it... @variable=column=formula ONLY works for Update and only with certain other "hooks" present....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2007 at 11:33 am
| I guess the hardest part for me is trying to understand someone else's logic and trying to figure... |
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2007 at 11:22 am
See "expanding hierarchies" in books online. There's lot's of other methods but that one is pretty easy.
For wicked speed, try the following URL with the understanding that it takes a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2007 at 12:49 am
That and a strong, respectful salute to the folks in the armed services who made it possible and continue to make it possible to enjoy such freedoms! Thank you all.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2007 at 12:42 am
Never mind about the @WhereClause... was going to try to make it so you didn't need the dynamic SQL, but I can't wait for it...
One of the common methods for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 11:16 pm
Working on this but need some info... what column names will you use in the @WhereClause variable for this proc only? Please give an example of what you will pass...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 9:59 pm
Viewing 15 posts - 55,891 through 55,905 (of 59,072 total)