Tuesday, May 24, 2005

Documentation

That _admin directory is a bounty of goodness. I've managed to get my directory-quota tracker down in the majority, now its experiencing minor tweaks as I figure out the best way to run reports and how to gather the data itself. Since this data doesn't change much from day-to-day, it'll be a week or three before we get enough data to do usability thingies with it.

Meanwhile, there are a couple of other projects I can set my mind to. Tracking of Trustee assignments would be nifty from an auditing and documentation point of view. Re-rigging my disk-space tracker to use the database instead of the SQL would be a perfectly useful thing to do, especially since it was originally developed with a DB as a back-end anyway.

However, I'm running into a perl issue. The disk-space tracker was written in perl and works great from there. Worked great at OldJob, and is probably still working great as I type; it has data back to 1999 in that table. For some reason, the Perl DBI modules for SQL-server aren't working well for me.

In order to improve space usage in the database and to better link the various tables together, I have a central lookup table.


UniqueIDInt







Servervarchar







Volumevarchar





Since the key bit of data all that stuff in _admin lacks is what server and volume we're talking about, I need to provide that link when I drop stuff in the database. The field-list for the volume disk-space tracker I have looks like this:

DateTime, VolServID(FK: UniqueID), TotSpace, FreeSpace, UsedSpace

What this means is that the data-gathering script needs to figure out what UniqueID to use for the Server/Volume combination it just queried. This is part of where my problem seems to lay. For reasons unknown to me, find-unique-ID part works great, but the INSERT to the freespace table freezes as I bind parameters. And the freeze happens in the DBI code itself, not my code, and it isn't giving me useful trace info. This is why I ended up using C# for the quota-tracker, by the way. I don't want to port this script into C# since that means learning how to do SNMP in C#, and I sense pain ahead.

Comments: Post a Comment

<< Home

This page is powered by Blogger. Isn't yours?