Viewing 15 posts - 49,291 through 49,305 (of 59,102 total)
That constitutes a "Triangular Join" in a correlated subquery... please read the following as to why those can be so very bad...
http://www.sqlservercentral.com/articles/T-SQL/61539/
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2008 at 6:44 pm
You bet...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2008 at 6:42 pm
gan (7/9/2008)
then you meant ident_current('table name') can be used as scope_identity ?
Absolutely not...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2008 at 6:24 pm
Aw rats... the fly in the ointment is that the ID's must already be in the correct hierarchical order in order to display in the correct order... Gotta add...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 9:17 pm
The neat thing about that code is that it allows for multiple top levels if you need them... thanks again.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 9:10 pm
Nicely done! Thanks! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 9:06 pm
terry.jago (7/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 9:03 pm
Martin,
I also have to say that this is usually a very bad thing to do in SQL Server... most
will tell you that if you need to do it for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 8:51 pm
Leo Mepham (7/9/2008)
Any CLR experts want to offer help?
No... but you don't need any CLR experts to do this either... Leo... I'm not picking on you but
I have a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 8:28 pm
MentalWhiteNoise (7/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 7:50 pm
This will help... details are in the comments
[font="Courier New"]--===== How to force messages to screen on long running queries
--=========================================================================
-- What normally happens is...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 7:38 pm
Make your life easy... import the date#time into a single column and replace the # sign with a space in the process of converting it to a real date/time.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 7:34 pm
Drat... I forgot you said you had a header row... you'll need to add a FIRSTROW = 2 to that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 6:50 pm
Not quite... IDENT_CURRENT('table_name') takes a table name as it's operand and has no scope other than the table itself... trigger shouldn't affect it like it can @@IDENTITY.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 6:39 pm
Here's another way using one of the "new" functions in SQL Server 2005 and a Classic Cross Tab... this example would require two Pivot clauses and a join or two,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 6:35 pm
Viewing 15 posts - 49,291 through 49,305 (of 59,102 total)