I'm not running SC in this environment, so I can be of only limited help
here.  But I will say that my favorite tool for examining processes
under windows is the SystemInternals Process Explorer which is a free
utility available at:
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

I'm not sure about the warning you cite in your server log, but I don't
think it's unusual for stock installs of SC to run MySQL as a spawned
process.  That's the way it seems to work under linux too, I believe.

If you really, really want to run MySQL as a service, rather than as a
child process, download and install the latest free MySQL community
version.  You'll need to configure a password for the mysqld root user.
Also, make sure that Vista's (or whomever's) firewall has tcp port 3306
open.

Then, I'd recommend downloading and installing MySQL-Administrator
which is a great gui admin tool.  Use it to create a MySQL
"squeezecenter" user with "squeezecenter" as a password.  Use
MySQL-Administrator to then create an empty schema named
"squeezecenterdata" and grant all rights to that schema to both root
and the "squeezecenter" user.  Finally, edit your squeezecenter
server.prefs file so that SC looks at your MySQL service:


Code:
--------------------
    
  dbpassword: squeezecenter
  dbsource: dbi:mysql:hostname=127.0.0.1;port=3306;database=squeezecenterdata
  dbusername: squeezecenter
  
--------------------


When you restart SC, it should automatically create all of it's tables
in that schema and populate them by rescanning your music library.

The only other thing I'll say here is that there are some benefits to
using an "external" MySQL in this fashion.  It makes it easier to
experiment with various server variables to try to enhance performance.
Also, it's a little more straight forward under this method if you want
to peek at the SC data using, for instance, an ODBC driver to link SC's
tables to a MS Access database.  If you do want to do that, however,
you'll need to modify SC's tables so that some key columns have a TEXT
datatype rather than BLOB (which the current MySQL ODBC driver seems to
not be able to handle.)  You can perform that little chore using the
MySQL query browser (another good cross-platform qui tool) and the
following query:

Code:
--------------------
    
  ALTER TABLE `squeezecenterdata`.`albums` MODIFY COLUMN `title` TEXT DEFAULT 
NULL;
  ALTER TABLE `squeezecenterdata`.`contributors` MODIFY COLUMN `name` TEXT 
DEFAULT NULL;
  ALTER TABLE `squeezecenterdata`.`genres` MODIFY COLUMN `name` TEXT DEFAULT 
NULL;
  ALTER TABLE `squeezecenterdata`.`tracks` MODIFY COLUMN `title` TEXT DEFAULT 
NULL, ROW_FORMAT = FIXED;
  
--------------------

AFAIK, as long as your music's metadata doesn't contain titles with
asian ideographs, there shouldn't be any downside to using the TEXT
datatype.


-- 
gharris999
------------------------------------------------------------------------
gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115
View this thread: http://forums.slimdevices.com/showthread.php?t=48028

_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta

Reply via email to