I'm the DBA of a firm that's running Orion 8.1.0 in a dev enviroment - a virtual 64-bit sql server 2005 instance - before moving it to our prod database server. We started with MSDE, but Orion quickly outstripped the capabilities of that (at which point I became involved).
We're having trouble, right now, with the Syslog service - it's not appropriately trimming the SysLog table to the 3 days retention we have it set for. I've restarted all of the services, changed the rentention value, and restarted the server, all to no effect - I still have to manually trim the table every few days so it doesn't grow too large, and I'm unwilling to move the db to our prod server until we can resolve this issue; I don't want to be manually hacking at the db every few days. Of course I could schedule a job of my own to take care of this, but I'm curious why the built-in functionality's not working as advertised. Even with nothing but the Syslog service running none of the too-old rows are being removed.
Has anyone else seen this?
This should be fixed in 8.5, which is due out in a few weeks.
I gather the fix isn't in one of the hotfixes, so I guess I'll wait ;)
Thanks!