08-11-2010 02:55 PM
Upgraded to V7.5.2 from V7.5.1 on an installation that has Scribe running (V6.3.x) on a Windows Server 2003 64 bit server. Once the SLX upgrade took place the Scribe DTSs would take 30-60 minutes to open. Upgraded Scribe to V7.0.1 with the same results. (SLX and Scribe ran fine before the upgrade).
Anyone else having an issue with SLX V7.5.2 and Scribe V7.0.1?
The time to open is dependent upon the number of dblookups() in the DTS. The Scribe Tracking indicates about 2 minutes for each dblookup() to run.
We're suspecting something has changed with the SLX provider that may be an issue.
What's been your experience/solution?
Solved! Go to Solution.
08-11-2010 05:31 PM
Believe we found the issue. There isa customized field in the Address table (address_id) that had null values in over 200K records. When the null was updated to a blank Scribe now runs as usual.
What is it about V7.5.2 that it doesn't like null values? This is exactly the same DTS that ran in V7.5.1 when there were null values in the address_id field.
08-12-2010 05:08 AM
Bruce, this is VERY interesting because the best practices way of handling "empty" (or invalid) values in foreign key fields is to "NULL" them out - not use blank(s).
08-12-2010 05:33 AM
We've ran across this in sever fields regarding a SLX Web Client project too. When the value was null the Group wouldn't load or the form doesn't load (and or is very slow to open). Once we blanked out the field it runs fine.
My concern is with customers entering data moving forward. Will code be needed for the fields to make sure they are blank if a value isn't entered on a new record? Just doesn't make sense to me that SLX or SQL would have a problem with nulls.
09-19-2010 06:24 AM
We had similar issues when upgrading from 6.2.2 to 7.2.2 so it isn't new with 7.5. Specifically, when Network Clients (and to a lesser degree Remote Clients) go into Opportunity Details View with the Notes/History Tab as default, they'd have to wait over a minute before theycould update. Our developer had to replace hundreds of thousands of Null Opportunityids in the History Table with Blanks to remedy the situation. We still have some other response issues in this and other areas we're trying to track down.