Viewing 15 posts - 43,381 through 43,395 (of 59,098 total)
GilaMonster (6/16/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 7:37 pm
george sibbald (6/16/2009)
Please note that the overall percentage of correct answers for QOTD has recently gone up from 57% to 58%
Heh... probably a rounding error by the same programmers that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 7:22 pm
MANU (6/16/2009)
Its an option under Create Index in sql 2000:http://msdn.microsoft.com/en-us/library/aa174535(SQL.80).aspx
MJ
Thanks Manu. What I was looking for, though, was a way to use DBCC DBReIndex with the sort-in-TempDB option. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 6:41 pm
Ah... got it. Seems like the right thing to do in this case.
Gus' code suggestion should work just fine except when you run into things like "&" and a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 6:33 pm
Mani Singh (6/16/2009)
Re-Starting SQL server is the best practise.
Ummmmmm.... Who made that rule? Do you happen to have an MS document that actually recommends such a practice?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 5:58 pm
Another possible method is Type 2 SCD's (Slowly Changing Dimensions). See the following article...
http://en.wikipedia.org/wiki/Slowly_Changing_Dimension
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 5:50 pm
Rich96 (6/16/2009)
Thanks so much.. that's going to do it for me!
Because this is a denormalization of data, I'm curious and I have to ask why this needs to be done?...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 5:45 pm
MissDaisy,
It's normally a very bad idea to store concatenated data in a table so I'm curious... why do you want to store concatenated data in a table?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 5:41 pm
ken.trock (6/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 6:22 pm
That may actually be ok... it depends on how many rows you're processing with things like the following...
EXEC UpdateAcdFact @ServerId, @SiteId, @EffectiveDate
How many rows does that sproc process for any...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 3:01 pm
Also I forgot to mention, this was a TESTBED server for ALL of development
Yep... you're correct. I totally missed it. Anyway, if you think I'm making a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 2:55 pm
It doesn't need to be the primary key. Doesn't even need to be the clustered index. Can be an index. It all depends... what do most of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 2:24 pm
Digs (6/14/2009)
Is there any CustomID method where I can create my own ID for keys in tables.
Sequential ID from identity is ok
The UniqueIdentifier works but is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 1:56 pm
Mike McQueen (6/15/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 1:50 pm
WayneS (6/15/2009)
Jeff Moden (6/15/2009)
Ok... you guys can remove the handrails, now. 😛
..... getting out the reciprocating saw .... or will that cause too much damage where the handrails are...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2009 at 1:46 pm
Viewing 15 posts - 43,381 through 43,395 (of 59,098 total)