Viewing 15 posts - 49,756 through 49,770 (of 59,099 total)
Do you have a time zone column somewhere?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 4:22 pm
Stephanie Giovannini (6/23/2008)
- Different phone ids may represent the same phone number
- Customers may share phone numbers
- A customer...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 4:13 pm
So, write some dynamic SQL to do it...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 3:44 pm
Hey Mark! Nice avatar!!!! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 3:38 pm
Hey folks... especially Jeff Williams and Peter Larson... thanks for the great help. Like I said, I'm kinda new at 2k5 and you just don't find the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 3:35 pm
Clear proc cache and clear the free buffers using DBCC commands of a similar name. Then, recompile the stored procedure code.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 2:27 pm
Set the recovery mode to SIMPLE or Bulk Logged... use SELECT INTO to make the tables and transfer the data. Then, add indexes, keys, triggers, and constraints... use NOCHECK...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 2:25 pm
It's the number of seconds since 1970-01-01 and can be changed to an SQL Server DATETIME datatype using something like the following...
SELECT DATEADD(ss,1195507770,'1970-01-01')
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 2:13 pm
You also have many columns being returned in the SELECT lists of the derived tables that aren't used anywhere else... remove them. Just return enough data in those derived...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 2:10 pm
Doing a convert on a column guarantees there's no chance of an index being used as effectively as it could... you need to change this...
AND (convert(VARCHAR(6), TT.StartTime, 112)= '{?Period}')
......
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 2:05 pm
Ummm, dates cannot be blank... so doing this...
AND (ISNULL(update_date, '') <> ''
... is a total waste of CPU clock cycles. Further, putting ISNULL on the date column will...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 1:53 pm
Ben Leighton (6/24/2008)
sorry looks to me that Jeff has just made the point I'm trying to make. Thanks to all!
Absolutely not a problem, Ben. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 1:07 pm
TheSQLGuru (6/24/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 12:47 pm
And... you might just want to learn to use Float for financial calculations and then round the answer to make the humans happy. A great many of the functions...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 8:04 am
Heh... Decimal is prone to more "rounding" errors than Float ever will be... it's a matter of rounding to the correct scale... For example, what should the answer to 1/3*3...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 7:59 am
Viewing 15 posts - 49,756 through 49,770 (of 59,099 total)