Viewing 15 posts - 47,041 through 47,055 (of 59,102 total)
If it's on the GUI side that you want to do this, then I'm not sure.
If it's on the SQL Server side of the house, a trip to Books Online...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 6:22 am
Again... Lookup SQL Server Certification on the Microsoft Website...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 6:20 am
I'm getting ready to go to work, so I can't solve it all right this instant.
I do have a question, though... are all of these values for a single column...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 6:18 am
Peso (11/24/2008)
Jeff's simplified.SELECT DATEADD(wk,DATEDIFF(wk, 0, getdate()), 6)
However when run on a sunday, the code returns following sunday.
My suggestion returns same sunday if run on a sunday.
Heh.. yeah... I did...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 6:11 am
yuvalpe (11/24/2008)
This topic was cover complitly by Itzik Ben-Gan years ago
So? There's lot's of folks that don't even know who he is, never mind what a Numbers or Tally...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 6:06 am
jacroberts (11/24/2008)
e.g.:
CREATE FUNCTION [dbo].[Nums]
(
@StartNum int,
@EndNum int
)
RETURNS...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 6:04 am
It was very difficult to maintain any semblance of professionalism on that one. Some of these folks need to clean the pipe they're smoking. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 6:00 am
Just an FYI... the source of the CTE in your article is by a fellow called Itzik Ben-Gan and can be found at the bottom of page 255 in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 2:20 am
Oh lordy... I can see it now... some DBA decided that (s)he was gonna cleanup "unused" SPIDs and wrote some proc to kill all SPID's that don't have "Runnable" as...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 12:57 am
Gosh... I don't know, but I'd like to know.
Anybody got any ideas on this one?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 12:53 am
Why can't you just use BCP for this?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 12:52 am
First, I think you posted this on the wrong forum.
Second, that type of error normally means that there's something wrong with either some slow code that needs to be reworked...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 12:45 am
So.... what happens if a step is reopened more than twice? Does it still work? And, heh... you've just gotta know that will be the next request because...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 12:28 am
Do you have any idea how rude you sound? "please send it immediately". Sounds more like an arrogant command than a friendly request. Learn some etiquette... IMMEDIATELY!...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 12:22 am
If that SELECT is returning the values you want, then...
SELECT obj.name Table_Name, sycol.name Column_Name,Len(sycol.name) 'Data Length', t.name DataType, sycol.Length
INTO #yourtemptable
FROM sysobjects obj
INNER JOIN syscolumns sycol ON (obj.id=sycol.id and obj.type='U'...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2008 at 12:16 am
Viewing 15 posts - 47,041 through 47,055 (of 59,102 total)