Viewing 15 posts - 7,246 through 7,260 (of 7,608 total)
return an INT value, which at a precision level of 7 gets overflowed.
The INT can't overflow returning billionths of a second -- the max possible value is 999,999,999, which is...
September 6, 2012 at 1:09 pm
Jeff Moden (9/6/2012)
ScottPletcher (9/6/2012)
I don't think audit triggers are relevant any more, given the better options built into SQL itself now.I've not found those options to do so well.
Interesting. ...
September 6, 2012 at 9:45 am
Jeff Moden (9/6/2012)
September 6, 2012 at 8:52 am
It doesn't need a trigger because the data doesn't change, it just needs to be cleaned up.
But the trigger DOES the clean up, which guarantees that (1) it occurs and...
September 5, 2012 at 3:49 pm
Sean Lange (9/5/2012)
To me that is vastly better than using LTRIM/RTRIM on all subsequent queries!
You certainly have a valid point. Not sure that adding an insert/update trigger on every table...
September 5, 2012 at 3:14 pm
To be fair, higher precision in intermediate calculations in complex equations can in fact cause errors rather than solving them.
I'm certainly no authority on currency laws, so I can't speak...
September 5, 2012 at 3:12 pm
Sean Lange (9/5/2012)
I don't think I agree that you should just add a trigger to trim spaces but we can agree to disagree here.
To me that is vastly better than...
September 5, 2012 at 2:51 pm
I think you avoid all the CROSS APPLYs, as below.
As written the code just ignores anything beyond 24 hrs, but if you needed to, you could add a check for...
September 5, 2012 at 2:28 pm
oradbguru (9/4/2012)Due to application limitations, there can only be the one existing filegroup.
Thank you
?? Not sure I follow. Applications should be completely unaware of any filegroups in SQL...
September 5, 2012 at 1:22 pm
You should use a trigger to trim the data during INSERTs and UPDATEs -- NEVER let poorly formatted data be queried directly from the database.
Personally I don't see anything wrong...
September 5, 2012 at 12:41 pm
Since the table already contains the previous year's YTD totals, would a simple LEFT JOIN suffice to get the prior year's YTD total?
SELECT
t1curr.cod, t1curr.[year], t1curr.[month], t1curr.value,...
September 5, 2012 at 12:29 pm
GSquared (12/14/2009)
BaldingLoopMan (12/14/2009)
To each their own.
Even in cases where the data type precedence won't cause a problem, I find the Coalesce version below much easier to read, understand, and maintain,...
August 28, 2012 at 3:45 pm
Any of that seems like overkill to me for the specific problem stated. Why not just?:
SELECT
name,
ISNULL(MAX(CASE WHEN type = 'typeB' THEN...
August 28, 2012 at 3:08 pm
winston Smith (8/28/2012)
But you can make a clustered index based on only a small number of columns in...
August 28, 2012 at 2:36 pm
Viewing 15 posts - 7,246 through 7,260 (of 7,608 total)