Viewing 15 posts - 32,716 through 32,730 (of 59,099 total)
Not yet, but I'm working on it. I've been working on an article about hierarchical structures and how to work them for a couple of months (there never seems...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 3:51 pm
Now, all I have to do is learn to spell it correctly and we'll be in complete agreement. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 2:59 pm
Sorry, Remi... Didn't see where you made such a differentiation but, now that you've said that, I made no differentiation... I hate it in all environments after using it in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 2:58 pm
Evil Kraig F (8/26/2011)
Stefan Krzywicki (8/26/2011)
Here's something everyone in IT should be aware ofYour decision making ability deteriorates as you make more decisions
Thanks for this Stefan, shared it around a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 2:49 pm
Sean Lange (8/26/2011)
True enough Jeff. Maybe it should be called LBAL (Level By Agonizing Level)? :w00t:
Heh... I was thinking the same thing and said, "Nah... " because it's actually fairly...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 2:43 pm
I guess it's what you "cut your teeth on". I have a lot to hate with implicit transactions especially when a 3rd party vendor provides some code.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 2:36 pm
Ah... apologies. I didn't see that you'd left the CTE out of your code.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 11:41 am
Michael Valentine Jones (8/26/2011)
If you see the wrong number or rows updated, you can just...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 11:39 am
In the meantime, the following article should help...
http://www.sqlservercentral.com/articles/T-SQL/72503/
As a side bar, the recusive CTE (or similar While loop) for doing this isn't totally RBAR because it will process [font="Arial Black"]all...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 11:33 am
Thanks for posting the "readily consumable" data on this. I'm not sure but I have an idea running around in the back of my mind that just might do...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 11:28 am
I've not been able to find the Microsoft document on this problem but we had precisely the same problem way back in SQL Server 2000. It turned out that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 10:55 am
Yep... Thanks for the clarification but I got that the first time. I'll fix you up tonight.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 10:44 am
weitzera (8/24/2011)
Select ActName, PName
FROM SalesDetailsCTE
GROUP BY ActName, PName
HAVING COUNT(DISTINCT DATEPART(yyyy, SoDate)) = 5
(this says for each customer and product, show me the customers that have...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 10:40 am
Grant Fritchey (8/26/2011)
Putting together an article on the most common backup errors (apart from not having one) and how to avoid them. I have four...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 9:58 am
tonyarp05 61903 (8/26/2011)
This doesn't work, I am getting an errorMsg 402, Level 16, State 1, Line 369
The data types varchar and varchar are incompatible in the modulo operator.
That means that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 26, 2011 at 7:37 am
Viewing 15 posts - 32,716 through 32,730 (of 59,099 total)