Viewing 15 posts - 40,816 through 40,830 (of 59,102 total)
I'm just having a hard time with your description... what you really mean is that if the ID is duplicated, it's considered to be a dupe and you don't care...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2009 at 9:12 am
Not a problem, Sam... that's what we're here for.
The graphic for SQL Server shows two result sets... one for 542 rows and one for one row. Unless you click...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2009 at 8:55 am
Heh... and I was thinking the other way around. Depending on what those batch files do, you may not have to use anything BUT SQL Server. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 9:11 pm
Steve Jones - Editor (12/5/2009)
However, the way you want to do this,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 9:10 pm
Heh... you know what, Matt? You're right. The extra 1 count came from the extra return on the one JPG. They are, in fact, identical. Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 9:06 pm
I split them to octets (using PARSENAME) stored as TINYINT and, like someone suggested, use a calculated column to reassemble them just to make life a little easier. The...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 6:24 pm
Yep... I agree with Pablo... you already have the metrics... make a spreadsheet and a graph from that and extend the line. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 6:18 pm
I made my first reference to your good article for a post today, Barry. If it keeps up, I may just have to add the link to my signature...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 6:14 pm
I'm not sure either. You might want to post the question on the Access forum of this site to get better visibility for your problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 6:10 pm
The JPG's won't help me or you. I suspect the devil is in the data. My recommendation is that you need to start with a row count check...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 6:05 pm
Taking Jason's fine code to the next level so that you don't have so much manual interaction (and, you could turn this into a DBA stored proc)...
DECLARE @sql VARCHAR(MAX)
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 12:41 pm
cos_ta393 (12/2/2009)
I am working with a dataset that has duplicate ID's due to unique records. The challenge is any number of column(s) can cause the uniqueness therefore there is...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 12:30 pm
No, sorry. I suspect there's a similar setting but don't know for sure. Might actually have to create a "report" for them which uses a TEXT(xxxx) definition for...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 11:00 am
marjan76 (12/4/2009)
Yes! I think I will set up my own database and practice, and show that I have hands-on experience 🙂
Do...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 10:40 am
Heh... wait just a minute, now. Let's ask the question... specifically, WHAT do those batch files do? You may not need to use anything in those batch files....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2009 at 10:36 am
Viewing 15 posts - 40,816 through 40,830 (of 59,102 total)