Viewing 15 posts - 45,046 through 45,060 (of 59,101 total)
You didn't try it enough. You will get dupes if you use CheckSum on GUID's.
SELECT TOP 1000000
CHECKSUM(NEWID()) AS...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2009 at 9:22 pm
I hope this was at least a paid entry. Other wise, I'd have to rate it as some seriously overdone SPAM.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2009 at 8:57 pm
Have fun... sp_who2 has two SPID columns. Make sure you name them differently in the temp table.
Also, think about NOT using a cursor.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2009 at 8:46 pm
Ninja's_RGR'us (2/22/2009)
... and what's the value for a transexual or people with both sexes?I'm really asking, just wondering if they covered all bases.
Heh... too easy... use the BIT datatype... 0...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2009 at 8:42 pm
sriram (2/22/2009)
henry - 10/20/1960 - 2 - 3 - 5
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2009 at 8:38 pm
I'd say there's bigger fish to fry...
Bold, italics, and underline work just fine but the highlighted item being affected loses focus after any of those. It's frequently desireable to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2009 at 7:56 pm
GilaMonster (2/21/2009)
You can't select from a stored procedure.
Actually, you can...
SELECT *
FROM OPENROWSET('SQLOLEDB','Server=yourserverinstancehere;Trusted_Connection=Yes;Database=Master',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 4:19 pm
Do you have any ETL processes on that server?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 4:06 pm
What you call a "normal" table structure may be the best or the worst or somewhere in between. You asked a question with no real information to go on...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 4:03 pm
KT8177 (2/20/2009)
select *
from openrowset('Microsoft.Jet.OLEDB.4.0'
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 3:42 pm
Make sure you read this fully
Heh... right... read 19 pages of posts... some with some pretty bad information (not yours). Can you summarize, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 3:41 pm
Edward Boyle (2/21/2009)
That said, I use both Tally...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 3:28 pm
I absolutely agree... It's not what you can backup... it's what you can restore. I do at least one "practice" recovery a week and I'm not the System DBA....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 3:20 pm
It's a "Catch 22". Only Developers that actually concern themselves with things like performance, scalability, and documented code would ever take the time to add such instrumentation to the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 3:17 pm
Please see the following article... for performance reasons, you may want to reconsider and use simple cross-tabs, instead.
http://www.sqlservercentral.com/articles/T-SQL/63681/
Also, if you'd like a tested answer to your good question, please see...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2009 at 3:06 pm
Viewing 15 posts - 45,046 through 45,060 (of 59,101 total)