Viewing 15 posts - 21,121 through 21,135 (of 59,072 total)
I've seen quite a few mistakes in temporal calculations. None of them were the direct result of adding a valid character based time to a DATETIME. I've seen...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 8:56 pm
mpescod (3/29/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 7:42 pm
mark hutchinson (3/29/2015)
Null is a something that means nothing
I'll have to disagree with that. To me, an empty string or the number 0 is nothing. Null can have...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 7:39 pm
Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 7:31 pm
For me, the "right way" would be to constrain the column to being NOT NULL and default it to zero. Makes life a whole lot simpler.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 2:45 pm
My question would be, why does one need to know the count of rows of this table to begin with? Since someone is adding a hundred rows per second...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 2:31 pm
George Wei (3/28/2015)
Our system runs a SQL Server 2012 DB, it has a table (table_a) which has over 10M records. Our system have to receive data file from previous...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 2:10 pm
Unless synonyms or pass-through views are in play, I'm pretty sure that you need to use the 4 part naming convention to "talk" across servers.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 1:36 pm
From your example, it would appear that this is more of a risk in explicit conversions than the implicit ones, in this case.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 1:25 pm
Heh... to quote someone far wise than I, "NULL is not nothing".
--Jeff Moden
Change is inevitable... Change for the better is not.
March 29, 2015 at 12:42 pm
So, what does the file look like and what does the table look like? And, does the table have any indexes or constraints on it?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2015 at 8:08 pm
Steve Jones - SSC Editor (3/27/2015)
And I didn't respond last weekend because I bought this:
BWAAA-HAAA!!!!! SPAM REPORTED!!! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2015 at 6:34 pm
I think that someone on "spam patrol" deleted the other two posts by mistake. This is the third instance I've seen of this particular request in the last hour....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2015 at 4:52 pm
Arjun SreeVastsva (3/27/2015)
I have one database App with having bulk logged recovery model.one customer raised a question that in this database which operation will run very firstly
one operation is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2015 at 4:25 pm
ScottPletcher (3/27/2015)
Eirikur Eiriksson (3/27/2015)
ScottPletcher (3/27/2015)
Just add them and SQL will implicitly convert the varchar to a datetime anyway:SELECT datetime_column + time_varchar AS new_datetime, ...
FROM ...
Until the locale driven implicit conversion...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2015 at 3:47 pm
Viewing 15 posts - 21,121 through 21,135 (of 59,072 total)