Viewing 15 posts - 43,231 through 43,245 (of 59,102 total)
Scott Coleman (6/26/2009)
You can use a self-join solution, although depending on your rowcounts and indexes this may...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 3:29 pm
Florian Reischl (6/26/2009)
Sure, it's a task on my list, too. 😉 But it's really neat that he provides a complete test setup.
I agree... it just like some of the good...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 3:25 pm
Florian Reischl (6/26/2009)
Jeff Moden (6/26/2009)
jaclynmcatanzaro (6/26/2009)
Good SQL Server articleWhich one?
Can't answer your question but the new article by Adam Machanic is really good in my opinion:
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 3:19 pm
Unless you're very careful, it becomes nothing more than an excuse for releasing bad or slow product with no documentation. Contrary to what many believe, it does take some...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 3:08 pm
DBCC CHECKIDENT
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 3:00 pm
jaclynmcatanzaro (6/26/2009)
Good SQL Server article
Which one?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 2:53 pm
You can specify that the sort done during the rebuild will be done in TempDB which should make your life a whole lot easier when it comes to space used.
Of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 2:49 pm
karthik_sql (6/24/2009)
Please try the below1. Put db to Simple recovery
Absolutely NOT! That will make a mess of the log file for purposes of backup.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 2:46 pm
tejas parikh (6/26/2009)
All I'm running is a simple count(*) below. The cpu usage goes to a 100%...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 2:44 pm
vick.ram79 (6/26/2009)
select batchID, [outfolder], [outfile]
from (Select batchID, paramName, paramValue From #foo) tmp
Pivot
(Max(paramvalue)
for paramName in (outfolder,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 1:55 pm
I could be wrong but I'd have to say it's because a recursive CTE is just the same as a While Loop (sometimes, it's worse). It's only going to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 1:51 pm
I agree with Lynn. No sign of a triangular join in your query. Are you merely talking about the fact that you have a "derived table" in your...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 1:48 pm
Adrienne (6/17/2009)
Can you just add this...,(select sum(b.sal) from cte b where b.seq_no <= a.seq_no and b.deptno = a.deptno) as "RunningTotalWRTDept"
Ummmm.... no. While that works, it has no scalability and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 1:43 pm
Krasavita (6/26/2009)
Thank you:-)
Heh... wait a minute, now.... splitting the date and time is normally a really, really bad thing to do. Why do you need to do this?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 12:49 pm
Ah... no joy... I still need some help on this, please. Even though I've found the sp_MS_upd_sysobj_category stored proc in Master and modified the the Web.sql stored procedure that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2009 at 12:43 pm
Viewing 15 posts - 43,231 through 43,245 (of 59,102 total)