Viewing 15 posts - 58,951 through 58,965 (of 59,099 total)
What are you using to do the export? If you are using BCP and use \" to enclose text fields in quotes in the format file, you should have no...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 8:22 pm
Adam is correct... basically, there is no way to store just the Month and Year in a datetime field. In fact, you cannot store a "formatted" date in a datetime...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 8:13 pm
BCP... read all about it in Books-on-Line then post back. I'll be happy to help once you are familiar with the terms and capabilities.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 8:04 pm
>The problem is that you have no idea what your are doing.
Apparently, Joe, you don't either because you provided no help to solve the problem... only caustic criticism on a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 7:55 pm
Yes, there is, kind of, but I don't know if it will work with a cursor (I avoid cursors) and it uses a temp table (no so bad if proper...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 7:04 pm
Yeah, you're right Frank... Not enough coffee ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 6:51 pm
Ben and Adam,
I ran into a problem with Adam's script returning all records instead of just the overlap records. I don't know if I did something wrong in changing the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 1:36 pm
Rather than messing around with dates and times, why not just add the three hours to the Pacific Time date (see DATEADD in code below)?
Also, you may have missed some...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 13, 2004 at 6:14 pm
Since you've explicity created the target table, you should not be using "SELECT/INTO"... use INSERT INTO/SELECT instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 13, 2004 at 6:00 pm
Your code is correct... my next step would be a SELECT COUNT(*) on the B table to make sure that I only had one row because it sounds like you...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 21, 2004 at 6:55 am
You forgot to post the error...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 21, 2004 at 6:49 am
CHAR(13) "Carriage Return" and possibly follow with CHAR(10) "Line Feed"
--Jeff Moden
Change is inevitable... Change for the better is not.
October 21, 2004 at 6:47 am
The datafile type would certainly not be "Native" if you are trying to input CSV.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2004 at 11:10 pm
Recompiles can be caused by having DDL like table creation or Select/Into buried between normal DML code. Define all tables and temp tables at the beginning of your code to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2004 at 11:05 pm
Here's how I do it... runs nasty fast too.
------ Finds the date without the time (Time=00:00:00.000)
SELECT DATEADD(dd,0,DATEDIFF(dd,0,GETDATE()))
AS DateOnly
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2004 at 11:00 pm
Viewing 15 posts - 58,951 through 58,965 (of 59,099 total)