Viewing 15 posts - 55,966 through 55,980 (of 59,098 total)
There are a number of ways to returns trees in a high speed fashion in SQL Server 2000.... are you simply having performance problems or are you just concerned with...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 11:46 pm
Concur...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 11:41 pm
It's just a gut feeling but your "need" is nothing more than a "feeling"... Hilton clients will understand that it's all the same company and they won't worry about ID...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 11:40 pm
Sorry for being a year late.
I thought the title of this article was "Sizing a Database"... not an advertisement for some 3rd party software.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 11:36 pm
Heh... I don't know and I'm sorry about that. I don't have 2l5, yet.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 11:30 pm
You might want to add something else to exclude statisics...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 11:28 pm
Do not shrink databases. Period. Fragmentation both at the database level and the file level is the result. There are execeptions, of course, but in general, do NOT shrink databases.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 11:24 pm
Heh... no way... two in the same lifetime is well enough for me
Learned a lot, laughed a lot, and puked a lot......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 5:24 pm
What "language" is the "For Each loop container" written in? Seems like anything that can use wild cards should do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 5:12 pm
No... all you need is to point BCP at the data on the other machine using a UNC... of course, BCP should be able to "see" it with the appropriate...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 5:09 pm
Thanks for the feedback, one and all... funny how the telcom business seems to need it the most ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 5:07 pm
Or, without variables...
SELECT d.Number1, d.Number2, (d.Number1 + d.Number2) AS Number3 FROM (--==== Derived table "d" does the aggragates once -- so outer select can reuse them with ease SELECT (SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 10:18 am
Heh... TempDb.mdf of 100Mb??? We start ours at 12 gig on boot up with growth settings of 500Mb. And, yes, we've found a huge performance benefit in having it that large...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 10:05 am
I went to the doctor once and said "Doc, if I hold my arm up like this, it hurts like hell." The doctor said "So... don't hold you arm up...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2007 at 9:54 am
Close... very close... but, that way will prevent an Index Seek if have a usable index on the column(s) because you're doing a calculation (subtraction) on the column. Best you'll ever...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2007 at 10:37 pm
Viewing 15 posts - 55,966 through 55,980 (of 59,098 total)