Sponsored Content
Operating Systems Solaris Solaris BigAdmin RSS MySQL Database Scale-out and Replication for High Growth Businesses Post 302257121 by Linux Bot on Tuesday 11th of November 2008 11:50:01 AM
Old 11-11-2008
MySQL Database Scale-out and Replication for High Growth Businesses

This Sun BluePrints paper addresses the primary ways MySQL installations can scale to meet increasing user demands, while still providing the flexibility and ease of use that single installations offer.

More...
 

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Strategical Shell Scripting For MySql Replication

Hi to all guyz , As i'm new to Shell scripting i was been working out to write a shell script for mysql Replication for multiple slave master architecture.i have done the process up with a script of 200 lines but still there are some things which can make my script more effective so i want your... (5 Replies)
Discussion started by: kgrvamsi
5 Replies

2. Linux

Mysql replication

Need to recover a replication broken error on the mysql slave server. I want to force it to resend the binlog file from the begining. What is the correct value for the: MASTER_LOG_POS ? 0, 1 or 107 ? (2 Replies)
Discussion started by: andriesh
2 Replies

3. HP-UX

Database replication process stopped in server

Hi, A database (Oracle) replication process was executed by the DBA team in one server (serverX). However, this replication process gets terminated, and there are no errors in the replication log. But there is error in the OS log files (syslog.log) : Aug 8 16:51:47 L28dre02 sshd: subsystem... (1 Reply)
Discussion started by: anaigini45
1 Replies
Session::Store::MySQL(3)				User Contributed Perl Documentation				  Session::Store::MySQL(3)

NAME
Apache::Session::Store::MySQL - Store persistent data in a MySQL database SYNOPSIS
use Apache::Session::Store::MySQL; my $store = new Apache::Session::Store::MySQL; $store->insert($ref); $store->update($ref); $store->materialize($ref); $store->remove($ref); DESCRIPTION
Apache::Session::Store::MySQL fulfills the storage interface of Apache::Session. Session data is stored in a MySQL database. SCHEMA
To use this module, you will need at least these columns in a table called 'sessions', or another table name if you provide the TableName argument: id char(32) # or however long your session IDs are. a_session text To create this schema, you can execute this command using the mysql program: CREATE TABLE sessions ( id char(32) not null primary key, a_session text ); If you use some other command, ensure that there is a unique index on the table's id column. CONFIGURATION
The module must know what datasource, username, and password to use when connecting to the database. These values can be set using the options hash (see Apache::Session documentation). The options are: DataSource UserName Password TableName Handle Example: tie %hash, 'Apache::Session::MySQL', $id, { DataSource => 'dbi:mysql:database', UserName => 'database_user', Password => 'K00l', TableName => 'sessions' }; Instead, you may pass in an already-opened DBI handle to your database. tie %hash, 'Apache::Session::MySQL', $id, { Handle => $dbh }; AUTHOR
This modules was written by Jeffrey William Baker <jwbaker@acm.org> SEE ALSO
Apache::Session perl v5.12.1 2007-09-28 Session::Store::MySQL(3)
All times are GMT -4. The time now is 03:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy