Viewing 15 posts - 51,481 through 51,495 (of 59,091 total)
Here's a couple of facts for you...
Creating a temp table that holds 750000 rows of primary keys of rows to be deleted takes 2.1 seconds using SELECT/INTO.
Adding a primary key...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2008 at 6:08 am
blahknow (3/25/2008)
My stored procedure accepts 2 parameters: names, number of names like this: (name1, name2, name3,3) Problem is: the number of names changes each time i want to run...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2008 at 4:59 am
Mahesh Bote (3/28/2008)
Better you go for XML.
A well formed UDF or open code that uses a Tally table to do the split will blow the doors off of any form...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2008 at 4:53 am
If it's for a join, as you say... why are you concerned with converting it back to a number? Just join to it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2008 at 4:42 am
Rather than testing your code on 300 million rows, here's some code that generates a million rows of test data. This particular code also has what I call a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 6:36 pm
Harveysburger (3/27/2008)
gotta say although it's not the most popular answer your arguments are strong
thanks for the input, I will meditate on that for a while and see...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 6:07 pm
John Rowan (3/27/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 5:54 pm
erdem (2/28/2008)
How can I prevent duplicate values on a row without using Primary keys?
For example you can easily see that Sales price2 and sales price3 are same.How can I...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 8:14 am
Madhu... a little feedback on what you end up doing would be much appreciated.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 8:01 am
Glad you got it resolved... what did you do?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 7:59 am
Sergei Zarembo (3/26/2008)
i agree in this simple replace it would be an overkill. But replace pattern can change by the minute. Wouldn't it be more convenient to have one [or...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 7:51 am
Heh... no, you're right, Matt. I was just anticipating the next possible question (I should probably get out of the habit) which usually turns up as either "How would...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 7:45 am
The popular answer on this and many of the other threads is scenario 3 and some for scenario 2. Just my humble opinion, but I think they might all...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2008 at 7:07 am
Todd Engen (3/26/2008)
Try changing "DROP" to "DELETE", or set a WHERE clause with EventClass = 47 for Object : Deleted events.
Opening the traces in Profiler will resolve the EventClass to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 12:51 pm
See? Now, I get that... thanks, Wayne. Why couldn't someone say something like that instead of thinking that I was trying to give them an eWedgie? :P...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 12:33 pm
Viewing 15 posts - 51,481 through 51,495 (of 59,091 total)