Viewing 15 posts - 37,606 through 37,620 (of 59,098 total)
Eralper (7/19/2010)
Hello,Easiest solution is using DATEPART function
select DATEPART(WEEK,GETDATE())If that is not useful for your requirements, you can also think of to create date table in SQL Server
It depends. What...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 4:56 pm
sunny.tjk (7/19/2010)
nothing happens when I run this in command prompt:
bcp CRIS_IST.dbo.Blaze69Repository in blazerepo.cris.bcp -T -c -SLUWZD5584 -Uroger -Proger
the table isn't getting loaded with the data which is in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 4:52 pm
Never mind...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 4:50 pm
CirquedeSQLeil (7/19/2010)
Trey Staker (7/19/2010)
Alvin Ramard (7/19/2010)
mtillman-921105 (7/19/2010)
I'm with Alvin! Yes, come on over here to Memphis and we'll show you what terrific BBQ's all about. π
Actually, if you...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 4:46 pm
Alvin Ramard (7/19/2010)
mtillman-921105 (7/19/2010)
I'm with Alvin! Yes, come on over here to Memphis and we'll show you what terrific BBQ's all about. π
Actually, if you come to Memphis...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 4:20 pm
kjc-1057161 (7/19/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 4:16 pm
Eugene Elutin (7/19/2010)
Jeff Moden (7/15/2010)
Eugene Elutin (7/14/2010)
Julie Breutzmann (7/14/2010)
...What would be an efficient way to code this?
...
If you need high-performance heavy string manipulation functions write them as CLR functions in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 4:08 pm
R.P.Rozema (7/19/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 4:00 pm
Hugo Kornelis (7/19/2010)
Jeff Moden (7/19/2010)
Hugo,The gain is that there is nothing you can naturally order by that will give you the correct original order. π
Huh?
USE AdventureWorks2008;
SELECT TerritoryID, GROUPING(TerritoryID),
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 3:53 pm
mike mcneer (7/19/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 3:42 pm
Hugo,
The gain is that there is nothing you can naturally order by that will give you the correct original order. π And stop playing the "gotcha back" tricks... can...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2010 at 6:34 am
mithun.gite-1086228 (7/18/2010)
This is not a actually a SQL job but its just similar to that , at scheduled time bunch of sps will start executing pulling data...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2010 at 12:58 pm
gah (7/18/2010)
also a sincere thanks to Jeff Modem for his article
It's actually spelled "Moden" but I'll take the compliment. π Thanks, Graham.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2010 at 12:54 pm
Sagar Sawant (7/17/2010)
Why you are using cursors? it's degrade the performance of sql query and also consuming memory..
Use while loop instead of cursor. [font="Arial Black"]You can see the dramatic performance[/font]......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2010 at 12:44 pm
Do the changes you're making make some data wider than the column that it was intended for?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2010 at 12:35 pm
Viewing 15 posts - 37,606 through 37,620 (of 59,098 total)