slxdeveloper.com Community Forums

The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!

Administration Forums - Database Administration
Forum to discuss SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to Database Administration | New Thread

View: Search:

Author

Thread: Enforce unique identifiers

P
Posts: 9

Enforce unique identifiers Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 03 Jul 08 9:28 AM

Is there a way to enforce that a field be unique in a table in the SLX db manager? I would like a new field to ensure that each entry is unique, because they recycle numbers on active jobs because the old, old system they use can only hold 100 customers simultaneously. And obviously, any mistakes there would not be fun - so I think enforcing that each number be unique is a good thing.
Thanks,
P

[Reply][Quote]

Phil Parkin
Posts: 819

Re: Enforce unique identifiers Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 03 Jul 08 6:55 PM

Uniqueness at the RDBMS level within a SalesLogix database is enforced only for table IDs - so the answer to your question is no. At least, not via the DB Manager.

But, of course, you can enforce uniqueness through your code. If you have remote users, this becomes 100 times more difficult, but it can still be done.

Phil

[Reply][Quote]

Walter Shpuntoff
Posts: 167

Re: Enforce unique identifiers Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 04 Jul 08 1:49 PM

It sounds like your best bet is allow the job number to be blank at the user level, and have a server side process that assigns it an available number.

As far as methods - you could do that with an Agent, or with one of the 3rd party process managers like Task Centre or KnowledgeSync.

If you do not have remotes, you could get away with a SQL trigger.

Note: all of these are workarounds. As Phil alluded to... having a unique ID is a problem if you have distributed data - that's why SLX embeds site codes in its record keys.

[Reply][Quote]

P
Posts: 9

Re: Enforce unique identifiers Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 07 Jul 08 7:39 AM

Well, I guess I should start working around then. I am glad all the data is centralized (except for the recovery & redundancy of course). Sadly, not all of their ID numbers are unique for my next assignment (still not sure how that happened).
Thanks for the help; I appreciate it.
P

[Reply][Quote]

Dan Carvin
Posts: 227

Re: Enforce unique identifiers Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 07 Jul 08 12:15 PM

Quote:

Originally posted by Phil Parkin

But, of course, you can enforce uniqueness through your code. If you have remote users, this becomes 100 times more difficult, but it can still be done.

If you use the remote user's sitecode as part of the ID (like SLX does when a remote user creates records), then it is less than 100 times more difficult.

[Reply][Quote]

Page 1 of 1

You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 5/21/2024 6:02:59 PM