Viewing 15 posts - 57,136 through 57,150 (of 59,067 total)
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
Heh... David, it is I who is not worthy... thank you for your continued compliments. You made my whole day! Good "seeing" you, again.
Anyway, folks... considering the trully variable nature...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2006 at 6:24 am
If you use BCP and a format file to import to a table, you don't need the "control file"... just add the necessary constraints to the table and setup BCP...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2006 at 5:59 pm
You bet... thank you for the feedback, Norbert...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2006 at 5:52 pm
Using Remi's fine demo table, the following will actually give you dates and times for half hour slots... it will not, however, give any missing slots... that would require just...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2006 at 11:04 pm
Viewing 15 posts - 57,136 through 57,150 (of 59,067 total)