Viewing 15 posts - 691 through 705 (of 6,041 total)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 10:26 am
I don't think we should shape and force a RDMS like SQL Server to act something like a EAV or document database. We've got more data storage options inside SQL...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 10:04 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 9:55 am
Entity-Attribute-Value tables are good for modeling operational configuration data; things like configuration strings, thresholds, and client implementation settings. The benefit is that it allows the application developers to easily create...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 18, 2018 at 7:45 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 17, 2018 at 1:20 pm
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 17, 2018 at 1:10 pm
I'm not on the ETL team, so I can't vouch for the specifics of why the table / indexes were modeled the way they are. However, it appears the index...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 17, 2018 at 12:50 pm
I have confirmed with the ETL developers that they are using READ COMMITTED ISOLATION on both remote source database and target database.
The version of the source database server...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 17, 2018 at 12:30 pm
What is the DDL for...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 17, 2018 at 12:25 pm
Outside the context of ETL staging, if your application must resort to pattern matching on varchar columns when joining tables or filtering rowsets, then your data model is to some...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 17, 2018 at 11:18 am
Also, keep in mind that MIN and MAX are scalar operations, so they will always return a value, like a value of NULL for an empty table. However, SELECT TOP...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 17, 2018 at 7:27 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 13, 2018 at 12:19 pm
Another issue is date/times contained in VARCHAR columns.
The ISO standard for formatting date strings is YYYYMMDD, and the following check constaint will not only require that the string...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 13, 2018 at 7:47 am
If you're debating whether something like phone number or zip code should be contained as a varchar versus an integer, then I'd rather err on the side of varchar. For...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 13, 2018 at 7:31 am
I don't have a problem with Microsoft's technical implementation of CLR functions in SQL Server. It's just that when folks want execute C# or VB.NET from SQL Server queries, it...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
December 12, 2018 at 7:12 am
Viewing 15 posts - 691 through 705 (of 6,041 total)