Viewing 15 posts - 6,706 through 6,720 (of 59,102 total)
Thank you guys....I really appreciate your reply but nothing of you give me a solution. Everyone talking about the weather, the child and how to dry the rocks with...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2020 at 1:22 pm
Ok... my apologies for not reading the original post well enough. My only concern was the /100 thing. Now I understand what's being done.
The CROSS APPLY method works just fine...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2020 at 2:56 am
My GUESS with this question is Jeff replied and then the OP was changed as the OP already has Jeff's suggestion implemented.
That would be a good guess, Brian.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 10:04 pm
Sorry... post deleted. Looking at it all again.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 10:02 pm
Change all the /100 things to /100.0
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 9:01 pm
It worked find for me as just \ n (without the space). The 0x0a thing will also work. For those that are reading this and don't know, that is the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 6:32 pm
I know it's an option in SQL Prompt... but... I do not think the inclusion/exclusion of quoted identifiers is a configurable scripting setting in SSMS.
Ah... my apologies. It's only...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 6:26 pm
Andy Mallon has a procedure to remove them.
https://am2.co/2018/07/removing-square-brackets-from-generated-ssms-scripts/
It's no longer needed if you have the later versions of SSMS. It's actually a setting now and, IIRC, it also...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 5:06 pm
I did run some tests. On SQL 2014 it is taking approx 8 - 10 hrs and on SQL 2017 it is taking less than 2 hrs. I can't...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 5:04 pm
Heh... "Computing Revolution". I call it the "Dust Revolution" because data and code is just like dust... it accumulates on horizontal surfaces (and sometimes sticks to vertical surfaces in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 4:52 pm
It's the nature of the beast and, to be honest, the brackets are the preferred method (in SQL Server, anyway) for using reserved words and object names that contain spaces,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 3:21 pm
BTW... I left a bit of a test in the table creation code and you should change it. The first column should be a BIGINT and not VARCHAR(11).
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 3:14 pm
p.s. Try it with my changes to the table and the BULK INSERT command first without doing the powershell stuff. I don't know if I just had a bit of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 1:38 pm
The Powershell code will work on any PC. Although it doesn't need to be, I installed it as a .bat file in the same directory as the file. That makes...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 1:36 pm
Ok... I got this working BUT...
The bastards lied on their record layout. The "HEALTHCARE_PROV_TAXONOMY_GROUP_xx" columns aren't 10 wide in the data... they're up to 43 characters wide. I changed the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 4:39 am
Viewing 15 posts - 6,706 through 6,720 (of 59,102 total)