RE: MSSQL-MySQL Compatibility Question
Thanks guys! J.R. -Original Message- From: JamesDR [mailto:[EMAIL PROTECTED] Sent: Thursday, October 27, 2005 9:21 AM To: mysql@lists.mysql.com Subject: Re: MSSQL-MySQL Compatibility Question J.R. Bullington wrote: > Hi All, > Quick question -- I have a client who co-owns a server with me. I am > a die-hard MySQL guy, they are MSSQL. They have some proprietary > Access-frontend/MSSQL-backend financial system that they want to > continue to use (i.e. pigheaded and won't convert). > > Can MS-SQL and MySQL run on the same box and not conflict with each > other? I don't have the SQL disks in front of me to test and I was > wondering if anyone else ran into this situation. > > Box is a Quad Xeon 2.0GHz, 1GB RAM, 80GB Ultra3 SCSI Raid. > > Thanks! > J.R. > I have MSSQL + MySQL on the same box here, no issues with that... My server is hardly "Big Iron" or "Small Iron" by any reach: P3 933 1GB Ram, SCSI160 non-raid ;-D More memory, if you can do it, is better... (roll on new server...) Best thing to look at is your current load, if you are pushing the limits, adding another RDBMS may cripple that box. As far as negative interaction, I've seen none. -- Thanks, James -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MSSQL-MySQL Compatibility Question
J.R. Bullington wrote: Hi All, Quick question -- I have a client who co-owns a server with me. I am a die-hard MySQL guy, they are MSSQL. They have some proprietary Access-frontend/MSSQL-backend financial system that they want to continue to use (i.e. pigheaded and won't convert). Can MS-SQL and MySQL run on the same box and not conflict with each other? I don't have the SQL disks in front of me to test and I was wondering if anyone else ran into this situation. Box is a Quad Xeon 2.0GHz, 1GB RAM, 80GB Ultra3 SCSI Raid. Thanks! J.R. I have MSSQL + MySQL on the same box here, no issues with that... My server is hardly "Big Iron" or "Small Iron" by any reach: P3 933 1GB Ram, SCSI160 non-raid ;-D More memory, if you can do it, is better... (roll on new server...) Best thing to look at is your current load, if you are pushing the limits, adding another RDBMS may cripple that box. As far as negative interaction, I've seen none. -- Thanks, James -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MSSQL-MySQL Compatibility Question
Yeah, it's perfectly ok to run both on the same machine at the same time, though with MS SQL you're limited to Microsoft OS. -- Alexey Polyakov -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MSSQL-MySQL Compatibility Question
Hi All, Quick question -- I have a client who co-owns a server with me. I am a die-hard MySQL guy, they are MSSQL. They have some proprietary Access-frontend/MSSQL-backend financial system that they want to continue to use (i.e. pigheaded and won't convert). Can MS-SQL and MySQL run on the same box and not conflict with each other? I don't have the SQL disks in front of me to test and I was wondering if anyone else ran into this situation. Box is a Quad Xeon 2.0GHz, 1GB RAM, 80GB Ultra3 SCSI Raid. Thanks! J.R.
Re: msSQL <-> MySQL (exhanging data between the two)
I haven't tried, but it seems quite difficult, for one thing, both sql engines are very differents. So the short answer would be a plain no. Now trying something exotic would be making a odbc bridge between the two dbs and then use some scripted solution it would be possible, something like java or c# or even vb(.net), even perl or php could be used, but again it is something that you should find out for your self. When deciding about what programming language one key comoponent should be that the language has native access to both server (php? perl?) so type coneversion would be easy to manage. But again it's just a thought... My two cents! =) maybe someone else here could have better ideas-options Best Regards On Thu, 2004-03-04 at 16:26, Daniel Ek wrote: > Once more - Dear list, > > I am doing some research on a CRM-tool which my company bought that uses > msSQL. > > The setup looks something like this > > User --> CRM --> MsSQL } > User --> Webform --> MySQL } The same data entered > > What would be optimal is if would be possible, that when a user requests > data through the CRM that it actually uses MySQL connections. > Unfortunately I speaked to the software vendor about it and they said > that it was not an option at the moment. > > My question then is if MySQL could replicate data with MsSQL as master > as following setup: > > User -> CRM -> MsSQL (<)--> MySQL --> Apps that relies on MySQL data > > I would be thankful to any comments and/or suggestions I can get > > Regards > > Daniel Ek -- |...| | _ _|Victor Medina M | |\ \ \| | _ \ / \ |Linux - Java - MySQL | | \ \ \ _| | |_) / _ \ |Dpto. Sistemas - Ferreteria EPA | | / / / |___| __/ ___ \ |[EMAIL PROTECTED] | |/_/_/|_|_| /_/ \_\|ext. 325 - Tél: +58-241-8507325 | ||geek by nature - linux by choice | |...|
msSQL <-> MySQL (exhanging data between the two)
Once more - Dear list, I am doing some research on a CRM-tool which my company bought that uses msSQL. The setup looks something like this User --> CRM --> MsSQL } User --> Webform --> MySQL } The same data entered What would be optimal is if would be possible, that when a user requests data through the CRM that it actually uses MySQL connections. Unfortunately I speaked to the software vendor about it and they said that it was not an option at the moment. My question then is if MySQL could replicate data with MsSQL as master as following setup: User -> CRM -> MsSQL (<)--> MySQL --> Apps that relies on MySQL data I would be thankful to any comments and/or suggestions I can get Regards Daniel Ek -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: msSQL-MySQL
Hello
Try SQLyog at http://www.webyog.com/sqlyog. You will
find a good tutorial out here
http://www.devshed.com/Server_Side/MySQL/SQLyog/page1.html
HTH...KARAM
--- Karma Dorji <[EMAIL PROTECTED]> wrote:
> Is there is utility which is free to convert ms SQL
> 7.0 running on windows
> NT into a mySQL format, i would be very grateful if
> someone in here could
> help me out.
>
> Thanks.
> Karma
>
>
>
> - Original Message -
> From: "Heikki Tuuri" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 06, 2003 2:53 PM
> Subject: Re: start innodb without transactions
>
>
> > Carlos,
> >
> > please send me your my.cnf. How big is the
> combined size of your log
> files?
> >
> > "
> > MySQL/InnoDB-4.0.9, January 14, 2003
> >
> > Fixed a bug: if the combined size of InnoDB log
> files was >= 2 GB in a
> > 32-bit computer, InnoDB would write log in a wrong
> position. That could
> make
> > crash recovery and InnoDB Hot Backup to fail.
> > "
> >
> > In the first printout:
> >
> > > InnoDB: Starting log scan based on checkpoint at
> > > InnoDB: log sequence number 13 1000286684
> > > InnoDB: Doing recovery: scanned up to log
> sequence number 13 1000286208
> >
> > looks like InnoDB is not able to scan the log file
> at all, not even up to
> > the checkpoint!
> >
> > > InnoDB: log sequence number 13 1002344016
> > > InnoDB: Doing recovery: scanned up to log
> sequence number 13 1002343936
> >
> > The same in the next printout. It has written some
> 2 MB more log but
> cannot
> > after a crash scan the log at all!
> >
> > The failing assertion checks when freeing a BLOB
> or TEXT field that its
> > length is right:
> >
> > if (extern_len - part_len == 0) {
> > ut_a(next_page_no ==
> FIL_NULL);
> > }
> >
> > This could be:
> >
> > 1) a bug in InnoDB's log writing;
> > 2) hardware fault, broken disk;
> > 3) serious corruption of the OS file system.
> >
> > If InnoDB fails to scan lots of log in crash
> recovery, it means that the
> > resulting database may have very extensive
> corruption. That can explain
> why
> > some of your tables are not visible at all.
> >
> > There is little hope of recovering your tables.
> You should resort to a
> > backup and upgrade to 4.0.13. Then do some heavy
> processing, for example,
> a
> > table import, and crash mysqld artificially by
> >
> > killall -9 mysqld
> >
> > Look then if InnoDB is able to scan the log in
> crash recovery.
> >
> > Best regards,
> >
> > Heikki Tuuri
> > Innobase Oy
> > http://www.innodb.com
> > Transactions, foreign keys, and a hot backup tool
> for MySQL
> > Order MySQL technical support from
> https://order.mysql.com/
> >
> >
> >
> > - Original Message -
> > From: ""Carlos Proal"" <[EMAIL PROTECTED]>
> > Newsgroups: mailing.database.mysql
> > Sent: Friday, June 06, 2003 7:41 AM
> > Subject: Re: start innodb without transactions
> >
> >
> > >
> > > Probably i need to describe the whole story:
> > > I did a huge insert, a file about 100Mb, and
> mysql crashed/restarted,
> the
> > > err file showed:
> > >
>
--
> > > 030605 12:11:59 mysqld restarted
> > > 030605 12:12:00 InnoDB: Database was not shut
> down normally.
> > > InnoDB: Starting recovery from log files...
> > > InnoDB: Starting log scan based on checkpoint at
> > > InnoDB: log sequence number 13 1000286684
> > > InnoDB: Doing recovery: scanned up to log
> sequence number 13 1000286208
> > > InnoDB: Last MySQL binlog file position 0
> 756499, file name
> > > ./catarina-bin.057
> > > 030605 12:12:01 InnoDB: Flushing modified pages
> from the buffer pool...
> > > 030605 12:12:01 InnoDB: Started
> > > /centia01/final/database/mysql/libexec/mysqld:
> ready for connections
> > > 030605 12:14:01 InnoDB: Out of memory in
> additional memory pool.
> > > InnoDB: InnoDB will start allocating memory from
> the OS.
> > > InnoDB: You may get better performance if you
> configure a bigger
> > > InnoDB: value in the MySQL my.cnf file for
> > > InnoDB: innodb_additional_mem_pool_size.
> > > mysqld got signal 10;
> > > This could be because you hit a bug. It is also
> possible that this
> binary
> > > or one of the libraries it was linked against is
> corrupt, improperly
> > built,
> > > or misconfigured. This error can also be caused
> by malfunctioning
> > hardware.
> > > We will try our best to scrape up some info that
> will hopefully help
> > > diagnose
> > > the problem, but since we have already crashed,
> something is definitely
> > > wrong
> > > and this may fail.
> > >
> > > key_buffer_size=67104768
> > > read_buffer_size=131072
> > > sort_buffer_size=524280
> > > max_used_connections=4
> > > max_connections=500
> > > threads_connected=4
> > > It is possible that mysqld could use up to
> > > key_buffer_size + (read_buffer_size +
> sort_buffer_size)*max_connections
> =
> > > 385528
> > > K
> > > bytes of memory
> > > Hope that's ok; if not, decrease so
RE: msSQL-MySQL
Take a look at SQLyog http://www.webyog.com/
It has a pretty solid import utility for importing from databases such
as SQL server.
Regards,
Mike Hillyer
www.vbmysql.com
-Original Message-
From: Karma Dorji [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2003 3:34 AM
To: [EMAIL PROTECTED]
Subject: msSQL-MySQL
Is there is utility which is free to convert ms SQL 7.0 running on
windows
NT into a mySQL format, i would be very grateful if someone in here
could
help me out.
Thanks.
Karma
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 2:53 PM
Subject: Re: start innodb without transactions
> Carlos,
>
> please send me your my.cnf. How big is the combined size of your log
files?
>
> "
> MySQL/InnoDB-4.0.9, January 14, 2003
>
> Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a
> 32-bit computer, InnoDB would write log in a wrong position. That
could
make
> crash recovery and InnoDB Hot Backup to fail.
> "
>
> In the first printout:
>
> > InnoDB: Starting log scan based on checkpoint at
> > InnoDB: log sequence number 13 1000286684
> > InnoDB: Doing recovery: scanned up to log sequence number 13
1000286208
>
> looks like InnoDB is not able to scan the log file at all, not even up
to
> the checkpoint!
>
> > InnoDB: log sequence number 13 1002344016
> > InnoDB: Doing recovery: scanned up to log sequence number 13
1002343936
>
> The same in the next printout. It has written some 2 MB more log but
cannot
> after a crash scan the log at all!
>
> The failing assertion checks when freeing a BLOB or TEXT field that
its
> length is right:
>
> if (extern_len - part_len == 0) {
> ut_a(next_page_no == FIL_NULL);
> }
>
> This could be:
>
> 1) a bug in InnoDB's log writing;
> 2) hardware fault, broken disk;
> 3) serious corruption of the OS file system.
>
> If InnoDB fails to scan lots of log in crash recovery, it means that
the
> resulting database may have very extensive corruption. That can
explain
why
> some of your tables are not visible at all.
>
> There is little hope of recovering your tables. You should resort to a
> backup and upgrade to 4.0.13. Then do some heavy processing, for
example,
a
> table import, and crash mysqld artificially by
>
> killall -9 mysqld
>
> Look then if InnoDB is able to scan the log in crash recovery.
>
> Best regards,
>
> Heikki Tuuri
> Innobase Oy
> http://www.innodb.com
> Transactions, foreign keys, and a hot backup tool for MySQL
> Order MySQL technical support from https://order.mysql.com/
>
>
>
> - Original Message -
> From: ""Carlos Proal"" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.mysql
> Sent: Friday, June 06, 2003 7:41 AM
> Subject: Re: start innodb without transactions
>
>
> >
> > Probably i need to describe the whole story:
> > I did a huge insert, a file about 100Mb, and mysql
crashed/restarted,
the
> > err file showed:
> > --
> > 030605 12:11:59 mysqld restarted
> > 030605 12:12:00 InnoDB: Database was not shut down normally.
> > InnoDB: Starting recovery from log files...
> > InnoDB: Starting log scan based on checkpoint at
> > InnoDB: log sequence number 13 1000286684
> > InnoDB: Doing recovery: scanned up to log sequence number 13
1000286208
> > InnoDB: Last MySQL binlog file position 0 756499, file name
> > ./catarina-bin.057
> > 030605 12:12:01 InnoDB: Flushing modified pages from the buffer
pool...
> > 030605 12:12:01 InnoDB: Started
> > /centia01/final/database/mysql/libexec/mysqld: ready for connections
> > 030605 12:14:01 InnoDB: Out of memory in additional memory pool.
> > InnoDB: InnoDB will start allocating memory from the OS.
> > InnoDB: You may get better performance if you configure a bigger
> > InnoDB: value in the MySQL my.cnf file for
> > InnoDB: innodb_additional_mem_pool_size.
> > mysqld got signal 10;
> > This could be because you hit a bug. It is also possible that this
binary
> > or one of the libraries it was linked against is corrupt, improperly
> built,
> > or misconfigured. This error can also be caused by malfunctioning
> hardware.
> > We will try our best to scrape up some info that will hopefully help
> > diagnose
> > the problem, but since we have already crashed, something is
definitely
> > wrong
> > and this may fail.
> >
> > key_buffer_size=67104768
> > read_buff
Re: msSQL-MySQL
Oooh, just dawned on my. On the windows side there is a gui front end
called mysqlfront which uses ODBC to talk to multiple databases. It will
pull the data from a mssql server and move it to a mysql server. I haven't
used it against a mssql server, but I did use it against an access database
and it worked quite well.
Curtis
Karma Dorji said:
> Is there is utility which is free to convert ms SQL 7.0 running on
> windows NT into a mySQL format, i would be very grateful if someone in
> here could help me out.
>
> Thanks.
> Karma
>
>
>
> - Original Message -
> From: "Heikki Tuuri" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 06, 2003 2:53 PM
> Subject: Re: start innodb without transactions
>
>
>> Carlos,
>>
>> please send me your my.cnf. How big is the combined size of your log
> files?
>>
>> "
>> MySQL/InnoDB-4.0.9, January 14, 2003
>>
>> Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a
>> 32-bit computer, InnoDB would write log in a wrong position. That
>> could
> make
>> crash recovery and InnoDB Hot Backup to fail.
>> "
>>
>> In the first printout:
>>
>> > InnoDB: Starting log scan based on checkpoint at
>> > InnoDB: log sequence number 13 1000286684
>> > InnoDB: Doing recovery: scanned up to log sequence number 13
>> > 1000286208
>>
>> looks like InnoDB is not able to scan the log file at all, not even up
>> to the checkpoint!
>>
>> > InnoDB: log sequence number 13 1002344016
>> > InnoDB: Doing recovery: scanned up to log sequence number 13
>> > 1002343936
>>
>> The same in the next printout. It has written some 2 MB more log but
> cannot
>> after a crash scan the log at all!
>>
>> The failing assertion checks when freeing a BLOB or TEXT field that
>> its length is right:
>>
>> if (extern_len - part_len == 0) {
>> ut_a(next_page_no == FIL_NULL);
>> }
>>
>> This could be:
>>
>> 1) a bug in InnoDB's log writing;
>> 2) hardware fault, broken disk;
>> 3) serious corruption of the OS file system.
>>
>> If InnoDB fails to scan lots of log in crash recovery, it means that
>> the resulting database may have very extensive corruption. That can
>> explain
> why
>> some of your tables are not visible at all.
>>
>> There is little hope of recovering your tables. You should resort to a
>> backup and upgrade to 4.0.13. Then do some heavy processing, for
>> example,
> a
>> table import, and crash mysqld artificially by
>>
>> killall -9 mysqld
>>
>> Look then if InnoDB is able to scan the log in crash recovery.
>>
>> Best regards,
>>
>> Heikki Tuuri
>> Innobase Oy
>> http://www.innodb.com
>> Transactions, foreign keys, and a hot backup tool for MySQL
>> Order MySQL technical support from https://order.mysql.com/
>>
>>
>>
>> - Original Message -
>> From: ""Carlos Proal"" <[EMAIL PROTECTED]>
>> Newsgroups: mailing.database.mysql
>> Sent: Friday, June 06, 2003 7:41 AM
>> Subject: Re: start innodb without transactions
>>
>>
>> >
>> > Probably i need to describe the whole story:
>> > I did a huge insert, a file about 100Mb, and mysql
>> > crashed/restarted,
> the
>> > err file showed:
>> > --
>> > 030605 12:11:59 mysqld restarted
>> > 030605 12:12:00 InnoDB: Database was not shut down normally.
>> > InnoDB: Starting recovery from log files...
>> > InnoDB: Starting log scan based on checkpoint at
>> > InnoDB: log sequence number 13 1000286684
>> > InnoDB: Doing recovery: scanned up to log sequence number 13
>> > 1000286208 InnoDB: Last MySQL binlog file position 0 756499, file
>> > name
>> > ./catarina-bin.057
>> > 030605 12:12:01 InnoDB: Flushing modified pages from the buffer
>> > pool... 030605 12:12:01 InnoDB: Started
>> > /centia01/final/database/mysql/libexec/mysqld: ready for connections
>> > 030605 12:14:01 InnoDB: Out of memory in additional memory pool.
>> > InnoDB: InnoDB will start allocating memory from the OS.
>> > InnoDB: You may get better performance if you configure a bigger
>> > InnoDB: value in the MySQL my.cnf file for
>> > InnoDB: innodb_additional_mem_pool_size.
>> > mysqld got signal 10;
>> > This could be because you hit a bug. It is also possible that this
> binary
>> > or one of the libraries it was linked against is corrupt, improperly
>> built,
>> > or misconfigured. This error can also be caused by malfunctioning
>> hardware.
>> > We will try our best to scrape up some info that will hopefully help
>> > diagnose
>> > the problem, but since we have already crashed, something is
>> > definitely wrong
>> > and this may fail.
>> >
>> > key_buffer_size=67104768
>> > read_buffer_size=131072
>> > sort_buffer_size=524280
>> > max_used_connections=4
>> > max_connections=500
>> > threads_connected=4
>> > It is possible that mysqld could use up to
>> > key_buffer_size + (read_buffer_size +
>> > sort_buffer_size)*max_connections
> =
>> > 385528
>> > K
>> > bytes of memory
>> > Hope that's ok; if not, decrease some variables
msSQL-MySQL
Is there is utility which is free to convert ms SQL 7.0 running on windows
NT into a mySQL format, i would be very grateful if someone in here could
help me out.
Thanks.
Karma
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 2:53 PM
Subject: Re: start innodb without transactions
> Carlos,
>
> please send me your my.cnf. How big is the combined size of your log
files?
>
> "
> MySQL/InnoDB-4.0.9, January 14, 2003
>
> Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a
> 32-bit computer, InnoDB would write log in a wrong position. That could
make
> crash recovery and InnoDB Hot Backup to fail.
> "
>
> In the first printout:
>
> > InnoDB: Starting log scan based on checkpoint at
> > InnoDB: log sequence number 13 1000286684
> > InnoDB: Doing recovery: scanned up to log sequence number 13 1000286208
>
> looks like InnoDB is not able to scan the log file at all, not even up to
> the checkpoint!
>
> > InnoDB: log sequence number 13 1002344016
> > InnoDB: Doing recovery: scanned up to log sequence number 13 1002343936
>
> The same in the next printout. It has written some 2 MB more log but
cannot
> after a crash scan the log at all!
>
> The failing assertion checks when freeing a BLOB or TEXT field that its
> length is right:
>
> if (extern_len - part_len == 0) {
> ut_a(next_page_no == FIL_NULL);
> }
>
> This could be:
>
> 1) a bug in InnoDB's log writing;
> 2) hardware fault, broken disk;
> 3) serious corruption of the OS file system.
>
> If InnoDB fails to scan lots of log in crash recovery, it means that the
> resulting database may have very extensive corruption. That can explain
why
> some of your tables are not visible at all.
>
> There is little hope of recovering your tables. You should resort to a
> backup and upgrade to 4.0.13. Then do some heavy processing, for example,
a
> table import, and crash mysqld artificially by
>
> killall -9 mysqld
>
> Look then if InnoDB is able to scan the log in crash recovery.
>
> Best regards,
>
> Heikki Tuuri
> Innobase Oy
> http://www.innodb.com
> Transactions, foreign keys, and a hot backup tool for MySQL
> Order MySQL technical support from https://order.mysql.com/
>
>
>
> - Original Message -
> From: ""Carlos Proal"" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.mysql
> Sent: Friday, June 06, 2003 7:41 AM
> Subject: Re: start innodb without transactions
>
>
> >
> > Probably i need to describe the whole story:
> > I did a huge insert, a file about 100Mb, and mysql crashed/restarted,
the
> > err file showed:
> > --
> > 030605 12:11:59 mysqld restarted
> > 030605 12:12:00 InnoDB: Database was not shut down normally.
> > InnoDB: Starting recovery from log files...
> > InnoDB: Starting log scan based on checkpoint at
> > InnoDB: log sequence number 13 1000286684
> > InnoDB: Doing recovery: scanned up to log sequence number 13 1000286208
> > InnoDB: Last MySQL binlog file position 0 756499, file name
> > ./catarina-bin.057
> > 030605 12:12:01 InnoDB: Flushing modified pages from the buffer pool...
> > 030605 12:12:01 InnoDB: Started
> > /centia01/final/database/mysql/libexec/mysqld: ready for connections
> > 030605 12:14:01 InnoDB: Out of memory in additional memory pool.
> > InnoDB: InnoDB will start allocating memory from the OS.
> > InnoDB: You may get better performance if you configure a bigger
> > InnoDB: value in the MySQL my.cnf file for
> > InnoDB: innodb_additional_mem_pool_size.
> > mysqld got signal 10;
> > This could be because you hit a bug. It is also possible that this
binary
> > or one of the libraries it was linked against is corrupt, improperly
> built,
> > or misconfigured. This error can also be caused by malfunctioning
> hardware.
> > We will try our best to scrape up some info that will hopefully help
> > diagnose
> > the problem, but since we have already crashed, something is definitely
> > wrong
> > and this may fail.
> >
> > key_buffer_size=67104768
> > read_buffer_size=131072
> > sort_buffer_size=524280
> > max_used_connections=4
> > max_connections=500
> > threads_connected=4
> > It is possible that mysqld could use up to
> > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
=
> > 385528
> > K
> > bytes of memory
> > Hope that's ok; if not, decrease some variables in the equation.
> > --
> >
> > (i have 256Mb in buffer pool) But the next restart stopped mysql
showing:
> > --
> > 030605 12:14:30 mysqld restarted
> > 030605 12:14:32 InnoDB: Database was not shut down normally.
> > InnoDB: Starting recovery from log files...
> > InnoDB: Starting log scan based on checkpoint at
> > InnoDB: log sequence number 13 1002344016
> > InnoDB: Doing recovery: scanned up to log sequence number 1
