Viewing 15 posts - 49,636 through 49,650 (of 59,099 total)
janine.rawnsley (6/26/2008)
Wasn't TAB in Barry's also an intermediate table?I could probably write it to use just one table.. but it'd be messy and got a day job..
No... was meant to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 9:02 pm
Ronald Cartmale (6/25/2008)
select * INTO #tmpHumongous from Massive where 1=0
You don't need to do that... that problem was solved way back in 6.5.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:55 pm
jds (6/26/2008)
anyway, I have got it resolved.
Two way street here... how did you resolve it?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:49 pm
Along with what Gail said...
... find and rewrite all RBAR to be good set based code. Learn how to use tricks of the trade like a Tally table. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:47 pm
Why on Earth are you still using the TEXT datatype on 2k5? Convert the text to VARCHAR(MAX) and you're done.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:42 pm
So... why did you post in the 2005 forum or at least let us know in the beginning that you were using 2000?
About the only way to do this in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:40 pm
Stephanie Giovannini (6/26/2008)
I have a table in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:28 pm
Matt Miller (6/26/2008)
A natural key that will end up with duplicates is no longer a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:25 pm
Also be aware that neither of those will handle the TEXT datatype. What you might want to look into is the undocumented sp_execresultset...
If you're using SQL Server 2005, lemme...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:22 pm
The real problem is that you're using the same table for OLTP and Batch processing. Load the data into a separate table (staging table), process it, the transfer the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:17 pm
To wit...
http://www.sqlservercentral.com/articles/T-SQL/63003/
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:13 pm
Jeff Moden (6/26/2008)
Michael Earl (6/26/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:10 pm
Michael Earl (6/26/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:10 pm
GSquared (6/26/2008)
Something like:
select t1.Col1
from dbo.Table1 t1
left outer join...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:05 pm
That's what the OP is trying to avoid, Gus... OP wants the temp table to size itself and it's columns like it would using a SELECT/INTO except the OP wants...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 8:02 pm
Viewing 15 posts - 49,636 through 49,650 (of 59,099 total)