Viewing 15 posts - 44,596 through 44,610 (of 59,095 total)
Heh... stupid me... of course it's set to 9 or you'd have gotten a message about the CTE. Sorry.
Can you post your final code? I just wanna make...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 8:59 pm
siddartha pal (3/12/2009)
I am not able to complie the function because of Varchar(max) for @string parameter.
Siddartha,
Check the compatibility level of the database... if it's set to "8", then the database...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 8:28 pm
WebTechie38 (3/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 8:13 pm
foxjazz (3/14/2009)
Why not have t-sql be capable of merging with other languages by preference?
Heh... I told you that it actually is, before... you can write all your stored procedures in...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 8:05 pm
Heh... definitely not. English only here. Of course, if I need something done in Germany, I get a translator.
Same goes with code... GUI programmers shouldn't have...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 8:01 pm
Goldie Graber (3/14/2009)
Jeff Moden (3/14/2009)
Hi Goldie...
Not sure I can help but it would make it easier to try if you attached a file that has an example HTML that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 7:43 pm
RBarryYoung (3/14/2009)
foxjazz (3/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 7:39 pm
foxjazz (3/14/2009)
Simply because cursors...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 7:23 pm
foxjazz (3/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 7:06 pm
Ahh... got it. Thanks. Glad you were able to get them over the bad question. You could, however, use dynamic SQL to create a cross-tab should that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 2:37 pm
Bob Hovious (3/14/2009)
1. Some code is missing from your first example. But I presume you were going to cross join syscolumns to itself. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 2:31 pm
BWAA-HAA!!! The real irony you speak of is that it obviously wasn't read by those that needed it the most! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 2:22 pm
Paul Hutchings (3/14/2009)
the upgrade is mainly to get current vs. because our performance requirements/environment has changed.
What I've found in the past is that such upgrades are expensive and are usually...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 1:36 pm
Heh... the first step towards troubleshooting any code is to make it readable... when I do that to your code example, a certain problem with the code sticks out like...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 1:16 pm
foxjazz (3/13/2009)
select name from mynametable where changedate > @yesterdayfetch from @sel into @name
while (@@fetch_status = 0)
begin
insert into nameother (name,changeddate) values (@name,getdate())
end
Do this without a cursor!
Heh... rant complete... regard all further...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 12:48 pm
Viewing 15 posts - 44,596 through 44,610 (of 59,095 total)