Comments on: Numbering Existing Records https://servicenowguru.com/scripting/numbering-existing-records/ ServiceNow Consulting Scripting Administration Development Tue, 28 May 2024 21:25:20 +0000 hourly 1 https://wordpress.org/?v=6.8.2 By: Mark Stanger https://servicenowguru.com/scripting/numbering-existing-records/#comment-6959 Mon, 04 Oct 2010 08:01:32 +0000 https://servicenowguru.wpengine.com/?p=1623#comment-6959 You might get a better response to this on the forums, but I’ll give you my opinion. My first thought is that you’ll still have users living in the global domain. For these users, you will have tickets with duplicate numbers that they will have to sort though — unless you set up your number separation so that each version of numbering on a table would have a different prefix or something. Even if you chose that route, it could be a nightmare to manage.

My second thought is that you’ve got an infinite supply of numbers for any given table. Because of this, there should be no need to further confuse the issue by domain-separating that table. A lot of people (maybe not you) get hung up about wasted numbers and numbers not following an exact sequence but I have yet to hear a real compelling argument for preventing ‘number waste’ :).

I’ve never tried to do what you’re asking about (somebody on the forums may have) but I can see some potential issues with doing it and see no reason to believe that domain-separating the sys_number table would provide a real benefit. If it were me I’d just make sure that my numbers had enough padding to not run out and forget the separation.

]]> By: Mike Flora https://servicenowguru.com/scripting/numbering-existing-records/#comment-6958 Mon, 04 Oct 2010 07:42:46 +0000 https://servicenowguru.wpengine.com/?p=1623#comment-6958 Do you see any ill-effects of domain separating the sys_number table in an MSP environment?

Thanks

]]>