Viewing 15 posts - 49,516 through 49,530 (of 59,102 total)
Oh my... wow... WOW! HOLY MACKERAL! :w00t::blush:
Ok, I've gotta tell you... It's all because of the good folks on this forum, both current and in the past. I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2008 at 12:12 pm
Obviously, you'll need to fix the error...
Part of the whole problem on things like this is the condition of the data. For example, I downloaded the provider list for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2008 at 6:07 am
gaurava16fc (7/2/2008)
(
@strInput nvarchar(50)
)
Returns DECIMAL(18,0)
AS
BEGIN
DECLARE @iCtr INT
DECLARE @AscVal INT
DECLARE @NumVal NVARCHAR(100)
SET @iCtr = 1
SET @NumVal = ''
WHILE @iCtr <= Len(@strInput)
BEGIN
SET @AscVal = Ascii(substring(@strInput,@iCtr,1))
IF (@AscVal >= 48) and (@AscVal <=...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2008 at 5:59 am
You made a BCP FORMAT file like I suggested, eh?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 4:23 pm
d_sysuk (7/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 4:13 pm
bitbucket (7/1/2008)
Except that that is NOT what was wanted. What was wanted was:
Eliminate One row from each distinct Group.
With the Following restrictions:
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 10:55 am
Heh... crack was showin'... :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 7:47 am
GSquared (6/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 7:44 am
Heh... this all reminds me of another of my favorite 4 letter acronyms... [font="Arial Black"]RTFS[/font]!!!!! 😀
Yeah... I'm out'a here, too! Nice job to the folks that actually read...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 7:31 am
Heck... even that "depends". The bottom line is that you don't really know for any particular circumstance until you write some POP code and test it.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 6:37 am
You guys are missing the point of this particular exercise... despite the name of the post, this is NOT about the elimination of duplicates. Here's what the op wanted...
1....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 6:35 am
It ALL depends... table scans are not always a bad thing... index usage is not always a good thing.
The real problem is not going to be simple index usage... it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 6:30 am
You can say it easier than even that...
Remove one of every type of row that can be uniquely identified even if there is only one.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 6:03 am
Ummm.... Use DTS to import just one of the Excel sheets... the one with the column headers. That will define a table fairly nicely. Then, truncate the table...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 5:59 am
Ummmm... before you go asking another question... how about letting us know if the fix for the previous question worked...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2008 at 2:02 am
Viewing 15 posts - 49,516 through 49,530 (of 59,102 total)