April 24, 2012 at 5:47 am
[font="Verdana"]Hi Folks,
We do have a new pragmatic software with the front-end technologies as N/Hibernate etc. The team has devised a manual sequence/identity mechanism (physical tables with next ID generation and manual updates) for its transactional tables.
Do any design strategy can be much beneficial than the stated one? but .. keeping in view the nature of N/Hibernate technologies and the strong factor of Migration between Oracle, SQL, MySQL and DB2.
Thank you!
[/font]
April 24, 2012 at 4:42 pm
:blink: what?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.April 24, 2012 at 4:51 pm
Abrar Ahmad_ (4/24/2012)
The team has devised a manual sequence/identity mechanism (physical tables with next ID generation and manual updates) for its transactional tables.
I do hope your team tested that under heavy load. Most of those 'manual identity strategies' are either dead slow or prone to race conditions.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 24, 2012 at 8:59 pm
Abrar Ahmad_ (4/24/2012)
[font="Verdana"]Hi Folks,We do have a new pragmatic software with the front-end technologies as N/Hibernate etc. The team has devised a manual sequence/identity mechanism (physical tables with next ID generation and manual updates) for its transactional tables.
Do any design strategy can be much beneficial than the stated one? but .. keeping in view the nature of N/Hibernate technologies and the strong factor of Migration between Oracle, SQL, MySQL and DB2.
Thank you!
[/font]
I'm sure your users will be very happy when there are 400 people waiting for some blocking transaction to complete so they they can get their next sequence number.
I have never seen what I would call a successful implementation of this strategy. Probably because anyone with the skill needed to pull it off would avoid it like the plague.
April 25, 2012 at 11:13 am
SQL Server & Oracle (I believe DB2 as well) provide the functionality to auto generate the IDs (sequence numbers) which are heavily used by industry. You don’t need to write any logic to generate any ID in your implementation. You just require setting up few flags / indicator in your tool’s metadata to indicate physical implementation. It will generate the DDLs based on the flag and rest of the things will be dependent on database server itself. Most of the tools follow the same strategy.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply