Viewing 15 posts - 26,371 through 26,385 (of 59,099 total)
On the other hand, you could use xp_DirTree to find the file names and use BULK INSERT to load the file into a table using only T-SQL.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 9:35 pm
Prabhu, I strongly recommend that you read and heed the article at the first link in my signature line below for posts like this. You'll get a lot better...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 9:03 pm
Using PRINT for troubleshooting can be a real PITA and the output sometimes doesn't show up until the end of the run instead of as the procedure run unfolds.
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 8:49 pm
dwain.c (7/24/2013)[hrGee whiz! And here I was thinking my STUFF solution was pretty clever.
Nice one Jeff!
Thanks, Dwain. Indeed the STUFF solution is clever. I went for the super...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 8:41 pm
This is a duplicate thread. Let's shift over to the other thread where there are more posts. No more posts on this thread, please. It's just dividing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 8:36 pm
Peter. I've receive several emails from you. Have you received any of mine?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 8:29 pm
This is real easy but it doesn't sound like you've taken the first proper step. Contact company "A" and explain the situation. Then have company "A" inform company...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 8:27 pm
dwain.c (7/24/2013)
WITH Rates (rate) AS (
SELECT -100 UNION ALL SELECT NULL UNION ALL SELECT 0
UNION ALL...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 4:58 pm
L' Eomot Inversé (7/24/2013)
I haven't got enough hair to have bad hair days 🙂
BWAAA-HAAA!!! I've got tons of hair. I'm just not allowed to show it in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 9:35 am
Too funny! "Episode-By-Agonizing-Episode". 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 9:12 am
SwePeso (7/26/2013)
I am running on SQL Server 2012 and have tested every January 1st between 0001...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 8:29 am
I still have some testing to do but it appears that converting the DATEDIFF back to a DATETIME using DATEADD instead of mistakenly allowing DATEPART to do it fixes all...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2013 at 12:01 am
Well, I found the problem. The problem is with anything that has a base date of less than 0 or "1900-01-01". Any correct calculations before then are simply...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2013 at 11:14 pm
Ah... Missed it. You were talking about changing the BASE date of "0" to something else. I'll check on that, too1 Thanks again, Peter. I just...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2013 at 10:42 pm
SwePeso (7/24/2013)
The short story is that if the anchor date is a leapyear the algorithm fails. If...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2013 at 9:39 pm
Viewing 15 posts - 26,371 through 26,385 (of 59,099 total)