Viewing 15 posts - 3,406 through 3,420 (of 8,416 total)
Aha! Found the original thread:
http://www.sqlservercentral.com/Forums/Topic896583-338-1.aspx
The explanation in the second thread is still worth a read though.
May 16, 2010 at 10:24 am
WayneS (5/16/2010)
<CuriousMode>Care to share this trick with us? Might be able to learn something new...
</CuriousMode>
oh wait... is it just a CROSS APPLY? 😀
What do you mean just an APPLY? 😛
It...
May 16, 2010 at 10:14 am
Jeff,
I feel so much better now I have cost you some time writing that full explanation :laugh:
No, seriously, I hear what you're saying about the recent posts on hierarchies -...
May 16, 2010 at 10:09 am
neelsmail (5/16/2010)
That didn't make any difference. Mainly, I am not certain it would make difference to the time taken for *inter process communication* between my C# app and SQL Server.
Adding...
May 16, 2010 at 10:03 am
I would add a "SET NOCOUNT ON;" to the top of the procedure to suppress DONE_IN_PROC messages.
Also, can we see the C# code to call the procedure please?
I should point...
May 16, 2010 at 6:59 am
Demonstration code as promised:
IF OBJECT_ID(N'dbo.Employee', N'U')
IS NOT NULL
DROP TABLE...
May 16, 2010 at 6:51 am
Jeff Moden (5/15/2010)
May 16, 2010 at 6:32 am
Jeff Moden (5/15/2010)
Paul's code didn't convert the Adjacency List to the Hierarchical Path that HierarchyID needs.
Still not quite sure why I'm doing this, but anyhow, here's the conversion code:
DECLARE @UserRegistration
TABLE...
May 16, 2010 at 6:15 am
8kb (5/15/2010)
May 16, 2010 at 2:01 am
mahbub422 (5/15/2010)
Thanks Paul for your suggestion. I have removed.
Thanks. For the benefit of others, it was a cool-looking report.
May 15, 2010 at 12:19 pm
Jeff Moden (5/15/2010)
May 15, 2010 at 12:18 pm
Mahbub,
That's really good news - and full credit to Peter for the time he spent on this too.
It's great to see the reports, but there is some pretty sensitive personal...
May 15, 2010 at 11:25 am
8kb (5/12/2010)
May 15, 2010 at 11:20 am
I'm not saying any of this is great design, but you can do this sort of thing directly using LIKE and PATINDEX.
The following code snippet demonstrates the general idea:
DECLARE @Lookup
TABLE...
May 15, 2010 at 9:38 am
Viewing 15 posts - 3,406 through 3,420 (of 8,416 total)