Viewing 15 posts - 57,166 through 57,180 (of 59,101 total)
David...
What do you call "huge?" How many denormalized rows are we talking about? I work with a denormalized input from a million customer IVR and there are currently almost...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2006 at 5:01 pm
I appreciate the compliment but I didn't do anything... my comment was actually directed to Mohammed's fine and easy solution.
John is correct... using the system tables would certainly work,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2006 at 4:49 pm
So... how many rows must you examine (do this for)?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2006 at 4:45 pm
Cache. It's not supposed to happen but I've seen it before. Could be something else but I'd have to see all of the code to figure it out.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2006 at 4:26 pm
Views of views of views to feed DTS... I once raised my arm over my head in a very funny way and it hurt like hell. I went to the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2006 at 6:57 am
Way to go Nigel!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 15, 2006 at 5:50 am
DATEFIRST isn't server sensitive and is not a system wide setting when invoked from QA... it's session/spid sensitive...
Run the following in one QA window...
SET DATEFIRST 3
SELECT @@DATEFIRST
Run this...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 11:10 pm
Nicely done... very nice, indeed.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 9:53 pm
Of course, if you want to go with total formatting of the version column for ease of sorting in the future...
--===== If the test table already exists, drop...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 9:44 pm
Rich,
If your version numbers will never have more than 4 parts, here's a good start without a UDF... the first two sections of the code below are just to setup...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 9:29 pm
Change the EXEC(@SQL) to PRINT @sql and debug that... that will lead you back to the problem in your dynamic SQL.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 8:49 pm
Ok, I'm a bit confused... Rose posted "Queries can take hours to run, and performance is the major issue. To be honest, there is not a lot of relational data."
I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 8:25 pm
Remi... I think you may have confused a couple of people because you didn't include any documention in your test script to identify the fact that most of your code...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 7:28 pm
UPDATE Customers SET Last_Name = REPLACE(@LastName,'''','''''') WHERE Cust_ID = 'A34778'
Do heed the other's warnings...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 7:02 am
Step 1... For "queries from hell", the first step would be to "knock the hell out of it". Format the code so you can actually read it instead of having...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 6:47 am
Viewing 15 posts - 57,166 through 57,180 (of 59,101 total)