Viewing 15 posts - 58,921 through 58,935 (of 59,075 total)
You're welcome and thanks for the feed back.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2004 at 8:21 am
We ran into a similar problem at work...
You have an IS NULL in the WHERE clause and while that is not in itself a problem, you've probably run into a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2004 at 3:50 am
I ran into a similar problem with a rather lengthy query and it became a real pain. I originally used IF logic but it required that the same lengthy query...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2004 at 2:59 am
Brian,
Really nice job on the "Stored Procedures and Caching" article. Looks like a few other folks share my sentiment. Definitely above the norm of what I've come to expect from...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2004 at 8:33 pm
If you format the "preview" table (also known as a "staging table") correctly, BCP will catch the kinds of errors you mentioned. Dates should always go into a DateTime data-type column. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2004 at 12:08 am
I had some very good luck using a CASE statement in a WHERE clause for just this purpose. Try something like this...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 16, 2004 at 11:54 pm
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
Viewing 15 posts - 58,921 through 58,935 (of 59,075 total)