Source of Numbers that does not drop
‎Jun 23, 2014
04:09 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
‎Jun 23, 2014
04:09 PM
Source of Numbers that does not drop
Has anyone had success with setting up a Number Sequence (or other source of Numbers) that does not drop numbers or otherwise create gaps as the OOTB Number Sequences do? I get that for the most part, the primary function of Number is to guarantee uniqueness, but there are some use cases where gaps in the Number Sequence is a factor in usability (mostly User perception).
Labels:
- Labels:
-
Other
3 REPLIES 3
‎Jun 23, 2014
04:16 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
‎Jun 23, 2014
04:16 PM
Method Servers cache blocks of numbers. When they are shutdown or whatever else, those numbers are thrown out. Causes big gaps. You can turn off the caching. Its technically there for performance reasons though if the demand isn't that high, I would certainly give it a try. Won't remove the gaps entirely but it will lessen them.
[cid:image001.gif@01CF7046.C96AB930]
Stephen Vinyard
Business Development Manager/Solution Architect
[cid:image001.gif@01CF7046.C96AB930]
Stephen Vinyard
Business Development Manager/Solution Architect
‎Jun 23, 2014
05:45 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
‎Jun 23, 2014
05:45 PM
All Windchill sequences are created from the Windchill Solution Installer.
Hard to understand why PTC does not fix this fundamental issue. At a minimum it should be documented in 64 FONT, Red, how to do so.
Each has SQL somewhat like this.
[cid:image001.png@01CF8EF1.CAA1FD30]
You have to one by one change each sequence to NO_CACHE.
[cid:image002.png@01CF8EF1.CAA1FD30]
[cid:image003.png@01CF8EF1.CAA1FD30]
Hard to understand why PTC does not fix this fundamental issue. At a minimum it should be documented in 64 FONT, Red, how to do so.
Each has SQL somewhat like this.
[cid:image001.png@01CF8EF1.CAA1FD30]
You have to one by one change each sequence to NO_CACHE.
[cid:image002.png@01CF8EF1.CAA1FD30]
[cid:image003.png@01CF8EF1.CAA1FD30]
‎Jun 23, 2014
09:45 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
‎Jun 23, 2014
09:45 PM
Group,
I seemed to have no issue with this command (with syntax as shown in Mike's screenshot) to create my custom sequence:
create sequence TEST_REQUEST_SEQ_FY14 increment by 1 nocache;
The key was adding the operator nocache. Of course this goes against PTC's suggestion of how to create a custom sequence:
exec wtpk.createSequence('TEST_REQUEST_SEQ_FY14',1,1)
Ben
[cid:image001.jpg@01CF8F24.18D96A10]
I seemed to have no issue with this command (with syntax as shown in Mike's screenshot) to create my custom sequence:
create sequence TEST_REQUEST_SEQ_FY14 increment by 1 nocache;
The key was adding the operator nocache. Of course this goes against PTC's suggestion of how to create a custom sequence:
exec wtpk.createSequence('TEST_REQUEST_SEQ_FY14',1,1)
Ben
[cid:image001.jpg@01CF8F24.18D96A10]