Viewing 15 posts - 3,271 through 3,285 (of 59,086 total)
I would recommend working with the receivers of the data to allow sending UTC directly instead of trying to perform the conversion for them. If you send UTC they...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2022 at 7:33 pm
Could a function be created where I pass in my date and it outputs my desired date
For 2012, yes, but that doesn't change step 1. You need a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2022 at 6:00 pm
BTw... the easier thing to do would be to convert your local dates and times to UTC and let the users fix their stuff. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2022 at 1:05 am
If I was SQL 2016 then...
JobStarted AT TIME ZONE 'Eastern Standard Time' AT TIME ZONE 'Central European Standard Time' AS JobStarted_TimeZoneCET
That server will be moving to 2016 but need...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2022 at 1:03 am
"does it REALLY need to be at the single row level of detail?" not necessarily
"they can tell you what aggregates they need to analyze and do that pre-aggregation for...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2022 at 12:59 pm
If you ran out of log file space on that NCI build, you're simply going to need more disk space for the log file. I also suspect you may have...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2022 at 7:08 am
... and if you have any elegant solution it will be great
I posted a link in my previous response as to what I think "the" elegant solution would be. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 11:28 pm
Stuff like this worries me. Just obfuscating the day part of a birthday still allows someone to determine that rough age of a person and, if they have a couple...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 9:48 pm
here is an (simplified) example below
SELECT tab1.a
tab1.b,
tab2.c,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 9:40 pm
Q: Sorry, but I'm not seeing it. How would such a thing be used to improve the performance of the query the OP posted?
Valid point, chances are good it...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 9:23 pm
Ohhh... no extended comment from me... none of it would pass HR. Let's just say that "I'm lovin' the lockdown" and seriously enjoy working remotely on all fronts.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 8:57 pm
Sounds like a prelude to spam... why would anyone in their right mind try to take an average on such an identifier column? Really bad question and, since you say...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 5:35 pm
One of the fastest methods ever created for doing this type of thing is documented in the following article.
https://blogs.solidq.com/en/sqlserver/packing-intervals/
It's an older article so solution #3 can be made work in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 5:17 pm
This was an interesting subject that I'd not heard of before. I checked and found the following article by Paul Randal. What most interesting is his answer to one of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 4:32 pm
Just out of curiosity sake, can you post the entire CREATE UNIQUE INDEX statement you were running to get this error?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2022 at 4:17 pm
Viewing 15 posts - 3,271 through 3,285 (of 59,086 total)