Hi
I'm trying to set up regular update statics. Due to some problems we had in the past, I have to first make a backup of the statistics, prior to the update, and I also want to do update statistics on backup server and transfer them to the primary server (we have a warm-standby enviroment).
Now, I know I can use optdiag to do the backup and transfering between servers, but that requires sso_role, which I don't have.
So, I wanted to make a table copy of sysstatistics, (named sysstatistics_backup) and system procedure, that would delete sysstatistics and insert there data from sysstatistics_backup, so I could use it either for loading old statistics or to transfer them to primary server (I can get our sso to turn on allow updates to system tables when i create the proc, but I can't make him to transfer the stats via optdiag every week).
But the first hurdle, when i do
select * into sysstatistics_backup from sysstatistics
i get
Warning: Row size (20706 bytes) could exceed row size limit, which is 1964 bytes.
and when i compare the data in the two tables, they are not the same.
My question : how come the rows in sysstatistics are wider than server page and can I somehow achieve the same thing for my backup table?
Or, am I doing the whole thing wrong and there is some other way to do, what I want to do?
Adaptive Server Enterprise/15.0.3/EBF 17770 ESD#4/P/x86_64/Enterprise Linux/ase1503/2768/64-bit/FBO/Thu Aug 26 09:54:27 2010
2k page size
Thanks
Karel