You can take care of it by adding a trigger and updating the new field yourself. You might maintain your own transaction ID's using a separate table that held the incremental counts of each transaction type.
More info if needed.
Thanks - the reason I want to do create the additional auto-incremeted field to generate random integer or varchar fields which will serve as passwords. This may sound somewhat clugy, but seems to be the quickest/easiest way to assign simple passwords to 100+ records. So I can't really use the first one (id) for both - ideally it would be at least a 4 digit field. I obviously don't live in sql, am pretty new so pardon me asking what if "aou" is the same thing as Auto Incremented identity seed, or something else?
1) Please post new questions in a new thread.
2) The documentation for SQL Server is called SQL Books Online or SQL BOL. Open the documentation to the topic "Create Trigger." Read faq183-689- "What are SQL Books Online & Where Can I Find Them?" Terry L. Broadbent - DBA
SQL Server Page:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.