Viewing 15 posts - 1,381 through 1,395 (of 6,041 total)
What's interesting is how these misguided policies actually encourage bad SQL programming practices.
"A SELECT statement can not have more than two tables joined together..."
Hey, boss-man, when...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 7, 2017 at 11:12 am
Typical programming books like "Database Programming with C#" may cover data modeling to come extent, but it's more of an afterthought and rather sparse.
Ralph Kimball has some excellent...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 7, 2017 at 9:33 am
Perhaps the best way to proliferate a process is to make tools for the process ubiquitous. There is a rudimentary Database Diagram tool in SSMS, but it hasn't changed in...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 7, 2017 at 7:34 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 6, 2017 at 8:48 am
I do believe that predictive analytics (non domain specific) can be leveraged to improve the optimization of databases and data storage systems, and do some extent that's been around for...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 6, 2017 at 7:56 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 6, 2017 at 7:30 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 5, 2017 at 7:31 am
JavaScript and LINQ are just window dressing for SQL, just like in the construction industry stucco is dressing for (not a replacement for) solid brick.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 3, 2017 at 3:03 pm
The expected answer would be similar to the following, although any equivalent and simple set based solution would suffice.
SELECT CustomerID
, COUNT(*) AS ContactCount
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 3, 2017 at 1:56 pm
The following is not really a database design question, but more of a baseline SQL query question. It's simple enough that a core SQL developer could easily rattle off the...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 3, 2017 at 1:54 pm
Hell, even today there is no broad consensus on when exactly we should start dancing in the streets to celebrate the arrival of the Age Of Aquarius. Some New Age...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 3, 2017 at 11:22 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 3, 2017 at 11:14 am
So, how to establish a timeline for when data corruption first occurred?
Off the top of my head, the first place I'd look would be error logs, both...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
June 29, 2017 at 7:43 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
June 28, 2017 at 8:50 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
June 28, 2017 at 8:23 am
Viewing 15 posts - 1,381 through 1,395 (of 6,041 total)