network profile
| bio | website | dvt.co.za |
|---|---|---|
| location | South Africa | |
| age | 42 | |
| visits | member for | 1 year, 4 months |
| seen | Apr 30 at 8:52 | |
| stats | profile views | 6 |
I have been developing software of all shapes and sizes using Microsoft technologies for around 20 years now.
The wonder of our profession is no matter how much experience we have, is that we continue to learn something new every day.
|
Jan 4 |
awarded | Yearling |
|
Oct 8 |
comment |
Best table schema to store daily hits for many items? Option 2 doesn't make much sense given your requirement to determine cumulative hits between any 2 dates. Your first option gives most flexibility. |
|
Aug 24 |
comment |
How can place SQL Server online on the internet? You might consider hosting your SQL database at a service provider - there are a lot of security concerns you need to address and a provider is likely to have more experience. |
|
Aug 17 |
comment |
Difference between count(*) and count(1) in mysql? Yes, is interesting to see how the different RDBMS handle an invalid expression. |
|
Aug 17 |
answered | Difference between count(*) and count(1) in mysql? |
|
Aug 14 |
awarded | Citizen Patrol |
|
Jul 31 |
awarded | Editor |
|
Jul 31 |
revised |
Implications of using a Unique NonClustered Index with Covering Columns instead of a Primary Key The index 'redundancy' was spotted after being inspired by Kimberley Tripp's blog article - referenced. |
|
Jul 30 |
comment |
Implications of using a Unique NonClustered Index with Covering Columns instead of a Primary Key Thanks - it turns out that the index stats showed that the PK was still heavily used for scans. It seems I was being overzealous - the readability / convention benefits of retaining the PK should outweigh any storage implications in the long run. The point about transactional replication clinches it though - we WILL need to replicate this database shortly. |
|
Jul 30 |
awarded | Scholar |
|
Jul 30 |
accepted | Implications of using a Unique NonClustered Index with Covering Columns instead of a Primary Key |
|
Jul 26 |
awarded | Nice Question |
|
Jul 26 |
awarded | Supporter |
|
Jul 26 |
comment |
Implications of using a Unique NonClustered Index with Covering Columns instead of a Primary Key Thanks - do you have any reference links? w.r.t. slightly worse, are you referring solely to the lower index density in the covering index, or is there something else which would cause this? |
|
Jul 26 |
awarded | Student |
|
Jul 26 |
comment |
Implications of using a Unique NonClustered Index with Covering Columns instead of a Primary Key @jn29098 - Updated. Confirmed that we do have a clustered index, on columns which are neither the PK nor the covering columns, so this doesn't seem relevant to this decision. |
|
Jul 26 |
asked | Implications of using a Unique NonClustered Index with Covering Columns instead of a Primary Key |
|
Feb 1 |
comment |
Attaching MDF without LDF Have a look at this post - it discusses how to rebuild the log in emergency mode, but as it requires a restart of SQL server isn't something to do on your Prod Server (Nb - Jose Basilio's answer, not the accepted one) stackoverflow.com/questions/773059/… |
|
Jan 4 |
awarded | Teacher |
|
Jan 4 |
awarded | Autobiographer |
