Viewing 15 posts - 49,306 through 49,320 (of 59,099 total)
Sure... here's a modified example from BOL...
BULK INSERT AdventureWorks.Sales.SalesOrderDetail
FROM 'f:\orders\lineitem.tbl'
WITH
(
FIELDTERMINATOR =',',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 5:04 pm
Lynn Pettis (7/9/2008)
PORK CHOPS!!!!! (lol) :w00t:Couldn't resist (well, I could have, but didn't want too!)
😎
Now THAT's entertainment! 😛 Haven't tried it yet, but I understand that Pork...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 4:45 pm
GSquared (7/9/2008)
Relational Theory is a wonderful thing, but every now and again (not more than ten or fifteen times per nanosecond), it runs into this...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 4:43 pm
Tom Hamilton (7/9/2008)
I was researching cross-tab like products and your postings come as one who knows how.
I need to produce a of Cases and comma-separated list of Jurisdictions, like...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 4:39 pm
Ummmm.... I use T-SQL and CmdShell... Once in a while, I may throw a little VBS into the mix... but everything else I do when I do DBA work is...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 4:17 pm
Dugi (7/9/2008)
So if you compare one MVP(SQL - and we have some infos how to become MVP) with one Software Engineer (SQL or Oracle Database) Graduate Master or...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 2:11 pm
webrunner (7/9/2008)
In your editorial you write, "I'm not sure why I was picked."
That's very humble. But as someone who has benefited from the SQL expertise that you and many others...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 2:06 pm
I just tell it to ignore at least 1 error...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 10:19 am
Looks ok to me... don't forget... you can use MAX in place of SUM for things that aren't numeric in nature provided they're unique.
And, thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 10:18 am
Angelindiego (7/9/2008)
Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 10:15 am
Christopher Stobbs (7/9/2008)
HI Jeff,Sorry you lost me on the column name there?
Sorry... I meant "SysComments"... not "SysColumns"... I've repaired the post where I made that error.
The key is that the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 10:13 am
It's ok, really... as suggested, it's a really great study in the human element. Some post with out reading, some argue they read, some read and still don't understand.
And,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 10:07 am
Gosh... this is an "adjacency" hierarchy on steroids... my feeling is that the tables are not correctly designed... there should be a table where ALL the managers and employees are...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 10:02 am
A sports MVP knows how to get one... serve the team and go the extra mile. Should be no different for SQL Server or any of the other categories...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 9:54 am
The only problem with that is if the function name sits on the "border" between two code segments in SysComments... you could miss a dependency that way. Works 99%...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2008 at 9:42 am
Viewing 15 posts - 49,306 through 49,320 (of 59,099 total)