Viewing 15 posts - 7,666 through 7,680 (of 59,098 total)
I'm seeing dupes in the first 10 lines and an open single quote on the 6th line for starters.
My suggestion would be to make things work in SSMS first and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2020 at 3:43 am
I'm curious... are you trying to find this file so you can import it into SQL Server?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 11:24 pm
Last but not least, is the extra space "unallocated" or "unused"? If it's "unallocated", it could be from a recent index rebuild. If it's "unused", you might want to lookup...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 11:21 pm
Thanks, Matt. I appreciate the info. I took a look a while back at SPARK SQL... the syntax of even simple things like DATEADD is quite different but I was...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 11:14 pm
The XML approach is one of the slowest mostly because of "ExpAnsive Concatenation".
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 11:02 pm
Sorry... Missed Jonathan's post, which appears to be spot on. Jonathan, how did you figure out it was a rail schedule and where to get the documentation on it? Is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 3:08 pm
The original question was how to import the data without having to use SUBSTRING to do it. The answer there is to use a BCP Format File along with BULK...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 2:58 pm
I don't really feel like I should be defending myself here, but 'BSNC001481905191912080000001 PEE5P01 124650005 EMU 090D P' is 57 characters long, the length of all those columns is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 2:28 pm
You're welcome and thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 2:25 pm
It sounds to me like you have an identically named/structured table in multiple databases and they want to keep all of them in sync insofar as content. Is that correct?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 2:19 pm
First, can someone speak to the premise that the entire row is updated when updating one column?
No. Only the modified column(s) are updated.
We can certainly prove that with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 4:48 am
First of all, I appreciate it when anyone puts the time and effort into writing and publishing an article, so thank you very much for that. Keep writing.
As you've seen...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2020 at 4:38 am
HDFS is alive and well - just like SQL was never threatened. I'm reminded of those Reeses Cups commercials from the 80's where two people collide -...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2020 at 9:07 pm
HDFS is alive and well - just like SQL was never threatened. I'm reminded of those Reeses Cups commercials from the 80's where two people collide -...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2020 at 9:00 pm
This question isn't designed to cover all possibilities. Writing questions like that is hard and fraught with perils. You are welcome to submit your own questions about other types...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2020 at 8:51 pm
Viewing 15 posts - 7,666 through 7,680 (of 59,098 total)