Viewing 15 posts - 51,841 through 51,855 (of 59,091 total)
Wouldn't OUTPUT return the same data type as whatever column or variable appeared in the stored procedure?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 7:25 am
While it's true that there is some trickery you can perform to "Tune the hardware" and "Tune the database" and you can throw indexes at tables to make some queries...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 7:12 am
No... no way to create a temp view. Creating a TempTable to hold what the TempView would have contained is the next best thing and pretty darned fast to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 7:00 am
Heh... LOL. I guess using TOP to overcome a double triangular join will do. 😀 I'll add it to my list of paging methods to test for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 6:43 am
Grant Fritchey (3/12/2008)
It sounds like a paging problem.One, of many, solutions that Itzik Ben-Gan offers in TSQL Querying:
I wish great authors would warn people of the code the create. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 5:35 pm
I built a million row table as you described. I made it so that the Status column has only 5 different possiblities and verified the distribution as an average...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 5:24 pm
Adding columns to a temp table or any table that uses ALTER is always a PITA... during run time, the new columns are perceived as NOT THERE. That means...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 3:03 pm
It simply substracts 2 from the character position returned by the FINDSTRING.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 2:34 pm
madeley68 (3/12/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 12:01 pm
Now there's an idea... and properly partitioned, it would be updateable, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 11:47 am
Perfect... thanks for the feedback!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 11:43 am
Lynn Pettis (3/11/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 11:10 am
Great link for a "System DBA", Adam. What about an "Application DBA" or a "Hybrid"?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 8:37 am
Isn't a DB2 timestamp is listed in seconds since some date? Are we chasing a ghost just because the OP said "it used to work"?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 8:31 am
Heh... and, still, you have to pay attention to the title... "ESTIMATING the size of a clustered index."
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2008 at 8:27 am
Viewing 15 posts - 51,841 through 51,855 (of 59,091 total)