Viewing 15 posts - 42,886 through 42,900 (of 59,098 total)
Wesley Norton (7/20/2009)
the sum of the 4 character code should be the same.
Ummm... not necessarily...
'ABBC' = 'AABD'
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 10:29 pm
Heh... couldn't wait. Since this is SQL Server 2000, there's no "programmable" TOP. So, I cheated to avoid the dynamic SQL (not that I'm against using dynamic SQL......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 8:47 pm
Hey Chris,
Thanks for posting your code. Lot's of folks just take the money and run. I'd like to return the favor in the form of another enhancement or...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 7:51 pm
Heh... no... I'm saying you're too late... no mind left. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 6:48 pm
Thanks... I appreciate that. Here's the solution... explanation is in the code comments.
--===== This is your original test table with just a bit of reformatting.
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 6:21 pm
touchmeknot123 (7/20/2009)
Hi Phil,Thanks for the reply.
I figured it out.
I had to use merge join task and implement the same.
How were you able to split the street name from the city...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 5:27 pm
. (7/20/2009)
Is the start date you entered considered to be day 1 of week 1? In other words, if you enter a start date which is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 5:14 pm
Ah... Jedi mind games... I see now... "other thread". 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 5:12 pm
Looks like the OP posted as I was writing my reply. And, is my mind playing tricks on me or are the INSERTs that you have in the quote...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 5:07 pm
Steve Jones - Editor (7/19/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 11:15 am
If you do that, just remember to recreate indexes, verify FK's, establish the PK, setup constraints, copy any triggers, and rebuild any views that reference the table. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 10:14 am
Unless there were some "run away" query that blew TempDB to an insane size, don't shrink TempDB... it's just gonna grow again.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 9:21 am
I was just wondering if you are able to change the tables so that you don't have a CSV column at all. But, if you're happy, I'm happy. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 9:16 am
That's the one, Lynn... it has a RowCount for each object ID and, I believe, that row count is always up to snuff.
If you read BOL about the system...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 9:14 am
Just to be sure... the "Magic" isn't in the CTE... it's in the Tally table and can be used in SQL Server 2000 just as effectively.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 6:36 am
Viewing 15 posts - 42,886 through 42,900 (of 59,098 total)