On 2016-03-28 11:01, Stephen Russell wrote:
For me it was moving business that was prepped in test and easily
moving it
to production. The keys are no longer an issue.
The issue with indexes is the free space available in an index page
before
it has to split into two pages for the same data.
This is only in a primary key because it can always be a problem in the
secondary one. The GUID generated may fit into any one of different
btree
index pages, but a int will only be placed at the last page.
The point you made about switching between systems (Test, Production,
Local, somewhere else) was the bonus for me using this approach. That,
and as mentioned earlier, being able to combine data from different
disconnected datasets (Database1, Database2, etc.). No more worrying
about AutoInc either meaning something else to a different disconnected
dataset, or duplicate integer keys (and see reason prior as a result).
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
