Viewing 15 posts - 44,491 through 44,505 (of 59,097 total)
Steve Jones - Editor (3/21/2009)
Yikes, looks like a lot of stuff to fix. We'll go through some of this next week.
I actually did this because Phil sent me an email...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 7:13 pm
Matt (3/21/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 6:47 pm
I fear programmers will miss the big picture that a top-quality book often provides
There're a couple of problems with that statment... first, there are disappointingly few programmers and a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 6:24 pm
Heh... this is a pretty simple problem and I'd try to help but you keep posting data in that absolutely useless JPG format. I'm not going to copy from...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 5:44 pm
Jeff Moden (3/20/2009)
ramu.valleti (3/20/2009)
what do you mean by "single query".?You can use sub queries to achieve this.
Regards,
Ramu
Cool... let's see it, Ramu.
Ramu... you there? I'd still like to see the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 5:37 pm
S (3/20/2009)
Thanks for the reply.
I should have expressed it clearly or more correctly.
Is it possible to achieve it with out using multiple statements (exclude subqueries as they are part...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 5:36 pm
There are three problems with recursive CTE's being used to supposedly resolve hierarchies...
1. Recursive CTE's are slower than cursors and a fair bit slower than a good "Fire Hose"...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 5:33 pm
Ummm.... just a couple of things to clear up here, folks. First, DBCC ShrinkFile does not now nor has it ever nor will it ever cause fragmentation. It's...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 5:09 pm
No... the cache I'm talking about is in the memory of the SQL Server.
And, no... indexes don't take care of themselves. Now that you've identified that you're not running...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 4:54 pm
Sounds like a plan... like you, I'm a bit busy this weekend but I'll get things going on this soon. We should also explore some of the other...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 4:44 pm
Sorry... I believe that one of two things has happened here... either that the two of you guys on the interview left something out of the code you posted, or...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 4:30 pm
Yeppp... couple/three things... first, it sounds like you may have a little "parameter sniffing" going on. Google'ing that will produce a pot wad of information on what it is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 4:13 pm
Amit Lohia (3/18/2009)
Steve Jones - Editor (3/18/2009)
http://www.steverrobbins.com/articles/ceojob.htmSteve, in your own word please. One sentence.
Shoot... you don't need a whole bloody sentence... you can sum it all up in one word...
[font="Arial...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 4:02 pm
Sure... well, maybe except for the article thing. I was thinking that the idea of using a sequence table correctly would make a good article right after I wrote...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 3:31 pm
You've managed to hit the other area that I drop the sword and shield on for CLR deployment... file management. 😉
As you know, hierarchical data in SQL Server is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 21, 2009 at 3:17 pm
Viewing 15 posts - 44,491 through 44,505 (of 59,097 total)