Viewing 15 posts - 50,641 through 50,655 (of 59,091 total)
15 million rows per month isn't much. Instead of looking for a hardware solution to a software problem, the best thing to do would be to follow the suggestions...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 11:54 am
My first question would be, why do you have a join to the Location table when you're not selecting anything out of it? Are you just using that as...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 11:48 am
I've found Zero applications that actually require case sensitivity... If I ever do, I'll change the collation on the columns that do rather than setting the whole database for it....
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 10:51 am
Heh... you live on a "farm", Steve... you know what it means to "close the barn door after the cows got out."
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 9:53 am
Without knowing what the 7 tables are, I'd say that's the better choice than trying to store it all as XML both from a design/maintainability aspect and a performance aspect.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 9:52 am
Try this link... also, do a search on "SQL SERVER TUTORIAL" and "T-SQL TUTORIAL"...
http://answers.yahoo.com/question/index?qid=20080229151637AAfb5Gu
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 9:50 am
Thanks, Anirban!
I absolutely agree. Steve Jones recently wrote an article asking the quesiton "Why do you write"? One of the reasons I pointed out was the incredible amount...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 9:36 am
Actually, "It Depends". You can trick it... see the following...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 8:54 am
The problem is that the stored procedures you're calling have been written to only handle 1 section at a time. Usually, the only way to use such a thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 8:41 am
Actually, the real reason why I write is because... I can't remember stuff no mo'. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 5:05 pm
Carl Federl (5/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 5:02 pm
creeds (5/9/2008)
Thanks for the feedback and the code you posted. What version of SQL Server are you using? I might be able to turn a treat for you...[/quote]
Jeff,
We're...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 4:59 pm
ALZDBA (5/10/2008)
Jeff Moden (5/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 4:57 pm
Thanks, Michael.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 7:57 am
This is the same thing that I just went through... I thought for sure that my latest article was on something very obvious. It turns out that it's not...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 7:32 am
Viewing 15 posts - 50,641 through 50,655 (of 59,091 total)