Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Hello, Boaz Yahav wrote: I don't think you realize the nature of the site. Its an auction site and not a retail site. Prices need to be updated on thousands of clients simultaneously. Our goal is to refresh the data on the client every 3-10 seconds while having 1500 online open auctions. This is quite a mess :) humm I am afraid that goal may be a bit unrealistic for your budget. I suggest that you cache as much content as you can to avoid hitting the database. One technique that I use in the PHP Classes site is to cache content indefinitly. Then when the data that defines that content is changed I call a method of my cache file class to void the cache, so it will force the cached data if and when it is needed on the next access for a page that uses that. This way I don't retard the database update process and the cache is only generated if it will ever be need. So I avoid having situations where more than one update is made to the database before the cached data needs to be redisplayed. For making your site static as much as possible, I usually recommend the page fault technique. That consists of static pages that are deleted when their content is updated. When there is a request for them, since when they are missing the server redirects the request to your error document. That is where you regenarate the page file with upto date data. While the page is upto date it remains in the disk and is served as static page at the server top speed (no scripting language nor database to clutter the access). Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Hello, Boaz Yahav wrote: Fail Over is not for when the cluster is too busy, it's for when the server dies, or when someone killed it's power, or when you loose your network, or when you get a blue screen (assuming you are on windows :). Ok, it is the same. When the server is dead, the response is the same: none. Then, in about 30 seconds the cluster will do a fail over to the 2nd node and the site will continue to work as if nothing happens... it's pretty amazing to see this in action :) I had requests to implement that in Metabase. The problem is that PHP database connection functions do not let you define the connection timeout parameters or check if the current persistent connection is still alive. Anyway, nothing that a good middleware could not do better for you. Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Very good answer Frank, Thanks! My department is 95% MS oriented and this is why we prefer an MSSQL Server 2000 Cluster instead of a sun based cluster. We already have an MSSQL 7.0 Cluster which we will be upgrading soon to MSSQL Server 2000 which has been up for over 2 years. It's running on win2K Advanced Server and we are extremely pleased with the up time and performance. We are not considering IBM / ORACLE because we do not have the knowledge in this area, as I said, we are MS Oriented. I asked my Unix people to come up with some kind of Unix / Linux based alternative for a cluster of MySQL and you wouldn't believe some of the combinations they had to do to prepare such a scenario. Bottom line is that no scenario they came up with was a serious one IMHO. Trying to simulate a cluster on a NON cluster aware database does not look like a way to go to a serious Ecommerce Auction site. Thanks berber -Original Message- From: Frank Flynn [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 16, 2002 7:51 PM To: Boaz Yahav; [EMAIL PROTECTED] Subject: RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 There are few things you should consider; perhaps you already have. You may not be replacing the OS of your Web server but you will be adding a new OS for the database since MS SQL only runs on Windows. So now your site will have a Solaris / Apache piece and Windows cluster running MS SQL. I have run configurations like this and they do work however if your fundamental goal is better reliability I suggest to be careful about MS SQL. My experience (not wanting to start any flame wars here) has been that MS SQL is not as reliable as some of the bigger names such as Informix / IBM and Oracle. All of those also run on Solaris which means you could still only have one OS. That may or may not be an advantage to you. The other issue to be very careful about regarding MS SQL is it is not supported on Solaris. So if you have an issue where the database appears to be functioning normally yet your Apache Web server cannot retrieve data from the DB Microsoft will have nothing to do with helping you fix this. It is an unsupported configuration; the connectivity products you will use, whatever they are, will not come from Microsoft nor will any help. But to answer your specific questions: ODBC, JDBC are not the only ways to move data from the database to Apache but they are the most popular ways because they're easy to use and they do work very well. Also check out freeTDS (tabular data stream) and a product called OpenLink, there are others try Web search from your favorite search engine. A few months ago we did a benchmark and we found JDBC to be faster than the Microsoft client or ODBC. In our case we believe this was because of the way that JDBC returned results in larger chunks which matched our needs for that App. Your mileage may vary; these things depend on your application and a particular versions of the software and combinations of the software using. Nothing beats having the time to try a couple different combinations and see which works best for your situation. I don't think there any particularly special points you need to consider because you're using MS SQL but as I've said each application can be different and have its own unique needs. Good Luck, Frank Well, My Site runs now on Solaris. Both the front end (Web Server / php code / Apache) and the Database (Backend server). We had some problems with Mysql and we don't find it 100% reliable for such a busy site. We also want to use a db cluster for high availability (we are talking about $200,000 of hardware and software for the change). The code will still run on Apache / PHP / Solaris so there is no change in that. Only the access to the Database will change. Does this help? berber -Original Message- From: Manuel Lemos [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 12, 2002 10:28 PM To: [EMAIL PROTECTED] Subject: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hello, Boaz Yahav wrote: Hi I'm planning to move my site (Very successful / high traffic Auctions site) from MySQL to MSSQL Server 2000. I was wondering if anyone has done this move and if there are any pit falls to notice. 1. Is ODBC the only way to work from a Solaris / Apache / PHP 4 machine to a Win2K / SQL Server 2000? 2. What could be the performance cost (if any). 3. Are there any special points that need to be taken into consideration on either side? If you have these doubts I wonder if you are really sure if moving from OS and databases is the right thing to do. Maybe if you tell what is you motivation for the move we can address your real problems more objectively. Changing OS, Web Server and database server all at the same time sounds like an operation of great risk. If your motivation really justifies all the changes, maybe changing one thing at a time would
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
I don't think you realize the nature of the site. Its an auction site and not a retail site. Prices need to be updated on thousands of clients simultaneously. Our goal is to refresh the data on the client every 3-10 seconds while having 1500 online open auctions. This is quite a mess :) -Original Message- From: Manuel Lemos [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 13, 2002 11:45 PM To: [EMAIL PROTECTED] Subject: Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hello, Boaz Yahav wrote: You realize that what they did will never work with an Ecommerce auction site where everything must be in real-time... Why do you say that? Because you think you will need to handle as much requests as they do but always with upto date information? AFAIK, most of e-commerce site requests are content publishing of front store pages. Most of that can be handled with no real time database access either with static pages or cached content. Unless you are going to sell 30 million items like Amazon did in X-Mas, you won't need great hardware for that. Anyway, for busy sites is always a good idea to avoid read only database accesses or else your site will not scale. Besides content caching, it is always important to avoid database accesses for simple but repetitive things like session authentication. Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Fail Over is not for when the cluster is too busy, it's for when the server dies, or when someone killed it's power, or when you loose your network, or when you get a blue screen (assuming you are on windows :). Then, in about 30 seconds the cluster will do a fail over to the 2nd node and the site will continue to work as if nothing happens... it's pretty amazing to see this in action :) -Original Message- From: Manuel Lemos [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 13, 2002 11:38 PM To: [EMAIL PROTECTED] Subject: Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hello, Boaz Yahav wrote: My main problem is that MySQL is not Cluster Aware. I never heard of a MySQL server being able to perform a Fail Over to another node. Did you? I never used MySQL in a cluster myself, but AFAIK, if it would not do fail-over, what good a cluster would be for when a cluster server is too busy? I think you should address these questions directly to MySQL AB. Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
There are few things you should consider; perhaps you already have. You may not be replacing the OS of your Web server but you will be adding a new OS for the database since MS SQL only runs on Windows. So now your site will have a Solaris / Apache piece and Windows cluster running MS SQL. I have run configurations like this and they do work however if your fundamental goal is better reliability I suggest to be careful about MS SQL. My experience (not wanting to start any flame wars here) has been that MS SQL is not as reliable as some of the bigger names such as Informix / IBM and Oracle. All of those also run on Solaris which means you could still only have one OS. That may or may not be an advantage to you. The other issue to be very careful about regarding MS SQL is it is not supported on Solaris. So if you have an issue where the database appears to be functioning normally yet your Apache Web server cannot retrieve data from the DB Microsoft will have nothing to do with helping you fix this. It is an unsupported configuration; the connectivity products you will use, whatever they are, will not come from Microsoft nor will any help. But to answer your specific questions: ODBC, JDBC are not the only ways to move data from the database to Apache but they are the most popular ways because they're easy to use and they do work very well. Also check out freeTDS (tabular data stream) and a product called OpenLink, there are others try Web search from your favorite search engine. A few months ago we did a benchmark and we found JDBC to be faster than the Microsoft client or ODBC. In our case we believe this was because of the way that JDBC returned results in larger chunks which matched our needs for that App. Your mileage may vary; these things depend on your application and a particular versions of the software and combinations of the software using. Nothing beats having the time to try a couple different combinations and see which works best for your situation. I don't think there any particularly special points you need to consider because you're using MS SQL but as I've said each application can be different and have its own unique needs. Good Luck, Frank Well, My Site runs now on Solaris. Both the front end (Web Server / php code / Apache) and the Database (Backend server). We had some problems with Mysql and we don't find it 100% reliable for such a busy site. We also want to use a db cluster for high availability (we are talking about $200,000 of hardware and software for the change). The code will still run on Apache / PHP / Solaris so there is no change in that. Only the access to the Database will change. Does this help? berber -Original Message- From: Manuel Lemos [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 12, 2002 10:28 PM To: [EMAIL PROTECTED] Subject: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hello, Boaz Yahav wrote: Hi I'm planning to move my site (Very successful / high traffic Auctions site) from MySQL to MSSQL Server 2000. I was wondering if anyone has done this move and if there are any pit falls to notice. 1. Is ODBC the only way to work from a Solaris / Apache / PHP 4 machine to a Win2K / SQL Server 2000? 2. What could be the performance cost (if any). 3. Are there any special points that need to be taken into consideration on either side? If you have these doubts I wonder if you are really sure if moving from OS and databases is the right thing to do. Maybe if you tell what is you motivation for the move we can address your real problems more objectively. Changing OS, Web Server and database server all at the same time sounds like an operation of great risk. If your motivation really justifies all the changes, maybe changing one thing at a time would be of less risk. Don't forget the Hotmail platform change fiasco. Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
I will read this article and let you know :) My main problem is that MySQL is not Cluster Aware. I never heard of a MySQL server being able to perform a Fail Over to another node. Did you? -Original Message- From: Manuel Lemos [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 12, 2002 11:25 PM To: [EMAIL PROTECTED] Subject: Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hello, Boaz Yahav wrote: Well, My Site runs now on Solaris. Both the front end (Web Server / php code / Apache) and the Database (Backend server). We had some problems with Mysql and we don't find it 100% reliable for such a busy site. We also want to use a db cluster for high availability (we are talking about $200,000 of hardware and software for the change). The code will still run on Apache / PHP / Solaris so there is no change in that. Only the access to the Database will change. Well, I can't speak from experience, but I was told that MySQL replication is very good. For the amount of money that you have as budget, I am sure you can pay a lot of MySQL AB certified consulting hours. I don't know what you mean that MySQL is not reliable. Does that have to do with scalability? There is a whole set of smart decisions to make regarding scalability before you decide to waste you money on commercial solutions. Anyway, before you jump on throw a lot of money to it and expect to do it, I think you would like to read (if you haven't already) this very compeling article on how the AmIHotOrNot.com site developers made it so scalable with just LAMP (Linux-Apache-MySQL). One of the things he states is that it seems that MySQL is much more optimized for Open Source platforms such as Linux than for instance Sun. http://www.webtechniques.com/archives/2001/05/hong/ Maybe that is the way to go. If you make it that way, I would not mind getting half of your budget above for the advice. :-) Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
You realize that what they did will never work with an Ecommerce auction site where everything must be in real-time... -Original Message- From: Manuel Lemos [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 12, 2002 11:25 PM To: [EMAIL PROTECTED] Subject: Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hello, Boaz Yahav wrote: Well, My Site runs now on Solaris. Both the front end (Web Server / php code / Apache) and the Database (Backend server). We had some problems with Mysql and we don't find it 100% reliable for such a busy site. We also want to use a db cluster for high availability (we are talking about $200,000 of hardware and software for the change). The code will still run on Apache / PHP / Solaris so there is no change in that. Only the access to the Database will change. Well, I can't speak from experience, but I was told that MySQL replication is very good. For the amount of money that you have as budget, I am sure you can pay a lot of MySQL AB certified consulting hours. I don't know what you mean that MySQL is not reliable. Does that have to do with scalability? There is a whole set of smart decisions to make regarding scalability before you decide to waste you money on commercial solutions. Anyway, before you jump on throw a lot of money to it and expect to do it, I think you would like to read (if you haven't already) this very compeling article on how the AmIHotOrNot.com site developers made it so scalable with just LAMP (Linux-Apache-MySQL). One of the things he states is that it seems that MySQL is much more optimized for Open Source platforms such as Linux than for instance Sun. http://www.webtechniques.com/archives/2001/05/hong/ Maybe that is the way to go. If you make it that way, I would not mind getting half of your budget above for the advice. :-) Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
It's not just that... For example, when I want to backup the MySQL server (and we are talking of a few GB of data) the server is practically dead while making the dump. MSSQL Server 2000 (for example) does that in the background and you can keep working... Any ideas? -Original Message- From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 13, 2002 10:42 PM To: Boaz Yahav Subject: RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hi! If you are not happy with MyISAM's lack of transactions or row level locking or crash recovery, you could try InnoDB type tables in MySQL. You can use MySQL's master - slave replication to get failover capability. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Hi! InnoDB is multiversioned. You can start a transaction, dump all your tables inside a single transaction using SELECT INTO OUTFILE and you get a snapshot of your database at a precise point of time. Because of multiversioning, your tables are not locked during the dump. I am also writing a (non-free) hot incremental binary backup program for InnoDB which will be even faster than SELECT INTO OUTFILE. It will run in background. Regards, Heikki -Original Message- From: Boaz Yahav [EMAIL PROTECTED] To: Heikki Tuuri [EMAIL PROTECTED] Cc: Manuel Lemos [EMAIL PROTECTED]; [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Sunday, January 13, 2002 10:45 PM Subject: RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 It's not just that... For example, when I want to backup the MySQL server (and we are talking of a few GB of data) the server is practically dead while making the dump. MSSQL Server 2000 (for example) does that in the background and you can keep working... Any ideas? -Original Message- From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 13, 2002 10:42 PM To: Boaz Yahav Subject: RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hi! If you are not happy with MyISAM's lack of transactions or row level locking or crash recovery, you could try InnoDB type tables in MySQL. You can use MySQL's master - slave replication to get failover capability. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Yes. PostgreSQL. On Sun, 13 Jan 2002, Boaz Yahav wrote: It's not just that... For example, when I want to backup the MySQL server (and we are talking of a few GB of data) the server is practically dead while making the dump. MSSQL Server 2000 (for example) does that in the background and you can keep working... Any ideas? -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Hello, Boaz Yahav wrote: It's not just that... For example, when I want to backup the MySQL server (and we are talking of a few GB of data) the server is practically dead while making the dump. MSSQL Server 2000 (for example) does that in the background and you can keep working... Any ideas? You don't have that problem if you use MySQL with Gemini tables of NuSphere. Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Hello, Boaz Yahav wrote: My main problem is that MySQL is not Cluster Aware. I never heard of a MySQL server being able to perform a Fail Over to another node. Did you? I never used MySQL in a cluster myself, but AFAIK, if it would not do fail-over, what good a cluster would be for when a cluster server is too busy? I think you should address these questions directly to MySQL AB. Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Hello, Boaz Yahav wrote: You realize that what they did will never work with an Ecommerce auction site where everything must be in real-time... Why do you say that? Because you think you will need to handle as much requests as they do but always with upto date information? AFAIK, most of e-commerce site requests are content publishing of front store pages. Most of that can be handled with no real time database access either with static pages or cached content. Unless you are going to sell 30 million items like Amazon did in X-Mas, you won't need great hardware for that. Anyway, for busy sites is always a good idea to avoid read only database accesses or else your site will not scale. Besides content caching, it is always important to avoid database accesses for simple but repetitive things like session authentication. Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Well, My Site runs now on Solaris. Both the front end (Web Server / php code / Apache) and the Database (Backend server). We had some problems with Mysql and we don't find it 100% reliable for such a busy site. We also want to use a db cluster for high availability (we are talking about $200,000 of hardware and software for the change). The code will still run on Apache / PHP / Solaris so there is no change in that. Only the access to the Database will change. Does this help? berber -Original Message- From: Manuel Lemos [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 12, 2002 10:28 PM To: [EMAIL PROTECTED] Subject: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000 Hello, Boaz Yahav wrote: Hi I'm planning to move my site (Very successful / high traffic Auctions site) from MySQL to MSSQL Server 2000. I was wondering if anyone has done this move and if there are any pit falls to notice. 1. Is ODBC the only way to work from a Solaris / Apache / PHP 4 machine to a Win2K / SQL Server 2000? 2. What could be the performance cost (if any). 3. Are there any special points that need to be taken into consideration on either side? If you have these doubts I wonder if you are really sure if moving from OS and databases is the right thing to do. Maybe if you tell what is you motivation for the move we can address your real problems more objectively. Changing OS, Web Server and database server all at the same time sounds like an operation of great risk. If your motivation really justifies all the changes, maybe changing one thing at a time would be of less risk. Don't forget the Hotmail platform change fiasco. Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
Hello, Boaz Yahav wrote: Well, My Site runs now on Solaris. Both the front end (Web Server / php code / Apache) and the Database (Backend server). We had some problems with Mysql and we don't find it 100% reliable for such a busy site. We also want to use a db cluster for high availability (we are talking about $200,000 of hardware and software for the change). The code will still run on Apache / PHP / Solaris so there is no change in that. Only the access to the Database will change. Well, I can't speak from experience, but I was told that MySQL replication is very good. For the amount of money that you have as budget, I am sure you can pay a lot of MySQL AB certified consulting hours. I don't know what you mean that MySQL is not reliable. Does that have to do with scalability? There is a whole set of smart decisions to make regarding scalability before you decide to waste you money on commercial solutions. Anyway, before you jump on throw a lot of money to it and expect to do it, I think you would like to read (if you haven't already) this very compeling article on how the AmIHotOrNot.com site developers made it so scalable with just LAMP (Linux-Apache-MySQL). One of the things he states is that it seems that MySQL is much more optimized for Open Source platforms such as Linux than for instance Sun. http://www.webtechniques.com/archives/2001/05/hong/ Maybe that is the way to go. If you make it that way, I would not mind getting half of your budget above for the advice. :-) Regards, Manuel Lemos -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
