Viewing 15 posts - 55,861 through 55,875 (of 59,098 total)
Heh... see what happens when you provide just the right amount of data and a table definition to go along with a good description ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 7:50 pm
Just about perfect... I'll be back in a few...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 5:55 pm
Look at it this way... they're all flaming one thread and leaving the others alone ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 5:39 pm
That's referred to as a "sequence table" and it one of the things that was suggested. But, you must be VERY careful how you do the update to it or...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 5:37 pm
Can you get them to reverse the process? Seems to me that the data table should be there completely befor the trigger table that says it is.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 5:34 pm
You're welcome...
Not sure what it is but being called "dear" instead of "Jeff" kinda bugs me, especially if you're a guy... must be a language barrier thing 
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 7:42 am
So... post the actual name of the column that identifies individuals along with a bit of sample data for those, the actual names of the other two columns, the datatypes...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 7:38 am
<Psssst! Bulk Insert...>
BULK INSERT dbname.dbowner.tablename
FROM '\\machinename\path\Sample.csv'
WITH
(
FIELDTERMINATOR = ',',
ROWTERMINATOR = '\n',
FIRSTROW = 2,
ROWS_PER_BATCH = 50000
)
No need for format files or anything else...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 7:33 am
PLEASE, don't double post...
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=380596
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 7:10 am
Lookup "Expanding Hierarchies" in Books Online.
And, if you search this site for "Hierarchy", you'll also find some pretty decent procs/functions for this. If you come across any that use recurrsion,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 7:08 am
Heh... I think lots of folks, including me, have made that error at least once ![]()
Just a bit of an edge for performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 7:02 am
You do NOT need a cursor to do this... but I need a bit more information...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 6:58 am
Dave,
If you want to do this from an app or even TSQL itself, see the following script for how to do it... and, yes, it is a registry change...
http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=1854
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 6:50 am
I guess I just don't understand why you are using OpenRowSet when Bulk Insert will load the file in about two heart beats. You wanna try that, instead? Lemme know...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 10:46 pm
Could it be that the sender of the files is sending the trigger file before the data file is received in total?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 8:34 pm
Viewing 15 posts - 55,861 through 55,875 (of 59,098 total)