Viewing 15 posts - 48,721 through 48,735 (of 59,099 total)
pleasehelpme (8/17/2008)
how do i extract data from yesterda using replication ? whgat about the format? and i want it to extract to txt files.
bASICally i...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2008 at 5:01 am
bluepaperbag (8/15/2008)
I BCP THE tables out + data. Now how can I do incremtanl extract like using changeDate = Yesterday?
Sorry... I didn't read all of the previous posts on this...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2008 at 4:57 am
Sure would like it if you'd post your benchmark code.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 9:24 pm
You might also be interested in some of the pitfalls of concatenation code...
http://www.sqlservercentral.com/articles/Test+Data/61572/
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 8:52 pm
Jeff Moden (8/17/2008)
It's odd that you must use a While loop instead of a cursor because a cursor uses a While loop! They both suck performance dry. 🙂
I'd...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 8:49 pm
karthikeyan (8/11/2008)
Create Procedure PrintReverse
(
@NumberToReverse int,
@NoOfTimesRepeat int
)
Select REPLICATE(@NumberToReverse,N)
from Tally,NUM
where N <= @NoOfTimesRepeat
and NumberValue = @NumberToReverse
UNION...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 8:48 pm
karthikeyan (8/11/2008)
why can't we use Tally or Number table ?
My approach :
Select REPLICATE('1',N),N
from Tally,NUM
where N <= 6
and NumberValue = 1
union all
select REP,N from (Select REPLICATE('1',N) as REP ,N
from Tally,NUM
where...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 8:46 pm
Hi Trevor...
It's odd that you must use a While loop instead of a cursor because a cursor uses a While loop! They both suck performance dry. 🙂
I'd recommend that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 8:32 pm
Niyala (8/11/2008)
I am getting the following deadlock message, but I could not figure out what the mentioned rate is.
DBSPI-3271.1: Deadlocks rate for object _Total (110.00/sec) too high (>=3.00/sec)
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 8:00 pm
... and it will require a change to your front end statement. You will need to select from the indexed view, instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 7:59 pm
You might be able to get a whole lot more retrieval speed if you created an Indexed View. Be warned that an indexed view can slow down inputs some.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 7:52 pm
I believe the first sheet of an Excel file can be referred to as Sheet1$ regardless of it's actual name.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 7:46 pm
pockeyfan (8/14/2008)
Thanks for your suggestion!I'm new to SQL and SP, will read the article to see whether I could apply it in my case...
Tally table won't do it, in this...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 7:40 pm
Lester Policarpio (8/13/2008)
And also please read the article...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 7:17 pm
Heck... I wouldn't even use the WHILE loop... it's RBAR. Most WHILE loop solutions are because someone doesn't know T-SQL well enough to come up with the proper set...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 7:05 pm
Viewing 15 posts - 48,721 through 48,735 (of 59,099 total)