Viewing 15 posts - 6,706 through 6,720 (of 59,091 total)
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
That particular problem is because there's a head row that you're not skipping. Add the following to the options in the BULK INSERT command...
FIRSTROW = 2,
I tried the same thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2020 at 2:09 am
Speaking of tenacity, that's some Awesome feedback! Thank you for taking the time to share what you found all across the board... especially the 4 space duplicate key error. I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2020 at 11:04 pm
For me, it's not a matter of being resistant to change or something new. My problem is that I've seen all manner of supposed "improvement" and supposed "better ways to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2020 at 7:46 pm
In a specific Query, how can you easily identify how long each piece of code is taking? My query is taking over 20 minutes so I can't just comment...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2020 at 8:18 pm
To add to Phil's correct answer, if there are a lot of columns, open the Object Explorer window, locate the table you need the column names for, find the "columns"...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2020 at 8:13 pm
Are you saying that you want ALL sequences to be set to the same number? If so, it makes no sense and the restored databases will all suffer multiple PK...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2020 at 4:34 pm
I have to ask, since "all sequences" are likely to grow at a different rate, why are you even thinking about doing such a thing?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2020 at 3:25 pm
Hard to believe the "way better" comment... the first two were awesome! You've enticed me to read the 3rd edition to see. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2020 at 2:25 pm
I have multiple parameterized SP for our Application.
When I Executes those SP individual it will returns output within 1 Sec. But when we are running Test Load with multiple...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2020 at 1:57 pm
First of all, I've not yet read the 3rd edition but I did the first two. If Grant continues his tradition of excellence in this 3rd edition as he did...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2020 at 1:48 pm
We are upgrading from SQL 2014 to SQL 2017. Noticed that integrity checks are running 6 times faster than SQL 2014. Is that a big enhancement in SQL 2017?...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2020 at 1:37 pm
Viewing 15 posts - 6,706 through 6,720 (of 59,091 total)