Viewing 15 posts - 32,881 through 32,895 (of 59,102 total)
I know it doesn't help but this is one of the many reasons why I try to do as much as possible from T-SQL. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 5:03 pm
tacy.highland (8/16/2011)
Question though, if this column is in Date format and the other fields are smalldatetime and I do a DATEDIFF between the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 4:50 pm
R.P.Rozema (8/16/2011)
Jeff Moden (8/16/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 2:57 pm
R.P.Rozema (8/16/2011)
However, in situations where readability is more important than raw execution speed
You're absolutely barking up the wrong tree with me on that subject. 😉 For me, performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 12:17 pm
SQLSandwiches (8/16/2011)
So if ALL isn't useful. Why still keep it around? MSSQL is released every couple years....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 12:06 pm
Try putting the cutoff year at 60 (NOT 49! That's going in the wrong direction!). That'll solve your immediate problem.
You're longer term problem is, of course, the 2...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 12:45 am
I'm sure that Grant Fritchey or Gail Shaw will have the precise numbers in their head but, yes... small tables (especially those less than 1 extent) won't be defragged because...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 12:39 am
I've used ALL once before... to show the same thing. 😉
Still, I'm always open to something different... what else could you use ALL for? I ask because I've never...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 12:35 am
I've gotta say it again... ya just gotta love XML tag bloat. All of this data would likely fit in a single well formed, properly delimited, single character delimited...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 12:18 am
A second run without rebuilding the test table shows a slightly different story, as well...
========== DATEADD/DATEDIFF ==========
SQL Server Execution Times:
CPU time = 1326 ms, elapsed...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 12:05 am
Evil Kraig F (8/15/2011)
Chuck Hottle (8/15/2011)
This is good and simple too.SELECT CAST(FLOOR(CAST(GetDate() AS FLOAT)) AS DATETIME)
I was originally going to call this a bad idea, but I decided a little...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2011 at 12:00 am
Evil Kraig F (8/15/2011)
Jeff Moden (8/15/2011)
You might want to check again... what happens on May 31st?
I'm confused here Jeff, nothing bad happens on May 31 + 3 months. August...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2011 at 11:35 pm
My recommendation would be to lookup what @@ROWCOUNT might do for you.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2011 at 11:12 pm
I believe the following will do the trick according to the updated requirements quite simply.
DECLARE @a int = 102733019,
@b-2 int = 102733019...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2011 at 11:07 pm
Eliyahu (8/14/2011)
When I run SELECT * FROM myView WHERE myCondition, will the SQL Server first extract values from the XML column for all 10,000 rows and then...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2011 at 5:00 pm
Viewing 15 posts - 32,881 through 32,895 (of 59,102 total)