No new Availibilty Statistics after manual insert of rows into ResponseTime_Detail table.

Got it working by renaming the old table and let Configuration Wizard create it new with DB repair.

Next problem...how do I get my historical data back in the working table (92m rows)? Or maybe the old table is repairable and I can just amend the newly gathered data from the newer table ResponseTime_Detail.

At the end it would be very interesting what happened in the first place as I can see no real difference between these tables...except for the row count.

It's some referential thing, almost has to be. What could have caused issues, I can't imagine. Were you just not seeing any new rows or did you have some errors being kicked out by the database?

must be referential. It was just not adding new rows to ResponseTime_Detail, no errors were logged. it kept filling the other tables like interface utilization. all very strange - would be interesting what a SW developer thinks about it...

I have a gig coming up that's going to require doing a bit of old history merging after a migration, so I'll keep you updated. I would have done the same thing, being the off roader I am, but now it seems a little research is in order. =)

I also think that shutting down NPM before doing the INSERT might have helped, but I have no test-system to proof that.

Haha, yeah--applications don't dig that much. I wonder if there's some last_id somewhere (which would be tragic) that needs a kick. It's a primary key though, no need for that.

that might work...

Shutdown NPM - extract the rows from the new and working table - insert the rows into the not working table - rename the table and PK to ResponseTime_Detail again - start NPM

The last row should then be the same as in the working table and NPM should see no difference - hopefully.

set up a testsystem and tried - no success. npm couldn't write into ResponseTime_Detail after restart.

I think, I'd need to know what NPM is checking in the table in order to continue writing records.

got it working:

Shut NPM

bulk insert ResponseTime_Detail from 'c:\File.csv'

with (
  check_constraints,
  Firstrow=2,
  Fieldterminator=',',
  Rowterminator='\n',
  keepidentity,
  keepnull,
  fire_triggers
  
 )  

Start NPM and it continued to write again into the table.

I think the "check_constraints" did the trick. Now I only have to figure out how to handle the insert of 92mio rows.

Nice one! Thanks for updating the thread with the results.