Viewing 15 posts - 55,441 through 55,455 (of 59,072 total)
Actually, I believe this is what they call a "UNIX DATETIME" and it represents the number of milliseconds since the midnight on 01/01/1970. That also makes your 5/11/2007 date incorrect (unless...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 7:14 pm
DBCC SHOWCONTIG WITH TABLERESULTS
... will show you a whole lot more than just table names and rows.
If you get negative numbers for rows for some tables, you will need...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 7:01 pm
For Windows XP... TaskMgr.exe
That'll be one case of beer for asking questions outside the scope of SQL Server ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 6:56 pm
I believe this will do.
SET DATEFIRST 7 --Default for SQL Server
SELECT GETDATE()-DATEPART(dw,GETDATE())-2
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 6:50 pm
Like this...
SELECT CONVERT(CHAR(10),CAST('Mar 20 2007 3:57pm' AS DATETIME),111)
Of course, you would sub a couple of things to use against a table...
SELECT CONVERT(CHAR(10),CAST(yourdatestringcolumn AS DATETIME),111)
FROM yourtable
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 6:38 pm
That's actually a pretty good plan and I agree with that... nice to see someone to spend a little time up front to save wads later on.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 6:12 pm
Exactly... (and great explanation, by the way)
I know that and you know that and even some other folks know that. And, you're absolutely...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 6:05 pm
1. Doesn't matter if the header doesn't have the same number of delimiters. BCP is picky that way.
2. That's because of what I said before... you must delimit the end...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 5:33 pm
Man, I gotta remember to check for those... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 2:50 am
Not sure what you're calling a base table but the correct covering indexes will allow for full length table access using index seeks across all tables in a join. By...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2007 at 9:15 pm
Sorry Tomm... was just trying to lighten things up a bit. And, maybe I'm taking you the wrong way, but "flame war" about what? It takes two and I'm out...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2007 at 9:03 pm
Cool. Thanks for the feedback ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2007 at 6:26 pm
Heh... and it's true, too! ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2007 at 6:01 pm
First problem is the header record...
NEATCM|8.07.00|867850731
...which does not have the same number of delimiters as the other rows. Will always throw an error or cause a skip of the first...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2007 at 5:59 pm
Heh... I asked the same thing... and the answer is... crappola 3rd party software.
So, Mike, you never hardcode anything? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2007 at 5:50 pm
Viewing 15 posts - 55,441 through 55,455 (of 59,072 total)