Viewing 15 posts - 52,066 through 52,080 (of 59,102 total)
Most people use the default settings for auto-grow and DB size... that's 10% and 1 MByte. Now, lemme tell you why it's REALLY bad to do that... first, what...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 4:21 pm
No offense... but this isn't really something that someone "new to SQL Server" should be asked to handle. You need to hire a good DBA to help you do...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 4:15 pm
It's a bug... turn off task pad by selecting a different kind of view... then, turn it back on. Problem should fix itself. If it doesn't you may...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 4:08 pm
John, you happen to have come to the right place at the right time...
There are several methods to do this, but for shear performance, nothing beats the method I'm getting...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 3:57 pm
Chris Schanno (3/6/2008)
Yes, I would consider using a cursor over the set based approach depending on the circumstances such as the size of the dataset and use for which I...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 3:02 pm
Sorry, previous knowledge... he's asked for it before on a different thread.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 2:47 pm
Jacob Luebbers (3/6/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 2:45 pm
The join needs to be part of the covering index or you will only get a scan.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 2:37 pm
The tuning wizard is recommending a full blown "Covering Index" and it's a good thing to have for a heavy duty set of SELECT's like this. It will, however...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 2:33 pm
The only way either of those would fail is if the data is different that what you said. Please post some sample data and a table to load it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 2:31 pm
a-brbeck (3/6/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 2:19 pm
Oooohhh... I just ran into that paging problem... really bad case of parameter sniffing and the traditional methods don't fix it... only full blown dynamic SQL fixes it... lemm see...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 1:38 pm
p.s. You friend DOES know what Books Online is, doesn't (s)he??? I figure if you have to ask questions on this forum for him/her, they just might not...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 1:03 pm
A week of preparation on this is not enough... but I'd say your best bet is to curl up with Books Online for the next week...
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/e9099cce-7f81-4808-8523-587bbcdc1720.htm
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c2eb5f77-2dc1-49b4-bd19-2cdac4c6cae1.htm
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/31529dfe-68e7-49f7-b3c2-39fcecf33a95.htm
... an exam-cram of this...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 1:00 pm
Just another test... please ignore.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 11:00 am
Viewing 15 posts - 52,066 through 52,080 (of 59,102 total)