While determining upon the secrets for any table, could it be good with an INT primary key (autoincrement) for that table along with a GUID (additionally towards the INT) for that scope from the database? Considering that you will see more table DML claims it will likely be faster to function on INT whereas if any pan-database DMLs claims should be performed, GUID can come handy. Please be aware I'm using MySQL, just just in case whether it matters. Please opine.

I have done that before also it labored effectively: while you explain, utilizing a GUID resulted in we prevented conflicts when merging, say, data in one database with another, and also the int provided us efficient joining etc. I'd never make use of a GUID like a key when you are coping with OLAP, as which will performance.