Viewing 15 posts - 53,176 through 53,190 (of 59,072 total)
AlexT (1/2/2008)
Nice article.Just another way to do this in sql 2005
with h(SomeID) as (SELECT DISTINCT SomeID from dbo.TestData )
select h.SomeID, dbo.fnConcatTest(h.SomeID) from h
Cool... another bullet for the gunbelt....
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:04 pm
JJ B (1/2/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:02 pm
Michael Skinner (1/2/2008)
What drives me insane about issues like this one (and I have had to create comma delimited files far too often through SQL) is that...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 5:49 pm
sushila (1/2/2008)
What an absolutely well-written and informative article - I totally agree with the earlier post that remarked on this being a great way to start the new year. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 5:45 pm
Correct... and thanks for the feedback!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 7:51 am
Heh... thanks for the feedback, Donald. I'm right there with ya on the 10 tries. 😀
Like Colin was kind enough to point out, if folks think they can...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 7:48 am
Perfect... thanks, Gail.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 7:24 am
As long as database owner is a sysadmin all objects created by database owner will automatically be owned by dbo.
Now, there's a decent tip... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 7:20 am
It just checks that your values are in the format of nnnn-nnnnn and the first 4 are a viable year. Please see "Like comparisons, Pattern Matching in Search Conditions"...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 7:15 am
First, recurrsion is nothing more than RBAR on steriods, only it's a bit more difficult to troubleshoot if something goes wrong. 😛
Second, this is an SQL Server 2000 forum...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:59 am
No, no... no need to convert to a proc... when your code detects that something is wrong, just do a SELECT 1/0 and, trust me, an error will be raised...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:47 am
What other values would you like to convert?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:43 am
You bet... easiest thing to see what I'm talking about is to simply run the code and compare to what's in the #yourtable to the results...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:41 am
Well, kind'a... haven't taken the time to CTE this puppy, yet... if you do, would you mind sharing it, please? Thanks...
The "key" is that at least one of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:18 am
Thanks for the feedback, Martin. Yeah, I have a grand love for such 3rd party shenanigan's myself... my favorite is loading data from a table into a Temp Table,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 4:48 am
Viewing 15 posts - 53,176 through 53,190 (of 59,072 total)