May 12, 2017 at 1:15 pm
Comments posted to this topic are about the item Cracking the SQL Code
Best wishes,
Phil Factor
May 15, 2017 at 7:50 am
Policies can destroy creative thought if applied too mechanically. In a complex system, such as a database, best-practices so often blur into 'it depends'.
What set of policies are appropriate (I'm assuming we're talking about best practices here) are also contextual depending on the data access patterns. A line of business OLTP database, a replicated subscriber serving as a reporting ODS, and a data warehouse are very different in terms of how they should be modeled and coded (ie: things like normalization, isolation level , indexing strategy, and usage of temp tables).
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 19, 2017 at 8:36 am
Agreed. Definitely.
Best wishes,
Phil Factor
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply