Database Location?

[PeteCress]

I'd like to move SageTV's database from my system drive to a drive that's dedicated to data.

Not a religious issue or anything - but it seems more sensible to keep data out of the system against the possible need to re-image the system.

Registry pointer? .INI file?

[CollinR]

wiz.bin it's in the install directory and it's path is called in sage.properties so you can move it if you like.

[GKusnick]

The installer makes a backup of Wiz.bin when you upgrade to a new version of Sage, but I'm not sure if this will still happen if you move your Wiz.bin out of the installation directory. Something to consider anyway.

Wherever you keep it, daily backups of Wiz.bin and *.properties are still a good idea.

[Opus4]

Originally Posted by GKusnick

The installer makes a backup of Wiz.bin when you upgrade to a new version of Sage, but I'm not sure if this will still happen if you move your Wiz.bin out of the installation directory.

I think SageTV does this the first time the new version is run, not the installer.

- Andy

[PeteCress]

Originally Posted by CollinR

wiz.bin it's in the install directory and it's path is called in sage.properties so you can move it if you like.

Thanks!

That was totally painless, albit a little unscripted.

I set up a directory S:\SageDB, pointed the .INI file entry to there and copied Wiz.bin there.

When I fired up Sage, an "S:\SageTV" magically appeared and a copy of Wiz.bin appeared within it.

I'm guessing that's what the app is using now be I was able to rename
SageDB to zzSageDB while SageTV was running with no adverse consequences.

Bottom line, I got my DB on a separate drive like I wanted.

Got a little *too* anal, though and moved the recordings to a different directory. Turned out the full path is in the DB instead of a pointer to the parm and the app thought they had disappeared.

As a workaround I just deleted the affected recording entries from the UI, moved the files to my "Imported" directory, and then "Imported" them into the app.

I'm liking these guys at Sage more and more - a little more today upon discovering that they were using text-based parm files instead of the Windows Registry.