Viewing 15 posts - 45,916 through 45,930 (of 59,101 total)
dmc (1/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 10:18 am
dmc (1/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 9:50 am
dmc (1/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 9:22 am
Jeff Moden (1/15/2009)
But, aren't you executing the column merge code once for each "employee"?
Never mind... not enough coffee... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 9:02 am
That's pretty much like what Seth has and both are pretty much the way I'd do it...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 9:01 am
latingntlman (1/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:54 am
dmc (1/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:44 am
Ramesh (1/15/2009)
Here is that query
SELECT *
FROM (
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:43 am
GilaMonster (1/15/2009)
Jeff Moden (1/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:38 am
Yep... don't split it at all... if the format of the file is stable and a couple of other nuances, use Bulk Insert. In SQL Server 2000, I used...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:34 am
Terence Keys (1/14/2009)
Thanks for the help!
So, what did your final code end up looking like?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:29 am
jabba (1/15/2009)
If I could persuade them to drop the requirement to house the servers in different locations and rely on the inhouse generator, would clustering fufill the other points?
Ummm... no.......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:27 am
Oliver (1/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:22 am
I disagree with most of the thoughts on this thread... I've used both and, for what I classify as "casual users" and ease of use, I think that SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:19 am
Let me rephrase my question a bit... add on to it, really...
How are you going to identify the columns that you want to check or are you asking for code...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2009 at 8:07 am
Viewing 15 posts - 45,916 through 45,930 (of 59,101 total)