+ Post New Thread
Results 1 to 4 of 4
MIS Systems Thread, ATF Import failing with SQL violations in Technical; Any constructive suggestions on how to resolve ATF import problems? The source is Tribal and I seem to recall problems ...
  1. #1
    Rammie's Avatar
    Join Date
    Jan 2007
    Location
    Derby
    Posts
    53
    Thank Post
    8
    Thanked 5 Times in 2 Posts
    Rep Power
    16

    ATF Import failing with SQL violations

    Any constructive suggestions on how to resolve ATF import problems? The source is Tribal and I seem to recall problems with this in the past, although I can't seem to locate the thread. Specifically, I've already fixed a number of issues with contact phone numbers exceeding the field length and I've also located a number of duplicate parental mother records (PAM) attributed to different contacts. This has removed all of the explicit error reports except some final fatal SQL-related errors ('UNIQUE KEY' and a number of 'Cannot insert NULL' errors). I won't bore you with the detail unless someone thinks it's useful. Currently, we're trying to use SQL debugger to identify what data is triggering the error. PS - doesn't say much for validation, does it?

  2. #2

    matt40k's Avatar
    Join Date
    Jun 2008
    Location
    Ipswich
    Posts
    4,391
    Thank Post
    368
    Thanked 637 Times in 519 Posts
    Rep Power
    158
    Sounds like a duff export.

  3. #3

    Join Date
    Aug 2011
    Posts
    21
    Thank Post
    4
    Thanked 7 Times in 6 Posts
    Rep Power
    8
    We're a school in Derby too and had issues importing our ATF file, the main one being about a Unique Key, our SIMS support team passed our ATF file to Capita who said the contacts in the file were a mess. I ended up removing all the contact details and importing the ATF without them, we'll import contact details through CTF files which we will get from the primary schools.

  4. Thanks to wpjon from:

    Rammie (25th April 2012)

  5. #4
    Rammie's Avatar
    Join Date
    Jan 2007
    Location
    Derby
    Posts
    53
    Thank Post
    8
    Thanked 5 Times in 2 Posts
    Rep Power
    16
    We've resolved it now. Thanks, wpjon, it's "reassuring" to discover someone else has experienced the same problem from (presumably) the same Tribal source. We had seriously considered dumping all the contact information, until the SQL debugging revealed the source of the problem. It looks like the SIMS contact pattern matching algorithm is sensitive to gender problems. Specifically, if it matches a contact on name etc and tries to update the record, the import will fall over if the gender doesn't match. Clearly the root cause is a discrepancy in the gender information somewhere or other (could be in the existing record or in the ATF file). Our fix is to remove all the contact gender information and we then successfully imported the file.

SHARE:
+ Post New Thread

Similar Threads

  1. Help With SQL Query Error
    By penfold_99 in forum Coding
    Replies: 6
    Last Post: 15th May 2009, 01:30 PM
  2. Getting in a muddle with SQL Server
    By sidewinder in forum Windows
    Replies: 1
    Last Post: 17th November 2008, 02:43 PM
  3. SIMS Backups with SQL 2005
    By WithoutMotive in forum MIS Systems
    Replies: 5
    Last Post: 17th January 2008, 09:55 AM
  4. ID Cards with SQL 2005
    By hayjo86 in forum MIS Systems
    Replies: 2
    Last Post: 20th December 2007, 10:34 AM
  5. SIMS communication with SQL server
    By dhicks in forum MIS Systems
    Replies: 9
    Last Post: 14th December 2007, 09:05 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •