Viewing 15 posts - 44,911 through 44,925 (of 59,095 total)
I'd definitely suggest you read the article that Bit Bucket pointed you to, but not until you understand how a Tally table actually replaces a loop in situations like this....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 8:31 pm
sp_cursorfetch isn't something the 3rd party vendor wrote into their code... it's what get's used as a result of their code (or anyone's code).
They key here is, and I...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 8:12 pm
Double post folks... no answers here, please. Goto the following URL instead...
http://www.sqlservercentral.com/Forums/Topic666037-149-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 8:02 pm
See the splitter example in the following article...
http://www.sqlservercentral.com/articles/TSQL/62867/
Also... if guaranteed to only have 3 parts, lookup PARSENAME in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 8:01 pm
And, yes... I wish there was a Phd for those who pretty much specialize in the code.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 7:53 pm
That works just fine, but there's only 100,000 numbers available that way. This type of serialization is really bad just because of that... even if the numeric sequence is...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 7:51 pm
jminette (2/27/2009)
Ok, there's not one....but if there were I think I'd like to be a SQL Proctologist. :hehe:Hey, it's Friday...this is the best I got.
Heh... Proctologist... reminds me of a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 7:45 pm
Lookup GRANT and ROLES in Books Online... it comes free with SQL Server.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 7:42 pm
Because the query produces a downline and you're trying to calculate the upline targets, you will need a separate correlated subquery UPDATE (maybe a CROSS-APPLY but haven't tried it) to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:42 pm
Bob Hovious (2/27/2009)
My war story is that our development group used to have a guy whose...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:30 pm
Bob Hovious (2/26/2009)
files that have been mangled by people who don't have the faintest clue what they're doing
I just have to ask, how much of your coding efforts are spent...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:22 pm
Bruce W Cassidy (2/26/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:19 pm
You're welcome, Tim... thanks for taking the time to post the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:10 pm
Mike, there's a whole lot of things that can make such a large insert slow. For example, a clustered index that's not quite on the right columns for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:08 pm
Grant Fritchey (2/27/2009)
I still think partitioning the data would be a better approach rather...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 6:00 pm
Viewing 15 posts - 44,911 through 44,925 (of 59,095 total)