Viewing 15 posts - 676 through 690 (of 6,041 total)
My wife and I got the kids a Beagle puppy from a local pet shelter for Christmas, so this holiday was extra special. 🙂
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 26, 2018 at 7:38 am
Hey, the days leading up to Christmas is the perfect time for team leads to schedule deployment requests. That way, if something goes wrong, the DBA will have plenty of...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 26, 2018 at 7:33 am
You're already importing the source text files using SSIS anyhow, so I agree with others that you should do this transformation using a "derived column" or "import column transformation" task....
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 21, 2018 at 12:44 pm
Look at this from different angles, I'll start by saying that the DBA should own the database. She should should be the smartest guy in the room when it comes...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 21, 2018 at 7:26 am
One thing that most all data breaches have in common is that it involves data access patterns that are not typical. The hacker must poke around, exploring for vulnerabilities, and...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 20, 2018 at 8:58 am
RegEx is useful, particularly for ETL, but from the perspective an application, having the data in a normalized and index-able format is more useful. A discussion came up a few...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 19, 2018 at 11:46 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 19, 2018 at 11:28 am
Jeff Moden - Tuesday, December 18, 2018 7:17 PMWhat does the warning triangle have to say?
It's warning about cardinality...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 19, 2018 at 6:26 am
Otoh, why are you specifying a...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 3:54 pm
Here is a portion of the execution plan:
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 3:42 pm
After examining Query Store, I have determined the following update statement is the source for the sample error above. It's performing an UPDATE/JOIN between a staging table and the production...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 3:37 pm
OK, here I will restate the problem, this time with less obfuscation, except for the actual data values involved.
Here is a sample error.
Cannot insert duplicate key...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 3:32 pm
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 3:20 pm
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 12:13 pm
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 11:54 am
Viewing 15 posts - 676 through 690 (of 6,041 total)