Viewing 15 posts - 53,656 through 53,670 (of 59,089 total)
Sandy (12/10/2007)
Hey Karthikeyan,Just have a Look on this Post.
http://www.sqlservercentral.com/articles/T-SQL/61539/
By Jeff Moden, 2007/12/06
Hope, you can get idea from this.
Cheers!
Sandy.
Ummm... thanks Sandy, but that whole article is about how bad triangular...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2007 at 12:08 am
I'll show how, you explain why...
DECLARE @Str CHAR(6)
SET @Str = 'ABCDEF'
SELECT LEFT(@Str,Number)
FROM Master.dbo.spt_Values
WHERE Type = 'P'
AND Number BETWEEN 1 AND...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2007 at 12:05 am
Proof! Oh heck yeah... I'm working on a bunch of proof right now! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 11:56 pm
GilaMonster (12/9/2007)
There are things that can be...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 11:52 pm
Thanks... I'll give 'er a whirl. Funny how they've so radically changed the terminology...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 11:48 pm
Think about it... 😉 See page 3 where they have the following code...
INSERT INTO [dbo].[Address_Temp] ( [FirstName], [LastName], [Address], [City], [State], [ZIP] )
SELECT [FirstName], [LastName], [Address], [City], [State], [ZIP]
FROM...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 10:57 pm
I believe the following will do it...
EXEC Master.dbo.xp_LoginConfig 'Default Domain'
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 10:36 pm
Hipp is smart... just like Gillette was... "Give away the razor, sell the blades." 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 10:25 pm
I'm just trying to point out that the industry has a particular definition in play for "set-based programming", and this is different than what I was getting from the article....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 10:19 pm
I'm sure I'll get a bunch of hooey from the CLR zealots on this but, with the possible exception of some decent RegEx CLR's written by Matt Miller, I've not...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 5:10 pm
so I'm not completely sold on the PIVOT operator yet. I think it looks kind of clunky. Then again, we usually say that when we come across something new. Perhaps...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 5:07 pm
Heh... only if Set A has an alias of Set B 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 9:34 am
More info...
You CAN do a dupe check using an after trigger... Again, ITS THE WRONG THING TO DO!!!! But it will help you "pass" if your instructor insists...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 9:28 am
The problem with such a trigger is that you've created an "After" trigger... these types of triggers fire "After" the data has already been inserted. In other words, the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 9:24 am
Agreed... Bit values are, in fact, "tri-state"... off, on, and "don't know" and, depending on your requirements, that may or may not be important. For example, in a "testing"...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2007 at 8:54 am
Viewing 15 posts - 53,656 through 53,670 (of 59,089 total)