Viewing 15 posts - 43,336 through 43,350 (of 59,063 total)
southwynd (6/16/2009)
I figured it out. @@IDENTITY will not work. This is what I needed to do:SET @ID = IDENT_CURRENT('Table1 ')
No... IDENT_CURRENT can allow other people "in". Take...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:59 pm
andrewd.smith (6/16/2009)
You might wish to cast to a float or decimal value before calculating the average.
Nicely done, Mr. Smith. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:57 pm
MissyDaisy (6/16/2009)
I don't know how to get an ascii dump of a string from a particular column so I can't accurately say what characters they are.
Visually, it has spacing wider...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:56 pm
Steve Jones - Editor (6/16/2009)
Quick clicks, for example, I typically type the code in, highlight, and then click "code" from the left.
So, why not add a "#" to the menu...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:51 pm
You can simply read a single row from a guaranteed-to-be-present table and then catch the error if it fails. If it succeeds, then everything is working fine including the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:49 pm
Heh... thanks for the plug, Lutz. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:43 pm
Jason Coleman (6/16/2009)
as the dates are stored as numbers....Anyone point me in the right direction
Thx..
The dates should be stored as the Date datatype. What is the data type...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:40 pm
It's simply because that setting only affects comparisons... not the way a UNIQUE index works.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:36 pm
Steve Jones - Editor (6/16/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:25 pm
Unless you know for a fact that the server or the columns in the given table are case sensitive, just remove all instances of UPPER. This isn't Oracle. 😛
Unless...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 8:11 pm
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
Viewing 15 posts - 43,336 through 43,350 (of 59,063 total)