[Serow225]

Sounds like you're off to a good start! :) Getting everything backed up soon is important; if things were implemented marginally, you don't know how long it will run before something crashes or hardware dies. Without a backup, you could then be in a rough spot... Also make sure that you test out the recovery from backup. I think documenting as you go is a great step, and is an easy way to generate a regular status report to show your boss what you've accomplished. You might want to start looking into the hardware that the systems are running on; are they working reliably, is there any redundancy (RAID, multiple servers, etc) and/or spare parts available. Once things are stabilized, I would continue refactoring the databases without making any user-visible changes (besides the improved performance once indexes are added :) Good luck!

[dwd]

Second documenting your accomplishments; remember to phrase them to match your audience, so describing how it measurably benefited the company is better than just the dry description of what you did.

[jdsfighter]

Luckily I've used the backups to setup my testing environment so I know they're good! Can you recommend anything else I should start doing? Development journals? Version control system?

[Serow225]

Another thing I just thought of is a health monitoring suite for your servers/network. Also starting to move towards virtualized servers makes dealing with both failed hardware and testing/rollout/rollback easier.

[jdsfighter]

They are very set in their ways when it comes to their severs, they wont even implement Active Domain services... So virtualization may be out of the question for now.

[Serow225]

Are the servers on any sort of UPS to enable graceful shutdown if power goes out?

[jdsfighter]

Yes, the company I work for is an electrical contracting company, and specifically the branch that I'm working for is based inside a massive data center. So power wise, everything is golden.

[Serow225]

Definitely set up revision control ASAP.

[jdsfighter]

Any recommendations on the best, I have minor experience with SVN, and I've only used GIT for github related stuff. Everything here is windows based, everything. So I was even considering going with TFS, but I also have been thinking about using git out of its simplicity and robustness. Especially since I may be working from multiple computers.

[Serow225]

Well the term 'best' is touchy, but for your use case I'd suggest trying SVN using something like VisualSVN Server and TortoiseSVN for the client(s). Simple to set up, understand and use.