Viewing 15 posts - 53,311 through 53,325 (of 59,098 total)
This whole thread and the original concept isn't something I would even consider doing... First, there may be a GUI out there that you don't know about that requires those...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 1:23 pm
No, it's not possible using BULK INSERT.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 1:13 pm
raym (12/28/2007)
How can I speed this up ?
Ray, the title of your post hit the nail on the head... get rid of the cursors, plain and simple. I'm not...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 1:10 pm
... and PLEASE DON'T DOUBLE POST!!!!
http://www.sqlservercentral.com/Forums/Topic436570-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 1:05 pm
... and PLEASE DON'T DOUBLE POST!!!!
http://www.sqlservercentral.com/Forums/Topic436572-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 1:04 pm
The REAL question would be, WHY are you using a cursor for this? You should be able to do this in a setbased fashion...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 1:02 pm
have about 2,00,00,000 records in a table which are being queried.
More over I have 2 more tables of same specs mentioned above.
Queries are taking lot of time. usually...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 12:58 pm
Heh... I got the answer right but the real answer isn't one of those listed. The question is "What must he worry about when using the @@FETCH_STATUS function in...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 12:52 pm
Ok... another way to do it would be to export the data to tab delimited files on some common file share and use BCP or BULK INSERT to import the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 12:41 pm
Dunno about most... I'd simply make linked servers and have a proc read the data in. Don't want to make a single view because if one of the servers...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 12:16 pm
Heh... a While loop... "Firehose" cursor would be just as good... take a look at the function I made in this thread... no explicit loop... no cursor... still basically hidden...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 12:10 pm
Hi Mark,
It's just the way this forum handles things when they repost an article... no updates were actually made.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 12:05 pm
Ion Freeman (12/28/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 12:02 pm
Except that you need to express dates in universal YYYYMMDD format to avoid conflict with local date settings
Heh... yeah... then there's that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 11:54 am
sorry Jeff I have to disagree, even if the clustered index is on an indentity column then the clustered index is actually the entire table, regardless of the index being...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2007 at 11:48 am
Viewing 15 posts - 53,311 through 53,325 (of 59,098 total)