Viewing 15 posts - 17,416 through 17,430 (of 59,067 total)
trboyden (6/20/2016)
SQL Server expects the date to be passed in as "2016-06-20 00:00:00"
That's not true at all. SQL Server will take a couple dozen date/time formats in stride with...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2016 at 7:00 pm
fizzleme (6/20/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2016 at 6:20 pm
Heh... why not cut out the middle man and just use T-SQL? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2016 at 5:29 pm
Any of you heavy hitters looking for a DBA (they need a good one) in San Diego? It's for one of our sister companies.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2016 at 5:26 pm
Eric M Russell (6/20/2016)
Jeff Moden (6/17/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2016 at 9:43 am
andymay-496937 (6/19/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2016 at 6:52 am
durga.palepu (6/18/2016)
create dbo.numbers(n int);
Load the numbers table using standard logic available.
Now to load the data into #insert table,
INSERT INTO #INSERT(txt)
SELECT txt
FROM #TEMP t
CROSS JOIN...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2016 at 2:11 pm
patrickmcginnis59 10839 (6/14/2016)
Jeff Moden (6/13/2016)
patrickmcginnis59 10839 (6/13/2016)
Jeff Moden (5/25/2016)
krypto69 (5/25/2016)
I have a pretty simple update statement:
UPDATE eligibility
SET primary_plan = 0
FROM temp_eligibility e
WHERE eligibility.eligibility_id = e.eligibility_id
This statement is updating around 7...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2016 at 2:07 pm
Steve Jones - SSC Editor (6/14/2016)
No need to answer to discuss. I rarely answer...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2016 at 1:45 pm
GSquared (6/15/2016)
Jeff Moden (6/15/2016)
GSquared (6/14/2016)
I just tested a Calendar table version against the UDFs defined here.Calendar table was consistently about 10X faster.
Can you post your test code?
Nope. The Post...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2016 at 1:36 pm
patrickmcginnis59 10839 (6/13/2016)
Jeff Moden (6/10/2016)
patrickmcginnis59 10839 (6/10/2016)
RonKyle (6/9/2016)
Besides, if you have to prepare for an interview, then you're not ready for the job.
Disagree. It never hurts to review the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2016 at 1:31 pm
Sergiy (6/17/2016)
My remark was about this statement from you:
the candidate probably shouldn't over-engineer the answer, especially in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2016 at 5:31 pm
djacob 65569 (6/17/2016)
THANK YOU!!! That helped me out immensely!
The question now is, do you understand how and why it works?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2016 at 9:14 am
As a bit of a sidebar and like anything else in SQL Server, saying something like the use of SELECT * always being bad is the wrong thing to say....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2016 at 8:55 am
Luis Cazares (6/17/2016)
Just curious on why you want to use CLR for this.
+1000
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2016 at 8:49 am
Viewing 15 posts - 17,416 through 17,430 (of 59,067 total)