Search results for query: *

Guys Here is the digest function. CREATE OR REPLACE FUNCTION DIGEST.OMD5 ( p_string IN VARCHAR2 ) RETURN VARCHAR2 AS v_string VARCHAR2(16); v_hexstring VARCHAR2(32); BEGIN v_string := dbms_obfuscation_toolkit.md5(input_string => p_string); v_hexstring :=...

Depends on if you need all data everytime or delta change data and the volumes etc etc. I would consider using transportable tablespaces if your using oracle 8i but there are many ways to achieve this - export/import; scripts etc as I said need to understand the requirements alot more if help...

Which programe are you using to do this ?

The look up code becomes redundant if you implement your surrogate keys as digests of the reference data primary key. Why ? when applying the transaction it is a case of doing the equivilant digest to the fields on the transaction - hence no need for the look up (digest function I have...

surrogate keys do not have to be sequential. They are also known as non-intelligent keys and are keys assigned to records independent of the production code i.e. a product with a SKU of 11234 would be assigned a surrogate key independent of the code 11234 and this would be stored as the unique...