Viewing 15 posts - 49,636 through 49,650 (of 59,091 total)
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
schuppe (6/26/2008)
insert into testtable values(getdate(), dateadd(day, 5, getdate()));
with test (startdate, enddate) as
(select startdate, enddate from testtable
union all
select dateadd(day, 1, test.startdate), test.enddate...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 7:56 pm
Michael Earl (6/26/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 7:52 pm
GSquared (6/26/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 7:46 pm
In that same vein...
DROP TABLE JBMTest
GO
--===== Create and populate a 1,000,000 row test table.
-- Column "RowNum" has a range of 1 to 1,000,000 unique numbers
...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 7:40 pm
First, the warning about nulls is just that... a warning to let you know that some rows had nulls and they were ignored. You can suppress that message with...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 7:37 pm
Heh... rowcount can be wrong in sysindexes unless you run the correct DBCC command to update them... that's a hint... look it up in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 7:31 pm
I dunno... I'm thinking that's about the 100th 64 bit related performance problem that I've seen in the last month or so... I'm thinking the 64 bit version is like...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 7:29 pm
With the information given, I would say the xyz.exe has a problem that needs to be repaired. Just because it compiles doesn't mean it's right... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2008 at 7:26 pm
Viewing 15 posts - 49,636 through 49,650 (of 59,091 total)