07-26-2012 04:26 AM
Ok Thanks to the guys in support for assisting on this one -- Turns out there will be a new Knowledgebase article shortly..
The issue was that Foreign Keys had been setup on the UserInfo and UserSecurity tables. These keys were what was causing the issue. Thanks again to Dan Johnson and Scott..
07-26-2012 04:53 AM
Just did a detailed look at the trace and I do not see any custom fields/FK's in it for those tables:
2012/07/25 21:22:02.267 USER 0.1813 0.0475 0.0036 0.0000 0.0000 0.0000 0 Admin 2264 1. 0. 0.127
FORWARD ONLY INSERT INTO USERSECURITY (USERID, USERCODE, TYPE, DEFAULTSECCODEID, ENABLED, ISMANAGER, ADDMEMBERS, DELMEMBERS, CREATETEAMS, MANAGERID, LASTRNFILE, PRIVATEACCOUNTID, SUPPORTUSER, USERTEMPLATE) VALUES ('U6UJ9A00018T', 'user0001', 'N', 'N6UJ9A00017H', 'T', 'F', 'N', 'N', 'N', 'ADMIN', 0, '', 'F', '')
2012/07/25 21:22:05.943 USER 0.1123 0.0352 0.0036 0.0000 0.0000 0.0000 0 Admin 2264 1. 0. 0.127
FORWARD ONLY INSERT INTO USERINFO (USERID, USERNAME, LASTNAME, ADDRESSID, HOMEADDRESSID, AVAILABLE, TIMEZONE) VALUES ('U6UJ9A00018T', '<NewUser>', '<NewUser>', 'a6UJ9A009P42', 'a6UJ9A009P43', 'T', 'Singapore Standard Time')
2012/07/25 21:22:06.202 USER 0.1268 0.0355 0.0036 0.0000 0.0000 0.0000 0 Admin 2264 1. 0. 0.127
FORWARD ONLY INSERT INTO USERSECURITY (USERPW,PWCHANGEDATE) VALUES ([DBTYPE_STR,"BA5E89A957F769EB60A1F0291D68BE8BE13B1A0A1A0A1B0377C2D4A18B92F3"],[DBTYPE_DBTIMESTAMP,20120725 13:22:07.000])
07-26-2012 05:04 AM
Adam, they were added by our DBA's who were helping to increase the performance.. sigh
RJ -- the way they were found was by taking the failed SQL statement from the profiler and then trying to run it in the Admin through Execute SQL..
It generated the error about the FK which is how we found it. Once we changed one it then errored on the second one.. once they were removed everythiong went clean.
07-26-2012 06:47 AM
IMHO - It never ceases to amaze me how dba's (who have little or no knowledge of SalesLogix) will do things like this rather than asking someone who really knows what is "under the hood".
Time was lost, people had to spin their wheels, etc... red flags raised.. money wasted..
Saleslogix is NOT a "simple db app". It is a highly sophisticated forward moving transactional Enterprise level application which requires a working (not just "head knowledge") skill set to do things like improving performance, etc.
Let us hope the user community (and partners) take this as an opportunity to learn from.