Viewing 15 posts - 53,581 through 53,595 (of 59,072 total)
Replace the 1234567890 with your INT column or formula. Could turn this into a function. Note that it's generally a bad idea to do this type of formatting...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 10:23 pm
Oh, crud... you're right... I just loaded 2k5 over the weekend and verified what you say to be true... it's not in 2k5... reportedly it was and I took someone's...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 5:35 pm
It will be a valuable experience... perhaps not the way most think, but valuable nevertheless.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 4:18 pm
And then, anyone who is touting the label of "Senior Software Engineer" needs to be able to do some pretty complex stuff right off the top of your head (like...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 4:13 pm
Now in case of FASTFIRSTROW..I am trying to achieve a fast response time
It's far better to write good fast SQL with the proper indexes instead of trying to trick...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 2:39 pm
Heh... they even made the same mistake that caused the y2k crisis...
Best T-Shirt I ever saw on the subject of "SQL Darwin Awards" was...
[font="Courier New"] SELECT *
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 2:30 pm
[font="Courier New"]SET @Cmd = 'DEL \\dt-sc2\shares\Data.txt'
EXEC Master.dbo.xp_CmdShell @Cmd[/font]
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 2:19 pm
Yes... it does NOT affect performance of what SQL Server does for page allocation...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 2:02 pm
Run the following: EXECUTE master.dbo.xp_cmdshell 'SET'
and then run SET from the command prompt. (make sure you are logged in as the account that the agent is running as). For me...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 1:47 pm
Ummm... actually, Scope_IDENTITY() is exactly what you want.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 1:41 pm
Crud... missed your reference where you explained it before. Sorry, John.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 7:49 am
A whole lot more subtle than the obvious candidates for the "SQL Darwin Award" that you guys have shown, is my favorite clock-cyle waster/index defeater...
[font="Courier New"]AND ISNULL(somecolumn,' ') <> '...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 7:17 am
Any alternate suggestions or anything else that i need to consider ?
Yes... don't forget that SQL_Variant can take up to 8016 bytes... if you have more than one SQL_Variant column...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 7:03 am
Great minds think alike... and, frequently, at the same time. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 6:57 am
Linda Johanning (12/13/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2007 at 6:45 am
Viewing 15 posts - 53,581 through 53,595 (of 59,072 total)